Drupal install profile distribution name

Email The subscriber's email address. Articles April 15 3 min read. Drupal for Community Platforms Articles December 14 5 min read. Planning your next digital transformation goals?

We can help you achieve that. What Do We Expect? The content should align with our interest in web development and open source technology. However we are open to topics from in and around the industry. An average blog post should be of around words, but this is of course subjective.

We love crazy and colourful content. Feel free to link awesome pictures, infographics, stats, and all. We are also open to articles with cool tips and tricks, some How-to and step by step guide as well Have a question? You must have JavaScript enabled to use this form. When you install a distribution, you'll see the phrase "installation profile" used.

This can cause confusion, so let's explain the difference. A distribution is not an installation profile. Take a look at the image below which is a screenshot of the Drupal Commerce distribution for Drupal 7.

The same is true with distributions in Drupal 8. The image below shows the files for the Lightning distribution:. Join today and get access to 1,'s of books and videos.

Sign up today! Here are examples of Drupal distributions that are designed to meet a specific need: Drupal Commerce : The quickest way to get up and running with e-commerce in Drupal.

Lightning : Acquia's version of Drupal that moves faster than core, and ships cool features early. Use this update function to install the newer version of the install profile. What now? You have created and perfected your installation profile. You have created the files and functions to install, update, and maintain them as well. The next step is to package your profile for distribution. Here is a nifty guide on how to package a profile on drupal. For more information please contact us.

Main Content. No longer do you need to worry that some module on your site has been modified without anybody knowing about it.

Never modify the module files directly; create a patch for the issue you are having and place that patch somewhere accessible by your make file preferably the module issue queue on drupal.

You don't need to wait for the module maintainer to apply your patch, you can still download it and apply it yourself in your make file. As you build your web site, it's good practice to export your various content types, views, and other configuration into Features using the Features module and then add those exported modules to your profile. With this strategy you can rebuild all of the code for your site at any time by re-executing the drush make command.

Paired with a sql dump of your database, this makes it easy to deploy your site. To actually inherit from an existing profile we need to change two things: 1 Tell Drupal the "base" profile name, 2 Tell Drush to execute the "base" make file. To tell Drupal the name of the base profile, add this line to your profilename. This should be the filename of the base profile without any extension or path.

To execute the make file of your base profile, simply add it to your profile. Simple, right! Just specify the "type" of "profile" instead of "module" and drush will download it and then recursively run the make file of the base profile.

In fact, you can nest this as far as you want, creating sub-sub-profiles that inherited from sub-profiles that inherit from profiles. But wait, there is one final detail. While drush has recursive nesting of profiles built-in, Drupal itself still needs a small tweak.

When you reference a module in Drupal, you need to tell it what order to look into the other profile directories. You want any module within your main profile directory to take precedence over any module with the same name in the base profile.

This allows your profile to use a newer version of a module or apply different patches than the same module in the base distribution. The patch needed for Drupal is here: Make install profiles inheritable. A patch for both Drupal 7 and Drupal 8 is provided and the issue is marked for back-porting to Drupal 7. You can easily include this patch in your make file near the top where you specify the version of Drupal you are using:.

If your profile installs a different version of a module that was already included in the base profile, the result will vary depending upon what version of Drush you are using.