Drupal News

It's Drupal Contrib Wednesday! Post recent contrib module likes/dislikes

Specbee: Drupal and Google Analytics - How to Create Custom Reports for Drupal Website

Drupal Config Management: Multiple Developers and SVN

  • Hi guys,

    we're in the process of rewriting our old D6 site into a D8 site. The config management is giving us a bit of a headache.

    • Our team consists of developers and a Drupal consultant.
    • We commit our config to svn.
    • We use config_split to manage staging differences
    Workflow commit (order of steps is important):
    • export config
    • dump relevant content (Things we consider configuration, but Drupal considers content)
    • svn up (This merges the svn state with the current local state)
    • Import the config and content to test locally
    • svn commit of relevant config changes and related code changes
    • Jenkins starts and tests config changes (Can the config be imported? Are there any error messages when opening pages?)

    This process only works if everyone is very disciplined. Otherwise, it results in dozens of unnecessary changes to the config files that have to be sorted out. This leads to commits of unwanted changes or to commits that are incomplete. This happens a lot, especially to our consultant, who can't program at all (we knew this going in). At least once a week one of the developers spends 1-2 hrs cleaning up the committed config. Commits are time-consuming, because of this. Everyone knows to commit more often as that mitigates the changes and thus lowers the time needed. However, not everyone wants or can do this (some changes are bigger, but not big enough to warrant a branch).

    Example 1: One developer swears he only worked on the feature he was supposed to but had inexplicable changes across all files. Names had been translated from English to German.

    Example 2: Our consultant added new fields (e.g. recommendation and ISBN) to product entities and later deleted some of those fields (e.g. recommendation). Yet the commited fields contained references to the deleted fields (e.g. ISBN depended on recommendation).


    The new configuration management works. It does what it is supposed to do. It's the process that we use that is to complex but how to change it?

    In my opinion, the problem is that in symfony changing the configuration is a conscious act. Drupal obfuscates it to a degree (to make it easier to work with). I think that is part of the problem. In D6 we built a configuration management based on features. After a feature module was created we directly altered that, which made changes deliberate. We could alter the yml files directly (which some of us do already) and use config_split to bundle relevant configuration together. Something just does not feel right with that approach.


    How do other teams handle this? Is there something we're missing? Most of the developers in our team are familiar with symfony and were hoping something as streamlined.

    submitted by /u/Mindz-ei
    [link] [comments]

    6 days 4 hours ago

Drupal website having browser issues

Agiledrop.com Blog: AGILEDROP: An ever-expanding field of opportunities for Drupal

  • There were five pieces altogether written about ambitious Drupal experiences. Each of them focused on a single subject of what constitutes an ambitious digital experience. In the first part of the series, I did my best to explain what ambitious digital experiences mean. The main conclusion, at least in my opinion, is that experience is much more than just mere content. And ambitious digital experiences should come as natural and intuitive as possible. And be focused on the customers, on the users.    Provide valuable and unique digital experiences I have tried to define the term customer… READ MORE

    6 days 7 hours ago

Colorfield: React and Drupal 8 with JSON API 3/3

  • React and Drupal 8 with JSON API 3/3 christophe Tue, 16/01/2018 - 22:31 This post focuses on translation issues and various pitfalls that you might encounter while building with React and Drupal: internationalization with and without language fallback, include images with images styles, taxonomy filter, fetch data on the route or the component, sort by weight, deploy in production.

    6 days 12 hours ago

Evolving Web: Drupal 8 Modules We ♥ for 2018

  • With so many shiny new Drupal 8 modules emerging this year, we were hard pressed to pick our recommendations for 2018. It came down to asking ourselves: which modules are we excited about implementing in 2018… the ones that will make our projects better, faster, smarter brighter? Read on for our list of Drupal 8 modules we're excited about.

    Configuration Split

    The Drupal Configuration Split module makes Drupal 8 configuration management more customizable. This means you can set up some configurations that can be edited on the live site, without interfering with your configuration management workflow. Instead of importing and exporting the whole set of a site’s configuration, the module enables you to define sets of configuration to export to different directories that automatically merge again when they are imported.

    Content Workflow

    If you’ve shied away from implementing complicated workflows in the past, you’ll enjoy how the Content Workflow module makes it easy to set up a simple workflow. This core module enables you to streamline the content publication process by defining states for content (such as draft, unpublished and published) and then manage permissions around these states.


    The Deploy content staging module makes it easier to stage and preview content for a Drupal site. It’s often used to deploy content from one Drupal site to another. Redesigned for Drupal 8, the new version is based on the Multiversion and Replication modules, making it more efficient and flexible.

    Drupal Commerce

    The new full release of Drupal Commerce has us very excited to start building ecommerce sites in Drupal 8. Fully rebuilt for Drupal 8, the new Drupal Commerce module doesn’t presume a specific ecommerce business model, enabling developers to customize the module to suit a merchant’s needs.


    The JSON API module formats your JSON requests and responses to make them compliant with the JSON API Specification. This module is the key to setting up Drupal as a backend so you can implement the font-end with React or your front-end platform of choice.

    Schema.org Metatag

    Ramp up your SEO with structured data that helps Google categorize and display your pages. The Schema.org Metatag module allows you to add and validate Schema.org structured data as JASON LD, one of Google’s preferred data formats.

    UI Patterns

    If you’re looking for a way to implement an ‘atomic design’ in Drupal the Drupal UI Patterns project is a nice option. It consists of six modules that allow you to define and expose UI patterns as Drupal plugins. You can use them as drop-in templates for all entity types — paragraphs, views, field groups and more.


    The Drupal webform module has a new release candidate for Drupal 8. A ton of work has been put into the module; it’s like a whole form-building application inside your Drupal site. Quickly integrate forms into any Drupal 8 website. enables you to build, publish and duplicate webforms. You can also manage and download submissions, and send confirmations to users.

    Which Drupal 8 modules are doing it for you?

    We’d love to hear about which Drupal 8 modules your team is excited about. Leave us a comment.


    + more awesome articles by Evolving Web

    6 days 15 hours ago

Manifesto: Looking ahead to Drupalcamp London 2018

  • This year’s Drupalcamp London, a three-day knowledge-sharing conference devoted to all things Drupal, promises to be the biggest and best yet. Taking place at City University from 2nd to 4th March, it’s a must-visit event for anyone with more than a passing interest in the open-source CMS – developers, site builders, vendors, agencies and potential. Continue reading...

    6 days 19 hours ago

It's Triumphant Tuesday! Post your recent Drupal wins and launches