سیاره دروپال

Drupal.org - aggregated feeds in category Planet Drupal
Subscribe to خوراک سیاره دروپال
Enforce SSL in Drupal 8 using a redirect timmillwood Wed, 03/05/2017 - 11:40

Place this code within .htaccess underneath `RewriteEngine on`.

RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Tags drupal-planet drupal drupal 8 ssl Add new comment

Creatng a custom video node export/import process using custom forms, RSS feeds with Views, and a custom Feeds importer using the SimplePie parser.

read more

Chris May 02, 2017 Installing Let's Encrypt Certificates on Acquia

Recently, one of our Enterprise clients asked for some help installing SSL certificates on their Acquia-hosted Stage and Development environments. This is not something that Acquia seems to provide (they do provide basic SSL on dev/stage environments, but not with hostname matching), so we set out to get them set up. They use their dev and staging environments to demonstrate new content and features to stakeholders, and some were getting scared off by the SSL certificate warnings.

Since its founding, Acquia has set a strong precedent for investing in developer experience. Developers are users and influencers of Acquia products, and need to be armed with state-of-the-art tools to build leading digital experiences with Drupal. From Acquia Dev Desktop to the Drupal 8 Module Acceleration Project, Acquia is committed to developing tools and resources that empower development teams.

Tags: acquia drupal planet

As of CiviCRM Entity 2.0-beta4 the sub module called CiviCRM Entity Price Set Field provides a Drupal field type for the Event entity type.  In this article we’ll review the features of this submodule and discuss how to configure and customize it to fit your needs.

Event Registration on the Event view page

When configured to display on the Event view pages, this field generates a registration form that supports:

  • Registering multiple Participants
  • Uses the event’s price set and all price fields of any type
  • Pay later or credit card transactions utilizing CiviCRM’s payment processing
  • Profiles
  • Default values for the profile fields corresponding to the logged in user’s contact information
  • Customizable Ajax-fied confirmation and thank you panes
  • Utilizes the event’s settings such as “Is paid event?” etc..
  • Test or Live transactions
Field widget for the Event Edit Form

A “simple” field widget is provided by default for this module.  At the time of this writing, only the first price field can be edited via this widget.  

Getting Started

CiviCRM Entity and CiviCRM Entity Profile are dependencies for CiviCRM Entity Price Set Field. Go to the Drupal module page and enable all three modules and enable CiviCRM Entity Price Set Field, CiviCRM Entity, and CiviCRM Entity Profile.

Once enabled, you can add the Price Set Field to the Event Entity Type.

  • Go to the Event Manage Fields form at “/admin/structure/civicrm-entity/civicrm_event”
  • Scroll to the “Add New Field” section, enter a Label, and select the ‘CiviCRM Entity Price Set’ field type, for this example select the “Simple -- one price field” widget
  • There’s no special field or field instance settings, so just click save until you’re back to the Manage Fields page
  • Now go to the Manage Display Full Content form at “/admin/structure/civicrm-entity/civicrm_event/display/full
  • Set the new field to display
  • There is a field formatter setting to optionally submit test transactions
  • Pat yourself on the back, you’re setup to take registrations from the Drupal based Event view pages at /civicrm-event/[id]

Please note that the registration form takes into account the different settings on the CiviCRM Event.  For instance it will only enable CC transactions and render a billing block if the “Paid Event?” checkbox is checked. The form conforms to registration start and end dates, only renders if Online Registration is enabled.  The form checks to see if Max Participants has been reached, even when adding additional participants. Additional participants can only be added if “Allow Multiple Registrations” is enabled.

To learn more about registration form, how transactions work with the Contribution API, and how it can be customized, please continue reading on Skvare.com.

ToolsCiviCRMCiviEventDrupalExtensions

At our April 2017 meeting Renée Stephen gave the Vancouver Drupal User Group (VanDUG) an encore of her Pacific Northwest Drupal Summit (PNWDS) presentation: No more performance anxiety! The presentation walked us through the formal process of server load testing.

