Planet Drupal

Subscribe to flux Planet Drupal - aggregated feeds in category Planet Drupal
Mis à jour : il y a 25 min 38 sec

ERPAL: A new way to update Drupal sites automatically

lun, 08/06/2015 - 12:55

Automated Drupal core and contrib updates have been discussed in the Drupal community on as well as on external blogs since Drupalgeddon in October 2014. The result? Automated updates are a good idea and would prevent Drupal sites from being hacked, but they also bring some inherent problems, such as:

  • Updates applied directly to the live site will ignore the development and quality assurance workflow
  • Updates could break the site if manually applied patches are overridden by automatically applied updates
  • If updates aren’t done continuously, the code changes are major and risky when applied as security hotfixes

Those are the most important arguments against automated updates from "the inside", meaning where Drupal updates its code base itself. Because many Drupal sites are developed in a professional environment, enterprise sites in particular, these Drupal development shops need to update their sites with integration into their development and deployment infrastructure and workflow. This should happen just as a separate team member will do this during her work hours. As monitoring and applying updates continuously is time-consuming, especially when you have many sites to support, the need to keep a site up-to-date is high – but the priority is not. That’s why many Drupal sites are already outdated when they go live after they have passed the development cycle. We want to help the Drupal ecosystem handle updates more professionally and more easily. 

In our latest blog post we described a workflow based on the idea of delivering Drupal updates continuously as a fixed part of the development workflow.
Taking the Drupal community's feedback into consideration, we’ve built a service that updates Drupal sites automatically, respecting both development and deployment workflows as well as module, core and theme patches. We call this new service Drop Guard. 

Drop Guard will help Drupal shops, freelancers and site owners to keep their Drupal installation updated and secure – automatically. 
Now, Drupal shops that provide support services for their clients can automate a big part of their service and extend their offer to include 24/7 security patch support – without losing sleep over critical security updates. 
Drop Guard integrates into the deployment workflow, regardless which tools and hosting environment you use. Currently we support a webhook integration for CI services such as Jenkins, Travis CI, Circle CI or PHP CI; SSH integration; feature branch handling to support GIT branching models such as GIT flow; automated patch detection and application during updates. Drop Guard also has some basic built-in deployment features. For small sites, in a few weeks we’ll be releasing a new feature for "FTP only" workflows without the need to have a GIT-based deployment.

The service is currently available at no cost for interested beta testers. If you want to be one of the first to use Drop Guard to automate and professionalize your Drupal update processes, just register at and we’ll contact you for a personal on-boarding. 

Catégories: Elsewhere

InternetDevels: Interview with Zhenya Rozinskiy: about Ukraine through the eyes of the West

lun, 08/06/2015 - 08:11

Planning to outsource web development and other services, customers should think of Ukraine in the first place. This and many other ideas of Zhenya Rozinskiy, a business consultant, who has been living and working in the United States for nearly 25 years now, can be found in our interview.

Read more
Catégories: Elsewhere

LevelTen Interactive: DrupalCon LA 2015 Video: Lullabot Interview

lun, 08/06/2015 - 07:00

Last week’s DrupalCon interview featured friends from Pantheon. If you missed the interview or even our first Roundtable Interview, you can catch the first episode here. The interviews first appeared during our weeklong live broadcast with Periscope and Twitter.... Read more

Catégories: Elsewhere

Midwestern Mac, LLC: Sessions are Live for DrupalCamp STL.15!

lun, 08/06/2015 - 05:35

The organizers of DrupalCamp St. Louis 2015 are excited to announce that the schedule is set for DrupalCamp STL.15; we will have sessions from a variety of presenters on a variety of topics—for both beginners and seasoned veterans alike!

Some of the great sessions lined up include a session on Git basics, the status of Migrate in Drupal 8, content strategy, securing Drupal, improving performance, improving search, Twig, and more! To kick it off, we'll have an awesome keynote from Alina Mackenzie (alimac) about getting involved in the Drupal Community.

Check out the sessions: DrupalCamp St. Louis 2015 Session Schedule.

Register for DrupalCamp STL.15 today, and build your schedule on the site—besides these excellent sessions, you'll get a tasty catered lunch, a comfy t-shirt, and some great memories and networking opportunities on both days of the Camp!

Catégories: Elsewhere

DrupalCon News: Call for Sessions, Training Proposals and Aid Close this Monday!

lun, 08/06/2015 - 04:20

