One Million Drupal Sites

It’s official! According to the project usage stats, Drupal has more than a million sites (1,005,489 as of February 15) live and in production on the web.

This number under-reports reality, because the project usage stats don’t count *all* Drupal sites on the web. For more information on how project usage stats are counted, visit the usage statistics page.

How to Write a Drupal 8 Installation Profile

This article is being written based on the Spark distribution.

Installation profiles are like modules

All installation profiles must have:

  2. profilename.profile

files, and they can also have a profilename.install file.

The profilename.profile file has access to almost everything a normal Drupal modulename.module file does because Drupal is fully bootstrapped before almost anything in the profile runs. The primary exception is that st() should generally be used to translate strings instead of the usual t() because the localization hasn't been set up until the installation process completes. Profile files should reside in their own directory within the /profiles directory to be loaded.

.info.yml file

The file should look similar to this:

Creating CentOS VM for Drupal development

The purpose of this topic is to cover the useful linux commands in creating VM for Drupal development. I am not linux expert so I can understand the pain of newbees into linux world.

Download Oracle VM box from

Follow the instructions in Oracle VM box I am not covering it here as instructions are simple to understand.

Structure of an Entity annotation

Entity types, both configuration and content entity are defined using annotation in the entity class.

The Example entity is defined in Drupal\example\Entity\Example.php (assumes the module name is "example"):

Parse error: syntax error, unexpected T_STRING in /home/....public_html/includes/ on line 592

Hi I'm getting this error message:
Parse error: syntax error, unexpected T_STRING in /home/....../includes/ on line 592

These are the lines mentioned:

Managing configuration - do's and don'ts

It's strongly recommended that you do a database-dump before each synchronization of the staging and the active directory.
For example if a node.type.[name_of_type].yml file is missing in the staging directory, the synchronization will delete all contents of this bundle on your site.
The database-dump "could save your live" on a potential needed rollback-strategy.


Subscribe with RSS Subscribe to RSS - Drupal 8.x