The content staging solution for Drupal 8 is based on a re-designed version of the Deploy module. This solution consists of some contrib modules and depends on three Drupal core modules. The core dependencies are Entity API, Serialization and Restful Web Services. The contributed module dependencies are Relaxed Web Services, Multiversion, Key-value Extensions and (soon) Deploy. The Relaxed Web Services module provides a Restful/Relaxed JSON API and endpoints for entities, file attachments, administrative tasks like revisions comparison, starting/stopping replication, etc.

Mark said, “I have a personal aversion to being too tied to one tool, so I want to make sure developers are thinking about their career right now but also 5, 10, 20 years from now.” Who can argue against this? At face value, these words are plain and simple and true. I can’t speak for every supporter of Backdrop CMS, but I personally will be learning both. I choose to do this because I can and I believe it opens many doors to what Drupal can do and how it innovates. I was working in Procedural PHP before I found Drupal in 2007.

Whether you’re a site builder, module or theme developer, or simply an end user of a Drupal website, Drupal 8 has tons in store for you. This ebook will enumerate the major changes in Drupal 8 for end users, for site builders, for designers and front-end developers, and for back-end developers. Note that since Drupal 8 is still under active development, some of the details here may change prior to its release. Drupal 8 is now feature-frozen, so most information should remain relevant. Where applicable, Drupal 7 contributed equivalents of Drupal 8 features will be noted.

There are five key features that we wanted to build: User profile User connection (follow) Uploading images and applying effects Uploading videos Like / Comment on a friends’ image or video While Drupal 8 gave a solid foundation to kick off such a site, there were certain glitches and shortcomings in the modules that were used. Some we solved, and others are being on worked on.

Loading configuration and re-saving it immediately should not result in any changes. Put another way, if the all the runtime dependencies of the configuration are satisfied (i.e it works), then regardless of any additional modules being enabled, the configuration should not change. An interesting case of configuration chainging unexpectedly was discovered in a bug with the filter module. The filter module was adding all the disabled text filters to every filter format configuration entity.