In case you missed it, the call for sessions for DrupalCon Barcelona closes this Monday, 8 June at midnight, Barcelona local time (CET)! If you've submitted your idea already, thank you! If you haven't yet, why not?

Got an idea for a session? Submit your session here:

Some helpful advice to get your session to the top of the list:

Catégories: Elsewhere

S. M. Bjørklund: How to migrate content from drupal 6 to 7 by using Migrate_d2d - Part 4 - field mappings

dim, 07/06/2015 - 18:11

This is probably the last post in this series. I will try in this article to bring it all together. This will also be the most code heavy article. If you are new to migrate and Drupal-to-Drupal data migration, make sure you read and understand the first articles before preceding.

Mapping fields (field mappings)

Migrate have no way of knowing your plans for your Drupal 6 CCK fields or to what fields you are planning to store the data in Drupal 7. Perhaps you do not want or need to migrate all your old data. Source and target field have the same field name and type, but sometime you might want to fix a bad decisions made in the past and reorganize your architecture. Migrate call this field mappings. What ever reason you might have, you will need to share these ideas with Mirate. The basic format is like this:

$this->addFieldMapping('drupal7-field_name', 'drupal6-field_name')

More details are found in the official documentation at

An example of this is found in

$this->addFieldMapping('field_bar', 'field_foo');

This map field_foo (drupal 6) to the cleverly named field field_bar (drupal 7). This is all it take to get a text field like this migrated if you re-run the node migration drush mi Article.

Catégories: Elsewhere

DrupalOnWindows: Making namespaced callbacks work in Drupal 7 (without hacking core and with bound parameters)

dim, 07/06/2015 - 07:00
Language English

What is the best way to prepare for Drupal 8 and make your projects easy (and cheap) to migrate to D8? Start using Drupal 8 programming patterns now as much as D7 allows you to....

I guess that most of you are already doing that - and have done for a few years now - with custom crafted frameworks that, as much as possible, use modern design patterns not stuck in 20 y/o spaguetty code. D7 is spaguetty, your custom modules and code need not to be so.

More articles...
Catégories: Elsewhere

Angie Byron: An analysis of Drupal major version adoption

ven, 05/06/2015 - 22:44

TL;DR We need to ship D8. ;)

I was sent this question today from a co-worker:

"We always talk anecdotally about how Drupal adoption slows before a new release and then picks back up. Do we have any data to support that for Drupal 7 or Drupal 6? I’d love to know the impact of Drupal 8 as well – but not sure that’s possible. Any thoughts?"

This is a great question, but since email is where information goes to die ;), I figured I would copy my response into a blog post as well.

Show me the data!

Since D8 has been in development so long, we don't have enough data showing on anymore since it prunes it after 3 years. :(

Here's a graph I made from trawling through historical data on though (source):

This only goes back to June 2008 which is after D6 came out, so it's not ideal, but we can still glean some useful data out of it.

Drupal 6