Renée's current gig as Technical Consultant at Acquia gives has given her lots of experience on the subject and she knows how to present. It's always a pleasure when someone deeply steeped in domain knowledge gives a great presentation.

I can't begin to summarize the entire presentation. Renée's slide-deck is available for download at the presentation description on the PNWDS website: No more performance anxiety: get your Drupal site tuned and ready to take the stage! Direct PDF link: PNWDS 2017 - No more performance anxiety.pdf

Here are the take-aways that surprised me:

  • The standard definition of load testing is backend server oriented and does not include front-end performance issues. For example, large hero images or JavaScript widget rendering. While these are important they are not part of this discipline and usually require different tool sets.
  • You'll want at least 2 days, possibly more, to familiarize yourself with jMeter.

I was also reminded of how much server and tool knowledge is required if you're the one doing the remediation. No single detail is exceedingly complicated but each technology in the stack has its particulars, tools, and metics.

Here are the tools Renée mentioned in her presentation:

Profiling Toolkit

  • Blazemeter Recorder
  • Postman
  • HAR
  • jMeter

Dynamic & Static Analysis

  • Blazemeter / jMeter
  • Apachebench (ab)
  • New Relic / TraceView / XHProf
  • WebPage Test
  • Chrome Inspector
  • Server logs and stats
  • varnishstat / varnishlog
  • Redis monitor / memcached-tool
  • Drupal Devel module WebProfiler

She also made a repo of her jMeter example files available at https://github.com/reinette/loadtest

A big thank you to Renée for presenting. I missed the presentation at PNWDS and was happy for the second change to see it.

Tagged:

Last week, 3,271 people gathered at DrupalCon Baltimore to share ideas, to connect with friends and colleagues, and to collaborate on both code and community. It was a great event. One of my biggest takeaways from DrupalCon Baltimore is that Drupal 8's momentum is picking up more and more steam. There are now about 15,000 Drupal 8 sites launching every month.

I want to continue the tradition of sharing my State of Drupal presentations. You can watch a recording of my keynote (starting at 24:00) or download a copy of my slides here (108 MB).



The first half of my presentation provided an overview of Drupal 8 updates. I discussed why Drupal is for ambitious digital experiences, how we will make Drupal upgrades easier and why we added four new Drupal 8 committers recently.

The second half of my keynote highlighted the newest improvements to Drupal 8.3, which was released less than a month ago. I showcased how an organization like The Louvre could use Drupal 8 to take advantage of new or improved site builder (layouts video, workflow video), content author (authoring video) and end user (BigPipe video, chatbot video) features.

I also shared that the power of Drupal lies in its ability to support the spectrum of both traditional websites and decoupled applications. Drupal continues to move beyond the page, and is equipped to support new user experiences and distribution platforms, such as conversational user interfaces. The ability to support any user experience is driving the community's emphasis on making Drupal API-first, not API-only.

Finally, it was really rewarding to spotlight several Drupalists that have made an incredible impact on Drupal. If you are interested in viewing each spotlight, they are now available on my YouTube channel.

Thanks to all who made DrupalCon Baltimore a truly amazing event. Every year, DrupalCon allows the Drupal community to come together to re-energize, collaborate and celebrate. Discussions on evolving Drupal's Code of Conduct and community governance were held and will continue to take place virtually after DrupalCon. If you have not yet had the chance, I encourage you to participate.

Discovery Workshops play an important role in the success of any development project. If a Discovery Workshop is not conducted the right manner, its value can be lost.

Tags: acquia drupal planet

On Saturday, April 9th, as most of the attendees of ngconf were catching flights home, a group of the core Angular team from Google and prominent community members came together for a Contributor’s Day discussion organized by ThisDot. The stated goal was to discuss areas where the core team and community could better support each other and help advance adoption and ease of entry into using Angular.

Start:  2017-05-02 12:00 - 2017-05-04 12:00 UTC Organizers:  catch cilefen xjm Event type:  Online meeting (eg. IRC meeting)

