Latest Blog Posts

Planning for CRAP and entity revisions everywhere in core

Submitted by Anonymous (not verified) on Wed, 23/09/2015 - 07:46

<figure class="tmblr-embed tmblr-full" data-provider="youtube" data-orig-width="459" data-orig-height="344" data-url=""><iframe width="540" height="405" id="youtube_iframe" src=";enablejsap…; frameborder="0"></iframe></figure><p>At DrupalCon Barcelona this year I presented with <a href="; target="_blank">Dick Olsson</a> outlining a plan for CRAP (Create Read Archive Purge) and revisions (on all content entities) in core.</p><!-- more --><h2>Phase 0</h2><p><b>For Drupal 8.0.0</b><br/>Enable revisions by default (<a href="; target="_blank"></a&gt;) on content types in the standard install profile and when creating new content types.</p><h2>Phase 1</h2><p><b>For Drupal 8.1.0</b></p><ul><li>Improve the Revisions API performance, some of this will come from moving elements from the multiversion module into the entity API.<br/></li><li>Enable revisions by default for all content entity types. So not just nodes anymore but blocks, comments, taxonomy terms etc.</li><li>Introduce a revision hash, parents and tree. Each revision needs to have a parent so you know where it’s come from, each parent can have multiple child revisions.</li><li>Data migration - Moving all 8.0.0 sites to 8.1.0 will mean moving their data to the new revision system.</li></ul><h2>Phase 2</h2><p><b>For Drupal 8.2.0</b></p><ul><li>Remove the ability to not have revisions. To simplify the API and the data stored it makes sense to remove the ability to disable revisions. This will allow us to remove all the conditional code around if an entity has a revision or not.<br/></li><li>Delete is a new flagged revision. When deleting an entity a new revision will be created and this revision will be flagged as deleted. This is the archive element of the CRAP workflow.</li><li>Introduce purge functionality. There may be times when an entity needs to be completely deleted.</li><li>Commit trash module to core. Trash is just a UI for the delete flag. It displays all entities marked as deleted. It then allows these to be restored by creating a new revision not flagged deleted, or purged by removing the entity.</li></ul><p>Simple right?</p>

Trashing Drupal

Submitted by Anonymous (not verified) on Fri, 11/09/2015 - 09:20

<p>At heart Drupal is an awesome CMS. The reason I would advise going for Drupal over any other framework is it’s ability to manage a scalable amount of content entities.</p><!-- more --><p>Earlier this week I discussed <a href="…; target="_blank">revisions in Drupal 8</a>. Specifically the use of <a href="; target="_blank">Multiversion</a> module to allow Drupal to use a CRAP (Create Read Archive Purge) workflow for content management.</p><p>Since then I have been working on the archive and purge aspects of this workflow. The <a href="; target="_blank">Multiversion</a> module is pretty astonishing in how it revolutionises the way revisions are handled and content is managed but so far there has been little focus on the archive and purge process. When entities are deleted they are simply flagged as “deleted”, they exist in the Drupal database but are gone from any where on the site’s UI. Until now&hellip;</p><p>The all-new <a href="; target="_blank">Trash</a> module builds on the <a href="; target="_blank">Multiversion</a> module provide a place where users can see all their deleted entities, listed by entity type, then restore them along with all their revisions. The first commit on the 8.x-1.x branch was only done 3 days ago on September 8th, so it’s still early days, but the MVP is available as a dev release to have a play with.</p><p>Now, this is more or less the archive process working, next up is purge. So what do we purge? Well, ideally, nothing. It’d be great if we never need to truly delete any entities, but instead purge specific revisions. This is something that will be getting a lot of thought over the coming weeks.</p><p>Another step to look at is compaction. <a href="; target="_blank">Multiversion</a> has been following CouchDB’s API and coupled with the <a href="; target="_blank">Relaxed web services</a> module it allows entities to be replicated to CouchDB and other platforms following the same API. <a href="; target="_blank">CouchDB has a notion of compaction</a> via the “_compact” endpoint. How harshly should the content be compacted? remove all revisions apart from the current one?</p><p>All of this will be discussed by <a href="; target="_blank">Dick Olsson</a> and I, in our session <a href="…; target="_blank">Planning for CRAP and entity revisions everywhere in core</a> at <a href="; target="_blank">Drupalcon Barcelona</a>.</p>

Revisions in Drupal 8

Submitted by Anonymous (not verified) on Mon, 07/09/2015 - 09:56

<p>I’m sorry to say that on the surface little has changed with revisions in Drupal 8, but there is some work still being done.</p><!-- more --><p>The first step, for me, is to get <a href="; target="_blank">revisions enabled by default</a>. I was interested to hear from <a href="; target="_blank">webchick</a> that this <a href="; target="_blank">came up indirectly during user testing</a>. Most Drupal sites I have worked on have been large enterprise organisations. These types of companies all want an audit trail and all want to effectively manage their content. This is easily achievable by using revisions. It looks as though many new to Drupal are in a way scared by revisions. Enabling revisions by default will take away the reasoning for being scared and give this awesome feature out of the box.</p><p>The current revisions system isn’t perfect, it’s pretty good, but not perfect. There’s a lot of work being done to improve upon in. In Drupal 7 we had the <a href="; target="_blank">deploy module</a>, which allowed users to move content from one site to another, such as from staging to production, this built upon the existing revisioning platform. In Drupal 8 we have the <a href="; target="_blank">multiversion</a> and <a href="; target="_blank">relaxed web services</a> modules. These were both <a href="; target="_blank">demoed</a> by <a href="; target="_blank">dixon_</a> at <a href="; target="_blank">Drupalcon Los Angeles</a>.</p><p>Although <a href="; target="_blank">multiversion</a> builds upon Drupal 8′s core revision system it’s vastly different with an awesome direction. One key feature is it enables revisions for every entity, users, comments, everything. The way it displays revisions as a tree also makes it clear and understandable as to how the revisons work and how the relate.</p><p>The <a href="; target="_blank">relaxed web services</a> module builds upon a similar ethos as the <a href="; target="_blank">deploy module</a>, but it makes use of an API based on the <a href="; target="_blank"> protocol</a> to handle bi-directional content replication. This means it can replicate content to any other <a href="; target="_blank"> protocol</a> source such as <a href="; target="_blank">couchdb</a> or <a href="; target="_blank">pouchdb</a>.</p><p>Step by step Drupal 8 is getting more amazing.</p><p>To find out more about all this head along to the <a href="…; target="_blank">Planning for CRAP and entity revisions everywhere in core</a> session at Drupalcon Barcelona on Tuesday 22nd September at 11am in room 122-123 “Interoute”.</p>

Update module the next generation

Submitted by Anonymous (not verified) on Wed, 02/09/2015 - 13:48

<p>In a post last week I discussed <a href="…; target="_blank">versioning in Drupal</a> and briefly touched on version numbers in info files. A lot of my focus over the last few months has been around composer and Drupal, one issue for Drupal when using composer for contrib modules is that the info file is pulled from git and therefore doesn’t have the version number, project name or datestamp in the info.yml file that is added by the packager.</p><!-- more --><p>I am <a href="; target="_blank">currently working on a patch</a> for the update module which will get the project name from the module’s composer.json. This is just the first step because the project name is what’s needed for the module to show on the update status page.</p><p>The patch adds a composer parser service, which like the info parser service that parses the info.yml file of a module, this parses the composer.json file of a module. From here we can get the project name such as “drupal/devel”, then by exploding that we can get the project name from the second element in the array.</p><p>Composer.json files sometimes include a version number so we could use that too, but this is vary rare. The only real option for the version number is the git branch or git tag, this is how the <a href="; target="_blank">git deploy module</a> works.</p>