Here is a screenshot of the data from just prior to Drupal 7's release in January 2011:

  • In December 2008 there were 77K installs of D6 (compared to 0 in January since it wasn't out yet :)) (77K% increase). This is when D7 was in active development.
  • At the end of 2009 there were 203K installs of D6 (163% increase). This was when D7 was in feature freeze.
  • At the end of 2010 there were 323K installs of D6 (59% increase). This was when D7 was just about to ship.
  • At the end of 2011 there were 292K installs of D6 (9% decrease). This is when D7 had been out for about a year and several key contributed modules were ported.
  • D6 usage has been declining ever since, and is currently at about 135K installs.
Drupal 7

Here is the data from 2011 to today:

  • At the end of 2010 there were 6.5K installs of D7. This is when D7 was just about to be released.
  • At the end of 2011 there were 230K installs of D7 (3438% increase). This is when D7 had been out for about a year and several key contributed modules were ported, and D8 was just beginning development (was mostly D7 bug fixes at this point). Of note, D7 usage eclipsed D6 usage just a few months later (Feb 2012).
  • At the end of 2012 there were 522K D7 installs (127% increase). This is when D8 was nearly done with feature development.
  • At the end of 2013 there were 728K D7 installs (39% increase). This is after D8 was in code freeze.
  • At the end of 2014 there were 869K (19% increase). This is when D8 was in beta.
  • As of last week (mid-2015) there were 984K installs (13% increase). D8 is currently still in beta, with ~25 critical issues remaining before release candidates.

There are a few patterns we can discern from this data:

  • There is an enormous uptick in Drupal usage every new major release (though it's delayed until it reaches a "stable" state, i.e. after enough contributed modules are ported).
  • After that initial year or two of exponential growth, it slows down a lot.
  • The closer the next version is to being released, the slower the growth is of the current version. Generally, this is because people will postpone projects and/or use non-Drupal solutions to avoid incurring a major version upgrade.
  • Usage of the older stable version starts to decline after the newer major version reaches the "stable" state.
Why Drupal 8 will make this more betterer

There are a few enormous shifts coming with D8 that should change these patterns significantly:

  • Drupal 8 is much more fully-featured out of the box than any of its predecessors, so for many sites there is no need to wait on any contributed modules to begin building. Therefore we reach "stable" state (for sites that can do what they need to with just core) at Day 0, not 6-12 months later.
  • A number of key contributed modules that delayed porting of other key contributed modules in D6/D7 (Views, Entity Reference, Date, etc.) were moved into core in D8. So they're available right now—even before release—to build on. And indeed we're seeing other big ecosystem modules (Commerce, Rules, etc.) porting now, while D8 is still in development.
  • D8 will end the 3-4 year "big bang" release cycle. Instead, we'll be doing "small bang" releases every 6 months with non-backwards compatibility breaking feature/API improvements. That means we should hopefully stave off adoption decline much longer, and possibly even sustain the "hyper adoption" rate for much longer.
  • We will still eventually have a D9 "big bang" release (3-4 years from now) with backwards compatibility breaks, but only after it's amassed enough awesome functionality that couldn't be otherwise backported to D8. This will provide us with another "epochal" marketing event that D8 is giving us today (well, soon) in order to drive adoption even further.

Sorry, that was probably Way Too Much Information™ but hey, the more you know. ;)

Tags: drupaldrupal 8acquia
Catégories: Elsewhere

cs_shadow: Drupal Media in GSoC 2015

ven, 05/06/2015 - 19:59
Drupal Media in GSoC 2015

Drupal Media has benefited from Google Summer of Code in the past. Last year one project under Drupal was directly a part of the Media Initiative - Entity Embed module for Drupal 8. I was that lucky student who got this wonderful opportunity to work under the mentorship of Media Initiative leads - Dave Reid (davereid) and Janez Urevc (slashrsm) but that’s a story from the past and you can read more about it in this blog post. In this post I’ll talk about the participation of Drupal Media in GSoC 2015.

3 Projects from Drupal Media, woot!

This year is turning out to be a great one for the Media Initiative in Google Summer of Code. We proposed three projects this year - all for Drupal 8 - and all of those were accepted and we managed to get three outstanding students. We take pride in telling everyone that not only all three students are Core contributors, they have also contributed to one or more Media modules already.

Now I would like to introduce the three students:

  • Jayesh Solanki (jayeshsolanki). Jayesh is a GSoC 2014 alumnus and last year he successfully ported Disqus module to Drupal 8. This year, he will be assisting with the development of Entity Browser. Entity browser is a module for Drupal 8 that tries to provide  powerful and flexible framework for searching & selecting of  entities. If you want to follow the development of this module or project, all the development will be happening in this Github repository. Janez Urevc (slashrsm) will be mentoring this project.
  • Prateek Mehta (prateekMehta). Prateek will be working on developing URL embed module for Drupal 8. This project aims to build a framework for CKEditor which would allow an end-user to  display an embedded representation of a URL, the content of the URL can  be a video, images, rich text or a link. This framework will handle URLs  from various third party sites and essentially replace oEmbed module  from Drupal 7. For more details, refer to this architecture discussion. Currently, the development is happening in this Github repository but this will change soon when we get a new namespace on (don’t worry, we’ll keep you posted). Dave Reid (davereid) and I will be mentoring this project.
  • Yuvraj Singh (root_brute). Yuvraj will be working on develop Embed module for Drupal 8 which will be an API level module. The idea of this project is to abstract  the buttons, embed form, and display plugins from Entity Embed module into a  generic Embed module that can be used by both Entity Embed, URL Embed,  and other embeddables in Drupal 8. For more details, refer to this architecture discussion.  If you want to follow the development of this module or project, all the development will be happening in this Github repository. Dave Reid (davereid) and I will be mentoring this project.

We have high hopes from all these three projects and hope that all of these will finish successfully on schedule and I’m very happy to tell you that all the signs are pretty good so far.

Looking forward to an exciting summer of code.

Tags: Drupal PlanetGoogle Summer of Codegsoc2015gsoc
Catégories: Elsewhere

Drupal Association News: What’s new on - May 2015

ven, 05/06/2015 - 19:35

Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Working Groups.

Organization and User Profile Improvements Explicit Attribution Option for ‘I am A Volunteer’

As a part of our effort to recognize individual contributions to the Drupal ecosystem we’ve slightly adjusted the options available to a user when making an attribution in the issue queues. Instead of simply assuming that a comment made without an attribution to an organization or customer is done by a volunteer - we now allow volunteers to explicitly mark their work as such. Requiring a positive affirmation of the volunteer attribution should improve the accuracy of the data we are gathering about the Drupal ecosystem.

This now means a user can make issue comment attributions in the following ways:

  1. Without attribution
  2. As a volunteer
  3. On behalf of an organization and/or customer
  4. Both as a volunteer and on behalf of an organization and/or customer.

We are seeing a rate of around 30% of issue comments attributed to an organization, customer or as volunteer work. We hope to see that rate increase steadily.

To date, there have also been over 7,000 issue credits that have been awarded to over 2,300 users and 175 organizations. We are looking forward to displaying these credits on user and organization profiles in the month of June and beginning to find new ways to reward our top contributors.

Content Strategy and Visual Design System for

Our collaboration with Forum One on developing content strategy for finished a few weeks ago. While recommendations were published in the issue queues earlier, we decided to use DrupalCon Los Angeles as an opportunity to present the work done and future plans in more detail, and get direct feedback from community members. Check out session slides or video if you want to know more on proposed changes to IA and content strategy.

Right now we are working on a few preparations steps before we can start implementing the changes. The first one of those steps would be a card sort exercise to validate our proposed IA and navigation with users. More blog posts and issues will follow as we move further.

Issue Workflow and Git Improvements

The Drupal Association has been preparing a plan for a new issue workflow on - with some very exciting improvements planned to create a workflow that is both familiar to other repository hosts and yet unique to the needs of the Drupal community.

Perhaps the greatest value of the new Git workflow will be the presence of per-issue repositories and pull requests on issues without forking the issue conversations. will use git namespaces to provide every developer working on an issue with their own branch. Developers will be able to pull in the latest changes from HEAD, or changes from other users’ branches. will be able to summarize the commits, take the changeset and run tests, and help maintainers manage the merge process to push changes upstream.

This architecture will make additional features possible as well:

  • The patch based workflow will continue to work - behind the scenes will create commits on namespaced branches from these patches so that these code contributions will be first-class citizens with the new git workflow.
  • We will be able to provide an inline editor for code in issues - simplifying the workflow for contributions such as code style fixes, documentation, quick typo corrections, etc.
  • We can provide the option to compare any two changes in an issue, giving us automated interdiff functionality.
  • We can identify merge conflicts across issues - to hopefully prevent conflicts across issues before they become too deeply entangled.

This planning work culminated in a presentation at DrupalCon Los Angeles - where the community provided some great feedback, and dove into help us with some architectural components during the extended sprints.

Implementation of the new Issue Workspaces architecture will certainly take some time - but we’re excited to have a plan to work from as we move forward.

Community Initiatives Two Factor Authentication

May saw the initial roll out of Two-Factor Authentication on Users with elevated privileges on now have the option of enabling TFA, and this may become required for all elevated roles in future.

Next we want to make two factor available to all authenticated users on However, before we can allow every user to enable two factor it is important that we create a support policy for resetting accounts with TFA enabled, which is still under discussion.


DrupalCon Los Angeles was a great opportunity to meet with the community and talk about the current state of DrupalCI, and it’s upcoming release.

As of the end of May, DrupalCI is very close to being ready for integration on All of the environments requested for the MVP deployment are functional, and the Drupal Association staff is getting ready to demo the integration with on a development site - at the same time work is continuing on the results site componenet and the test-runner’s results publishing capabilities.

DrupalCI will be rolled out in parallel with the existing PIFT/PIFR infrastructure for at least a few months following initial deployment as a sanity check.

Click-testing has identified several additional issues going into the end of May, and the Association team continues to work on knocking the issues down as they appear. When the current set of identified issues is resolved, we intend to notify the most active translation groups and ask them to perform a final round of testing on the staging environment.

When any issues from that final round of testing are resolved, we will deploy the D7 version of

Revenue-related projects (funding our work) DrupalCons

DrupalCon Los Angeles was a productive and fun event for the community and the Association staff - in every way a success. At the conference we made several announcements about the upcoming DrupalCons, including 2016 locations.

First, we announced the opening of the call for papers for DrupalCon Barcelona, September 21st-25th. The call for papers for Barcelona closes on June 8th.

We then announced our next two conferences, and launched their websites.
DrupalCon Asia will be held in Mumbai in February of 2016.

And the next DrupalCon North America will be held on May 9th-13th, 2016 in New Orleans!

Sustaining Support and Maintenance

The Git servers replacing our existing Git infrastructure are nearly ready for thorough testing and deployment. These servers give us a highly available cluster for, in addition to increased storage capacity, a newer operating system, and dedicated hardware for Git services on

Our Fastly CDN deployment for downloads ( was a success, and soon to follow is the same new architecture for updates traffic ( This new architecture uses dynamic purging to reduce the number of update requests served by our origin servers. It also decreases the latency between packaging a release and serving the update data from a number of minutes to a few seconds.

As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporters, who made it possible for us to work on these projects.

Follow us on Twitter for regular updates: @drupal_org, @drupal_infra.

Catégories: Elsewhere

Acquia: Drupal 8 - 1st product of the PHP-FIG Era

ven, 05/06/2015 - 17:45
Language Undefined

I was happy to talk with two major contributors to Drupal 8 at the same time at Drupal South 2015 in Melbourne Australia. At the time we recorded our conversation in March 2015, Hussain Abbas from Bangalore, India and Jibran Ijaz from Lahore Pakistan had both contributed well over 100 patches to D8. In this podcast we talk about their history in Drupal, open source software as a force for good in society, the benefits of contribution, Drupal as the 1st project of the PHP-FIG era, Drupal 8 for developers, the incredible energy and size of the Australasian Drupal community, and more.

Catégories: Elsewhere

Cocomore: MYSQL - Backup & Recovery

ven, 05/06/2015 - 16:47

Backups are very important for every application, especially if a lot of data is stored in your database. For a website with few updates it is not so important to do backups regularly, you can just take the backup of last week for restoring the site and if there was just one or two updates, you can add them manually afterwards. But if you run a community site with user generated content and a lot of input the topic backup & recovery becomes a lot more important but also complex. If the last backup is from last night you have to consider all the updates that were made in the meantime.

read more

Catégories: Elsewhere

Acquia: Drupal in China

ven, 05/06/2015 - 16:11

That's me: front row, second from the left.

On 14th March 2015, as everyone was coming down from the month-long Valentines Day high, I was in the midst of an exciting Open Source event in Shanghai, China.

With several hundred attendees, the camp attracted people from all over China and the world. Experts and beginners -- in both Drupal and a number of Open Source technologies -- engaged in conversations about CMS, design, language and even solar panels.

Partnering with the Shanghai Barcamp, DrupalCamp China brought together Drupal users, developers, architects, and entrepreneurs from all over China, and the world, to talk Drupal and Open Source.

I was lucky enough to have the opportunity to be asked to speak about Drupal 8 at the event.

As both a Drupal 8 advocate, and someone highly interested in the development of the Drupal community in the Asia Pacific & Japan region (you can read about my Acquia background here), I jumped at the chance to give my take on how the latest version of Drupal will revolutionize open source in China.

Covering the key changes and new features that make Drupal 8 the most exciting version of the framework yet, we took the whistle stop tour of all the features Drupal most needs out of the box:

  • multilingual
  • mobile first
  • inline editing
  • site preview
  • configuration management
  • REST
  • incorporation of other PHP projects

Since this was a Barcamp event, it wasn’t only Drupal community members benefiting from this knowledge, but the entire Shanghai and Chinese technology community.

My friend Sheng Wang has written up a more in-depth report on the day's events, and a broader analysis of Drupal in China. I highly recommend that you check it out.

Both Sheng and I agree: knowing the level of adoption of Drupal in China currently, and looking at the benefits companies are able to take advantage of when laid out against existing solutions, it’s only a matter of time and understanding that will propel Drupal into the forefront -- as it has done in so many other countries.

Tags:  acquia drupal planet
Catégories: Elsewhere

CiviCRM Blog: 16-19 July 2015: NYC Drupal Camp, Aegir Summit and CiviCRM turn-key hosting

ven, 05/06/2015 - 15:44

For those of you in the New York City area, 16-19 July 2015 is NYC Drupal Camp (pronounced "nice camp"), an annual grassroots non-profit conference run by volunteers. The event covers a broad range of topics related to Drupal. As part of the camp, the developers of the Aegir hosting system have organised the first Aegir Summit, 16-18 July.

For those not familiar with Aegir: it is a control panel based on Drupal and Drush to help automate the installation of Drupal, typically in a multi-site architecture (1 code base, many independant sites). With the provision_civicrm module, Aegir can also automate the installation of CiviCRM. This means that with a few clicks, you can create a new database, install Drupal and CiviCRM, configure the web server and optionally manage the SSL certificate. It also helps to automate other tasks, such as backups, upgrades and cloning. Need to create a new testing site for a client? Two clicks and it's ready. If you often create the same types of sites: create a model site, then clone it everytime you need a new instance.

There are also plans to support WordPress in Aegir. I have been working on a prototype that uses the command line tool wp-cli instead of Drush. If you would like to try it, please keep it mind that it is highly experimental and requires patching Aegir 3 (which is still in beta, although there are Debian/Ubuntu packages). The code is available here: hosting_wordpress (please read the 'Readme' file for installation notes).

If you are into Docker and other types of farming, you might find the Aegir Summit interesting as well. There has been a lot of talk about moving Aegir to a more Docker/container-friendly architecture in the next phase, for example.

Long story short: if you are in the NYC area, it would be great to see you there. If you cannot make it and you are interested in any of the above, feel free to leave a comment on this blog post or contact me by e-mail: mathieu at

If you are a CiviCRM hosting provider and you would like to provide a self-serve online form so that your future users can test your services and create a new CiviCRM instance, that's possible too. Hopefully we will have a demo on time for the Aegir Summit, but in the mean time, I will leave the following teaser below (and yes, the sign-up form is a CiviCRM form!) :-)

Catégories: Elsewhere

J-P Stacey: Client/agency relationships at last week's Oxford Drupal User Group

ven, 05/06/2015 - 15:40

Two days ago was June's Oxford Drupal User Group. In a similar manner to our March special event, we were very lucky to get two local speakers: this time round, our speakers were both the main points of contact at their respective organizations: leading Drupal projects themselves, but as part of that having to work with external suppliers, Drupal agencies brought in for their relevant expertise.

Read more of "Client/agency relationships at last week's Oxford Drupal User Group"

Catégories: Elsewhere

Lullabot: Let's Chat About Web Accessibility

ven, 05/06/2015 - 14:57

Join Amber Matz as she chats with web accessibility aficionados Mike Gifford, Chris Albrecht, and Helena Zubkow about what web developers and Drupalistas can do to build more accessible web sites. How has web accessibility changed over the years? Who is being left behind? What are some common gotchas? What are some easy ways to get started testing for accessibility? All these questions and more are discussed in today's podcast. Don't forget to check out the links and resources in the show notes for all sorts of useful things mentioned in our discussion.

Catégories: Elsewhere

Drupal core announcements: Recording from June 5th 2015 Drupal 8 critical issues discussion

ven, 05/06/2015 - 14:07

It came up multiple times at recent events that it would be very helpful for people significantly working on Drupal 8 critical issues to get together more often to talk about the issues and unblock each other on things where discussion is needed. While these do not by any means replace the issue queue discussions (much like in-person meetings at events are not), they do help to unblock things much more quickly. We also don't believe that the number of or the concrete people working on critical issues should be limited, so we did not want to keep the discussions closed. After our first meeting last week, here is the recording of the second meeting from today in the hope that it helps more than just those who were on the meeting:

Unfortunately not all people invited made it this time. If you also have significant time to work on critical issues in Drupal 8 and we did not include you, let me know as soon as possible.

The issues mentioned were as follows:

Alex Pott
Performance issue:
Entity title:
Render cache for views:

daniel wehner, Gábor Hojtsy
Make Views bulk operations entity translation aware:

Lee Rowlands
Ensure #markup is XSS escaped in Renderer::doRender():
Create a php script that can dump a database for testing update hooks:
Views::getApplicableViews() initializes displays during route rebuilding etc.:

Jibran Ijaz
FieldItemInterface methods are only invoked for SQL storage and are inconsistent with hooks:

Alex Pott
Ajax form patch:

daniel wehner

Jibran Ijaz
PHP Script for dumping the database:

Catégories: Elsewhere

Sooper Drupal Themes: Case Study: Glazed Drag and Drop Drupal Theme

ven, 05/06/2015 - 12:32

On June 1st 2015, released the first Drupal Theme that integrates a visual front-end Drag and Drop page builder. I have worked on this project for almost a year, with some breaks in between for client projects that pay the bills. With the release of this theme I have retired all other SooperThemes drupal themes. All new designs will use Glazed theme as a platform. It was a great adventure and I feel proud to show you what I think is the best I could do.

Project Goals 1. Empowering novice users in building high-end responsive websites

I think the Wordpress ecosystem for paid plugins has worked rather well for the WordPress community. Wordpress has various plugins that do Drag and Drop better then any other web application. Now there are also various open source solutions emerging for WordPress. This is an example of how the WordPress community profits from a thriving paid-plugin ecosystem. 

Drupal is really lagging behind in the user experience for building responsive websites. I hope that my Drag and Drop theme will help reverse the trend and attract more young people who are interested in Drupals' flexibility and power as a CMS. In Glazed theme, building grids and setting breakpoints is all done without writing a single line of code:


2. Helping experienced site builders work faster through development automation Amazee Labs employs three back end developers, but nine site builders Michael Schmidt, Amazee Labs

Like many Drupal shops, Amazee Labs has discovered you can provide the most value to your customers by hiring several site builder for every programmer in your team. Automation is good for everyone: you can build more websites in less time and with less training.

Drag and drop web building is not just a gimmick anymore. The tools have evolved to be more powerful, produce better code, and leverage MVC frameworks to create a fluent site building experience that runs mostly in the browser. In Glazed theme this experience is integrated with Views and the block system: you can create highly dynamic pages and even dashboards with Drag and Drop, without loosing re-usability of components you build.


Visual Design and Front-end Architecture

Glazed at the core is architected to be a platform for design. Still it's neccessary that Glazed has a visual identity through which it can demonstrate how good Drupal can look right out of the installer: 

Glazed Drupal Theme Main Demo

There are also several demo packs that demonstrate different niche-designs that are built with Glazed.

Bootstrap to the bone

One of my goals with Glazed theme was for everything to be naturally mobile-friendly. The decision to integrate with Bootstrap 3 seems like an easy one but at first it was not. I was always wary of CSS frameworks because they somewhat limit design freedom, whereas Susy and Zen grids are more sophisticated tools that I had always used in the past. However, the overwhelming availability of Drupal integrations with Bootstrap 3, and the excellent documentation and support that comes from the Twitter Bootstrap team sealed the deal for me.

Glazed theme integrates with Bootstrap on many levels:

  • Bootstrap based Drag and Drop page builder
  • Bootstrap views integration
  • Bootstrap fields API integration
  • Bootstrap block class integration 
  • Bootstrap shortcode library
  • Bootstrap basetheme
  • Bootstrap image style and media integration
  • Bootstrap based Drupal Distribution ( CMS Powerstart )
SASS Bootstrap and a library of CSS Elements

I just love SASS, it makes writing CSS a joyful experience without nasty browser prefixes and futile code repitition. Having an awesome Drag and Drop page builder is boring if you don't have beautiful design elements to drop into your website. Glazed comes with an army of naturally mobile-friendly beautiful elements. To get an idea of what this means take a look at the Motion Box, Time Line and Pricing Table elements in the main demo. These elements can be dropped anywhere in a your webpage and you can edit them without writing a single line of code! This is a one-step process and you get fully customizeable elements.

Icon Box Element

In order to keep track of the design elements and element variations I was coding I felt the need to have more order and logic in the HTML code that marks up the elements. After research in existing CSS namespacing methods I decided on a BEM (block__element--modifier) namespace. 

.stpe-imagebox__figure {   &.stpe-imagebox__figure--akan {     .stpe-imagebox__image {       opacity: 0.7;     }     .stpe-imagebox__fig-caption {       top: auto;       bottom: 0;       height: 50%;       text-align: left;     }     .stpe-imagebox__title, .stpe-imagebox__fig-content {       transform: translate3d(0, 40px, 0);     } Improving Drupal's HTML Output
  • Fences
  • html5_tools
  • Metatag

Drupal does not naturally produce the HTML code that frontend-developers will fall in love with. Fortunately, this is easily fixed with a few add-ons. The first is the Bootstrap basetheme, which overrides most of Drupals' templates. This will not only get you nicer formatting but also cool Bootstrap forms and form buttons. Looks great on administrative pages!

To gain even more control of Drupals' HTML I integrated the Fences and HTML5_tools modules. This adds field-level control of HTML output. I integrated the metatag module for better SEO general future-friendliness. Metatags give search engine and other non-human readers a deeper level of information about the pages and structure of the website.

Drupal integrated Drag and Drop page builder
  • Front-end visual page building
  • HTML5 Based.
  • Pages work fine in regular backend WYSIWYG
  • Blocks, Views integration
  • Refined user experience
  • Naturally mobile-friendly
  • MVC with Backbone and Underscore JS

You may have seen drag and drop builders like Visual Composer in Wordpress. Visual Compores is the best selling Wordpress plugin ever. I think the page builder experience in Glazed is even better. More visual, more editable, less shortcodes. In fact, no shortcodes are used. The Glazed drag and drop builder leverages Backbone and Underscore JS. This means that the document (webpage) is the data. All of the controls and metadata are valid HTML. No shortcodes, no processing needed to render a page after you save it.

The UI is also very user friendly. There is a sidebar that contains visual shortcuts to pre-made beautiful design elements. You can drop them anywhere in your page and edit them, make them bigger or smaller. No problem. The grid system is based on bootstrap. With the greatest ease you can make 3 columns, 4 columns, or anything you can imagine within a 12 column grid system. You can easily control for each row individually at which breakpoint (Screen size) the layout will collapse to a vertical, mobile-friendly stack. 

Views, Media and Blocks integration

Our drag and drop builder is not just a vanity tool. It's integrated with Drupal and makes available all Drupal blocks as well as all views. This allows you to create dynamic, complex pages. For example, on I could easily re-create and improve the customer dashboard with our drag and drop tool. The dashboard contains several views that show download links and documentation for products that are bought by a user. It was no problem to drop the views into the page and then surround them with drag and drop mobile-friendly peripheral content and imagery.

Managing images is done with the Media module. Images can easily be added, used, re-used and then resized using bootstrap-grid image styles. Moreover, our page builder features an awesome animation engine and a number of preset image effects that help you build an immersive experience. My favorite element is the CSS3  Motion Image box:

Motion Image Box Element


Installation Profile Builder
  • Open source CMS Drupal Distro
  • Auto-download custom selection of features and dependencies
  • I plan to add hosting integration in the future

All these modules, libraries and settings need to be carefully set-up to make all this code work. To this purpose I have built an open source Drupal distribution called Drupal CMS Powerstart. I have blogged about CMS Powerstart before so I will skip that and talk about Custom Installation profiles. Drupal distributions are a great way to ship different kinds of Drupal. Unfortunately the way distributions are processed and displayed at is very rigid and not enticing to prospective users. What I built at is a custom installation profile build interface:

Thanks to CMS Powerstarts' autonomous CMS components you can configure a Drupal installation profile that contains only the features you need. Once you make a selection my webserver will download all modues, libraries and patches that are needed for your selected feaures. This service is totally free! The installation profile even contains block/region layout configurations for dozens of free themes, so that all blocks will be in the right region for each installed feature. My server has already built over a hundred custom installation profiles for CMS Powerstart and I'm actually surprised it's holding up. I hope people will also be interested in buying a subscription for Glazed on so that I can buy a new server. I'm not running a trusty but laggy 7 years old AMD Dual core machine.

Community Contributions

SooperThemes loves Drupal and is committed to improve Drupal not only in the premium themes landscape but also as an open source platform. During a year of development for Glazed theme and its backend tools I contributed a number of modules as well as a bunch of patches and the Drupal CMS Powerstart distribution.

Drupal CMS Powerstart

CMS Powerstart is a collection of CMS related components that are enhanced and glued together by the cms_core module. You actually don't need to use the installation profile or cms_core module to use the components, they are all autonomous and you can easily add cms_blog or cms_events to add functionality to any existing Drupal 7 website.

Thank you for reading my case study. If you are still interested to learn more, check out my drupal themes website. I'm also working on a video tutorial that demonstrates the Drag and Drop interface, keep an eye on my blog or twitter or linkedin to get an update for that.



Tags planet glazed drag and drop drupal case study Drupal 7.x
Catégories: Elsewhere

InternetDevels: Implementing Websockets using php (Ratchet library) or Tornado web server

ven, 05/06/2015 - 11:35

Websockets is an important protocol in web development which provides a two-way communication channel between the browser and the web server. Its difference from the traditional way of data transfer is in the fact that the connection is not closed after receiving the answer, but is kept open. Thus, there is an exchange of information in real time, in particular, you can receive notifications from the server without additional requests.

Read more
Catégories: Elsewhere