The monthly core patch (bug fix) release window is this Wednesday, May 03. Drupal 8.3.2 will be released with dozens of fixes for Drupal 8. There will be no Drupal 7 bugfix release this month.

To ensure a reliable release window for the patch release, there will be a Drupal 8.3.x commit freeze from 12:00 UTC Tuesday to 12:00 UTC Thursday. Now is a good time to update your development/staging servers to the latest 8.3.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the latest changes that will be included in the release, see the 8.3.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, May 17 (security release window)
  • Wednesday, June 07 (patch release window)
  • Wednesday, October 5 (scheduled minor release)

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

What is Drupal?

In his keynote at DrupalCon Baltimore 2017, Dries talked for some time about how Drupal is now for Ambitious Digital Experiences. There has been a lot of talk over the last few years, especially since Drupal 8 was release, that Drupal is now an enterprise CMS. With this keynote it seems as though Dries is, in a way, acknowledging this. Ambitious Digital Experiences reads as something more complex than a blog, a brochure site, or sites for SMEs.

With this in mind, and recent discussions about the Future of Drupal, maybe it's time to put together a sort overview of where we are and what we have in Drupal.

Drupal 8 took nearly 5 years to develop and had over 4,000 people contribute code to it. There are now 11 core committers for Drupal 8, with a further 3 committers tasked with Drupal 7. Listed in MAINTAINERS.txt are over 60 subsystem maintainers who oversee the development of parts of Drupal known as "subsystems".

When downloading Drupal 8 the majority of the code sites within the core directory, and from there is split into a number of distinct parts. There are 22 Drupal components, which are independent libraries and don't depend on anything else within Drupal, there are all available via github. On top of are over 70 base subsystems, these may depend on components or other base subsystems, but don't depend on any modules. Finally there's over 70 modules, 5 themes, and 2 profiles, these may depend on any other parts of Drupal core. From these modules there are 12 that are (or were) experimental, experimental modules are here to add new functionality into core for testing purposes, but not yet fully supported.

The documentation for Drupal core is pretty awesome, and well worth a read for those looking for more information on the governance, "gate", or development workflow.

timmillwood Sun, 30/04/2017 - 12:28 Tags drupal-planet drupal drupal core Add new comment
What is Drupal?

In his keynote at DrupalCon Baltimore 2017, Dries talked for some time about how Drupal is now for Ambitious Digital Experiences. There has been a lot of talk over the last few years, especially since Drupal 8 was release, that Drupal is now an enterprise CMS. With this keynote it seems as though Dries is, in a way, acknowledging this. Ambitious Digital Experiences reads as, something more complex than a blog, a brochure site, or sites for SMEs.

With this in mind, and recent discussions about the Future of Drupal, maybe it's time to take a look at where we are and what we have in Drupal.

Drupal 8 took nearly 5 years to develop and had over 4,000 people contribute code to it. There are now 11 core committers for Drupal 8, with a further 3 committers tasked with Drupal 7. Listed in MAINTAINERS.txt are over 60 subsystem maintainers who oversee the development of parts of Drupal known as "subsystems".

When downloading Drupal 8 the majority of the code sites within the core directory, and from there is split into a number of distinct parts. There are 22 Drupal components, which are independent libraries and don't depend on anything else within Drupal, there are all available via github. On top of are over 70 base subsystems, these may depend on components or other base subsystems, but don't depend on any modules. Finally there's over 70 modules, 5 themes, and 2 profiles, these may depend on any other parts of Drupal core. From these modules there are 12 that are (or were) experimental, experimental modules are here to add new functionality into core for testing purposes, but not yet fully supported.

The documentation for Drupal core is pretty awesome, and well worth a read for those looking for more information on the governance, "gate", or development workflow.

timmillwood Sun, 30/04/2017 - 12:28 Tags drupal-planet drupal drupal core Add new comment

Direct .mp3 file download.

Join Chris Weber, Ted Bowman, Kelley Curry and Mike Anello discuss the goings-on at Day 2 of DrupalCon Baltimore. Music: We'll Get the Hard Part Done Tonight (Hamilton Parody)

Direct .mp3 file download.

Join Kelley Curry, Ryan Price, Liz Lipinski, Dan Schiavone, Kevin Lannahan, Lakia Newkirk and Mike Anello discuss the goings-on at Day 1 of DrupalCon Baltimore. Music: Drupalcon Baltimore (to the tune of Good Morning Baltimore) from the Prenote.

CiviCRM Entity 2.0-beta7 has been released.

Pick it up now at the Drupal.org Project Page

Changes since beta6:

Add Rules action Assign Contact to Group
Add Rules action Remove Contact from Group
Add Integration for IM entity
Add Integration for Website entity
Add integration for Contribution Recur
Add Rules event for CiviCRM Price Set Field 'After Successful CC Transaction'
CiviCRM Price Set Field , improved support for price fields with multiple checkboxes
Fix issues with CiviCRM Core Contribution Recur Views integration
Enable CiviCRM Entity Reference field on parent entity 'add', Inline Entity Form Single widget, for Contacts
Expose civicrm_world_region table to Views

Views Relationships:

  • Membership -> Membership Payment
  • Participant -> Participant Payment
  • Participant Payment -> Participant
  • Explicit Relationship from Address -> Country
  • Country -> World Region

Overhaul of CiviCRM Entity Inline, inline entity form widget FAPI generation and handling
Minor bug fixes for CiviCRM Entity, CiviCRM Price Set Field, CiviCRM Entity Discount, CiviCRM Entity Reference Field

 

CiviCRM Entity is close to its stable, non-beta release.  We've had fewer and fewer bug reports each release, and only 1 found in the main module since beta6. Unless something is broken, 2.0 will be cut next.

Development sponsored by Skvare

Thanks to all our contributors and users!

ToolsDrupalExtensionsRelease
Content Moderation + Content Translation = Crazy

As part of the Drupal Workflow Initiative we have critical issue relating to Content Moderation and translations. This is not actually a Content Moderation issue, but is just surfaced by Content Moderation because it allows you to create forward revisions. The video here should explain the issue:

Forward revisions + translation UI can result in forked draft revisions and Only having one default revision per entity forces translations to be kept in sync are the related core issues.

timmillwood Fri, 28/04/2017 - 16:08 Tags drupal-planet drupal 8 drupal core drupal Comment

Submitted by Agnar Ødegård (not verified) on Fri, 28/04/2017 - 19:36

Permalink

You have one field (revision) in the node table and you're trying to keep tabs on two or more pieces of information. You may succeed by creating rules to keep revision number across languages to be the same, but as you point out, when reverting revision for one language you really don't know the correct revision for the other language(s).

I think we'd avoid a lot of hurt by introducing a new table translation_revision. The id in this table will replace the revision id in the node table. The new table will know which revision is current for any language.

This will for sure break BC, but in the end I think it will be the cleanest solution.

Add new comment
Content Moderation + Content Translation = Crazy

As part of the Drupal Workflow Initiative we have critical issue relating to Content Moderation and translations. This is not actually a Content Moderation issue, but is just surfaced by Content Moderation because it allows you to create forward revisions. The video here should explain the issue:

Forward revisions + translation UI can result in forked draft revisions and Only having one default revision per entity forces translations to be kept in sync are the related core issues.

timmillwood Fri, 28/04/2017 - 16:08 Tags drupal-planet drupal 8 drupal core drupal Add new comment

Entities have been introduced late in Drupal 7. Drupal entity is an instance of a particular instance type. For example, the entity type for taxonomy terms is named taxonomy_term and the class name Term. We include the class like  Drupal\taxonomy\Entity\Term. Here taxonomy is a core module name, and Term is the class name of Entity.

A. How to create an user programmatically.

The fields to be created are as follows:

  1.  Username
  2.  Email address
DrupalCon Baltimore, Heads or Tails?

Every few years at DrupalCon, a new theme sweeps through the community. It’s a conceptual theme—a motif, a forward-looking glimpse into the future (not the kind with a .info file). The topic tends to dominate conversations and fill sessions. People have varying ideas of how to best approach the new frontier.

Kathryn McClintock Fri, 04/28/2017 - 13:38

When I first began attending DrupalCons in 2011, I remember the hype about responsive websites: the difference between responsive and adaptive layouts, which grid system to use, and how to best add and target classes to efficiently apply media queries.

In 2014, there was a natural and communal shift in interest to Drupal 8’s frontend. Twig was the new kid on the block and everyone wanted a taste. Developers aimed to learn the new syntax and eagerly compared the new D8 techniques to their tried and true D7 counterparts.

This year at DrupalCon Baltimore, the hot topic has been headless Drupal. Decoupling Drupal’s frontend has been buzzed about for years, but in the past it seemed to be just that—a buzz word—a conceptual, potentially problematic, but exciting idea. Today, on the last day of DrupalCon, it’s clear developers are not just buzzing anymore, they’re building headless Drupal sites and loving it. Amazee Labs is building headless Drupal sites and loving it.

Amazee’s history with headless Drupal is a complicated one. In fact, our own Michael Schmid pointed out during his and Brandon’s React, GraphQL and Drupal session, how Amazee Labs was both skeptical and dismissive of the decoupled/headless vision when the idea initially emerged. In the last quarter of 2016 however, Amazee’s stance on headless changed. I’d encourage you to review Michael and Brandon’s Wednesday session for a deeper explanation as to the reasons behind that shift. 

Technology is a rapidly changing thing and always will be. As developers, it’s natural to feel more or less acceptance towards some changes than others. As a frontend developer who’s grown to master and enjoy working in Drupal’s theme layer, the shift to headless is a tough pill to swallow. I’d equate the sensation to experiencing some kind of loss—there’s a kind of mourning for all the hard, long hours put into building expertise in a complex, yet rewarding theme system. I’ve grown to love Twig, transforming Drupal’s notoriously bad markup into something simple and semantic, and creating truly beautiful Drupal experiences “the old fashioned way.”

Dries published an article Tuesday during the conference, Drupal is API-first, not API-only. In the post, he discusses the benefits of preserving the coupling between Drupal’s front- and back- ends, at least in part. His summary on headless CMSs has validated many of the thoughts I have regarding a fully decoupled Drupal. There are reasons to remain coupled, reasons to go headless, and reasons for a middle-of-the-road approach.

We are certainly future-looking at Amazee Labs. As a company, we are committed to enhancing our team’s skills and providing clients cutting-edge solutions. My takeaway from DrupalCon Baltimore is to embrace and learn new skills required to build innovative headless frontends while simultaneously working to improve and educate others on Drupal 8’s theme layer. The best of both worlds. Let me hear from you, fellow frontend Drupal devs—what’s your take?

Don’t panic! If you don’t use Content Moderation- and Layout Plugin-based components (like Display Suite, Panels, Panelizer and Contexts) then you’ll be fine upgrading to Drupal 8.3. If you do, there are just a few things you need to know first. “It looks insanely complicated, and this is one of the reasons why the snug. Continue reading...

آخرین ارسال ها

محتواهای محبوب

درباره ما

Author
اینجا دروپال یعنی همه چیز. در مورد دروپال صحبت میکنیم. ماژول هامون رو به اشتراک میزاریم در مورد قالب دروپال ، فروشگاه دروپال، دروپال فارسی و تاریخ شمسی دروپال صحبت میکنیم و هرچیزی که در مورد طراحی سایت با دروپال میدونیم به هم انتقال میدیم. دروپالیون یک سایت شخصی نیست. ما دست همه کسانی که برای پیشرفت دروپال تلاش میکنند رو میفشاریم و با آغوش باز اونها رو در این سایت میپذیریم.

تماس با ما

با ما تماس بگیرید.

logo-samandehi