Drupal is awesome as always! At my first speak to the candidate session on wednesday, not only did I speak for myself, but also got a chance to meet other candidates who are standing for the Drupal Board - Director At Large. Each of the candidates had so much to share about their contributions and were from different cultural background and brought different skills and competencies. This shows how Drupal has grown in the last years. For those of you who could not make it to my first session, some key questions and my responses. Here is the link to the video: https://www.youtube.com/watch?v=b2eiS1Lkk94&feature=youtu.be
We speak to a lot of companies that manage more than one website, often up to a dozen or more. Sometimes it’s worth consolidating a messy digital footprint and bringing the focus back to an all-encompassing central site, but sometimes there’s very good reason to have multiple sites: perhaps a company has diversified into different audience verticals, or maybe they have different divisions or departments that need an independent presence.
In these cases we often find that an organisation’s time and budget is stretched as they try to support and maintain a fragmented digital presence. If they are lucky enough to have sites on the same platform, then bug fixes and security updates may be similar, but will still need to be applied multiple times. If sites have been built on different platforms over the years, then the situation becomes increasingly complex and a raft of suppliers with different specialisms may be needed to hold it all together.
So, what can be done in these cases? There’s often good business logic behind having multiple sites, but if they can’t be sustainably managed, what’s the solution?
We were presented with a similar challenge when we started working with Bath and North East Somerset Council’s world-renowned Heritage Services division. They had a portfolio of five websites promoting their key heritage attractions, with the Roman Baths website as the flagship. The Roman Baths site was by far the most popular and most complex of the five, unsurprisingly since it showcases one of the most popular tourist attractions in the UK. The other sites were smaller and contained less functionality, but each served a similar purpose: to promote a heritage attraction in Bath.
The key to developing a sustainable digital footprint was to shift the way we thought about the problem. Rather than thinking about five websites, we began to think about a single website with five different ‘facades’. Since the sites shared a lot of key functionality, we wanted to create a central code-base that would power all five sites, but still allow each to have their own individual ‘look and feel’, web address, content and functional variations. The Drupal ‘multi-site’ approach allowed us to do just that.
We launched the five sites in quick succession, starting with the ‘master’ Roman Baths site. The subsequent sites were developed at a fraction of the cost of the first, as the functional elements were already in place and thoroughly tested. Each of the smaller sites just needed a new theme and some configuration and they were ready to launch.
Maintaining the sites has been a breeze, since module upgrades and security patches need only be done once to apply to all five sites. The client has also taken advantage of the built-in flexibility of the system to launch a sixth site. Building it into the Drupal Multi-site system means it’s been incredibly cost-effective to launch and even more-so to maintain.
The six sites are hosted on Acquia’s market-leading enterprise cloud platform, where the costs are calculated ‘per codebase’ rather than ‘per site’, So again it’s a win-win, with the client enjoying Acquia’s unrivalled SLA and support across all six sites for a single fee.
The Multi-site approach certainly worked for Bath and North East Somerset Council, but it has plenty of potential applications. Online publishers that deliver numerous ‘news’ sites in different verticals would perhaps benefit most, but it could equally apply in Higher Eduction, Public Sector or NGO space. Sure, there are situations where the multisite approach wouldn’t work well, like where the sites has significant functional differences, or where the requirements are likely to diversify in future, but in the right circumstances a single code-base to power multiple sites can save a lot of time, budget and frustration.
Written by: Dan McNamara, Managing Director
Microserve is a Drupal Agency based in Bristol, UK. We specialise in Drupal Development, Drupal Site Audits and Health Checks, and Drupal Support and Maintenance. Contact us for for further information.
I have revised and improved the training in preparation for DrupalCamp next week. I've incorporated some feedback, added a bit of theory, and included more practical examples. Join me and level up your PHP development skills in this 1 day course.
Build Your Own PHP Framework.
Learn modern PHP practices and see the benefits first hand via practical examples. Learn object oriented design and how to apply design patterns.
There's a lot of old PHP code and information around on the web. With the massive improvements in PHP in recent years, a lot of this information is wrong and out of date. In this course I will be focusing on only modern, state of the art PHP.
Moving from Drupal 7 to Drupal 8 means adopting modern, object-oriented, PHP practices. Drupal 8 has gone through a process of "getting off the island" and embracing the wider PHP ecosystem. We, as PHP developers using Drupal, can improve our own processes by doing the same.
Building your own framework is a great way to learn the fundamentals of modern PHP. Regardless of your choice of framework, this will make you a better developer. A similar foundation of components underlies Drupal, Symfony, Silex, and Lavavel.
- Learn framework decoupling techniques.
- Write better code by avoiding unnecessary complexity.
- Use Domain Driven Design to tackle complexity and design better solutions.
- Go beyond MVC and start to explore other design patterns such as command bus and repositories.
- Learn simple strategies you can immediately apply to develop better code.
- Understand the components at the core of Drupal 8, many other PHP frameworks and popular PHP apps.
- Digestible 40 minute sections interspersed with practical workshop where you get hands-on experience.
You will need a basic knowledge of PHP and a laptop that can run PHP. You will leave with a better understanding of the principles behind modern PHP and Drupal 8.Tickets available here.
£295.00 or £95.00 concession tickets for sole traders, students and charities. The training will be on Friday March 4, 2016 at City University London.
The most installed module in Drupal “Views” is now available as the core modules of Drupal 8. Now you don’t have to search for the latest version of views separately.
For the 1st timer, Views allows you to generate dynamic query using easy to use UI. That's the simple explanation, but it doesn't give the module the credit it deserves.
For instance, you can create a page (/latest-news) which displays all the latest content by bundle type and sorted by posted date. Using the module, you can display content in a block, table or formatted structure.
In this article, we'll continue building our new site by adding up few more custom views. We'll create a view page to showcase news on homepage, and a "Recent News…
Today, after over 8 years, we say thank you and goodbye to Drupal 6.
Drupal 6 is now officially "end-of-life".
Drupal 6 launched in 2008 and was the backbone behind many of the projects that made Drupal famous. At its height, there were over 300,000 Drupal 6 sites.
Below you can see Drupal 6's popularity during its first 3 years of Drupal 6. The purple line shows Drupal 6's growth and the green line shows Drupal 7.
Drupal.org frontpage posts for the Drupal planet: Drupal 8.0.4, 7.43, and 6.38 released, and Drupal 6 reaches its end of life (EOL)
Drupal 8.0.4, Drupal 7.43, and Drupal 6.38, maintenance releases which contain fixes for security vulnerabilities, are now available for download.Download Drupal 8.0.4
Download Drupal 7.43
Download Drupal 6.38
Upgrading your existing Drupal 8, 7, and 6 sites is strongly recommended. There are no new features nor non-security-related bug fixes in these releases. For more information about the Drupal 8.0.x release series, consult the Drupal 8 overview. More information on the Drupal 7.x release series can be found in the Drupal 7.0 release announcement, and more information on the Drupal 6.x release series can be found in the Drupal 6.0 release announcement.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 8 and 7 include the built-in Update Manager module, which informs you about important updates to your modules and themes. Drupal 6 has reached its end of life (EOL) and will not get further updates.Bug reports
Drupal 6 has reached its end of life (EOL), so it will not receive further bug fixes or official releases.Change log
Drupal 8.0.4, 7.43, and 6.38 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisories:
To fix the security problem, please upgrade to either Drupal 8.0.4, Drupal 7.43, or Drupal 6.38.Update notes Planet DrupalDrupal version: Drupal 6.xDrupal 7.xDrupal 8.x
Image styles are one of many great features Drupal ships with. This part didn't really change from functional point of view in Drupal 8. It does a great job, but if we'd be limited to image effects that ship with core it would be hard to cover more complex use-cases.
The image style system is luckily pluggable (like most of Drupal:)), which allows contributed modules to provide additional image effects.
Image effects is a new module for Drupal 8 as it didn't exist in previous versions. It's purpose is to bring most of contributed image effects under one roof. This makes a lot of sense since it prevents fragmentation and makes effects easier to find. Module is still in alpha, but it already ships with many useful effects.
It tries to support both the GD toolkit from Drupal core and the ImageMagick toolkit, but there may be effects that are not supported by both of them or that provide different results with different toolkits.Effects Auto orientation
This effect will read EXIF, check if the camera recorded orientation information and rotate the image accordingly.
Although most modern browsers do support the orientation tag, the information may get lost or become incorrect by other operations. So, to support all browsers and prevent rotation errors, it is better to start each image style with this effect.Brightness
Supports changing brightness settings of an image. Also supports negative values (darkening).Colour shift
Colour shift allows us to colourize and image with a colour of choice.Contrast
Supports increasing or decreasing a contrast of the image.Canvas
Allows us to define a canvas and position the image on it. We can also set the background colour.
On the example image I used canvas that is larger than the image and it's background colour set to black.Set transparent colour
This effect is useful when dealing with transparent GIF images. It allows us to define the colour that will be used instead of transparency.Strip metadata
Strips entire EXIF metadata from the image. GD does this by default, which means this effect will only be useful if ImageMagick image toolkit is being used.Watermark
Allows us to place a semi-transparent image anywhere over the original.What is next
We are actively working towards next alpha release. There are patches for two more effects ready to be reviewed: Background and Text overlay. When this two patches land we'll be able to release second alpha, which will most likely be followed by the first beta release.
We urgently need help with reviewing the two patches. This is a perfect task for anyone that is trying to get involved and looking for a something fairly simple but still fun.Who is behind the module?
A lot of people contributed. Specially if we consider that most of the effects came from the other Drupal 7 modules like ImageCache actions we're talking about tens or event hundreds of contributors.
However, most of the recent work has been done by @mondrake. If you meet him at any of the community events please buy him a beer.About me
I (Janez Urevc - @slashrsm) am one of the architects and maintainers of the media ecosystem for Drupal 8. If you like what I am doing please consider donating to my Bitcoin address: 1Xqe6gYWEbF1iKsy3Mr5SbAyebNyucj5t.
Together with some colleagues I'm building a small team of professionals that will be providing top-level consulting, training and development related to media in Drupal 8. If you're interested or you'd like to work with us please get in touch.slashrsm Wed, 24.02.2016 - 18:18 Tags Drupal Media Enjoyed this post? There is more! When will media be ready for Drupal 8? A lot of exciting Drupal 8 media news! Entity browser got configuration UI
Replace old or broken links with a new url in your Drupal site, by using Redirect module.
In this tutorial, I'm going to show you how to create redirections with a few clicks. Let's start...
Part 4 of a series investigating what options you have with your Drupal 6 site as EOL has now come. We discuss whether Drupal 7 or Drupal 8 make sense for your site. Continue reading…
Acquia Developer Center Blog: Multisite Governance and Other Delivery Issues Related to Managing Many, Many Sites
An interview with Will Eisner, Senior Director, Product at Acquia. Will’s primary focus is on Acquia Cloud Site Factory, which helps organizations create and manage many sites, from a dozen to thousands.
Also sitting in on the interview, via conference line, was Sonya Kovacic, a Junior Product Manager at Acquia who also works on Site Factory. Sonya's comments are featured in Part 3 and Part 5 of this series.Tags: acquia drupal planet
Updating modules in Drupal 8 is similar to updating modules in Drupal 7 - the drush pm-update (drush up) command still works, but there's a new "gotcha" that you need to look out for when updating modules that work with entities.
Sometimes, after updating modules that interact with entities, you'll see a "Entity/field definitions: Mismatched entity and/or field definitions" error on your site's status report (admin/reports/status).
In the screenshot above, this error was generated by updating the Inline Entity Form module from its alpha4 version to the most recent -dev version (the site also uses the Scheduled Updates module). As long as a mismatch is present, the fields listed in the error will lead to unpredictable results.
Neither rebuilding caches nor running cron will fix this issue ("drush up" doesn't automatically run this command either) - for these types of errors, the drush entity-updates command is what you're looking for.
Once this command is run, your status report will look something like this:
This is just one more reason why checking your site's status report page after updating modules is always a good idea.
Using Vagrant to manage virtual machines in a development workflow has become a life-saver and standard practice in many cases. Running a project server inside a virtual machine sidesteps the majority of the custom configuration that used to be required on a developer’s machine, but at the same time it introduces a new machine to connect to and manage.
This episode Bob is out on assignment so we have Matt Davis in his stead to talk about our upcoming invasion of Sandcamp on February 24th and then Florida Drupal Camp on March 5th. Mario has the latest blog posts from Mediacurrent.com, there will be actual content in the Maildrop, Ryan brings us home as always with The Final Bell.
A fundamental part of ThinkShout’s philosophy and business is to not only use great open source tools, but to actively give back to the open source community. The most recognizable part of that contribution is in the form of Drupal modules: over 60,000 Drupal sites run on ThinkShout technology! This strategy has been a huge win for our clients, who get features, bugfixes, and security updates from the community because they are sharing code. We benefit from this work as well, as it enhances our profile in the community and helps us generate leads for new projects. Of course, the vast majority of these sites are built on Drupal 7, which released in the same month that ThinkShout was founded.
The exciting and much-anticipated release of Drupal 8 has given us a lot to think about. Internally, we’ve been running a Drupal 8 "book club" to give our development team a chance to dive in and figure out what’s going on with D8. While we’ve bathed in the glories of Composer, Twig, and YAML files galore, we’ve also had a chance to start upgrading a few of our favorite modules to Drupal 8!
With support from the incredible folks over at MailChimp, we’ve already got a working release of the MailChimp integration module for Drupal 8, and are hard at work on the integration with Mandrill, MailChimp’s awesome transactional email service, which may have a Drupal 8 release before this blog post goes live.
This is a great start, but it’s really only the tip of the iceberg: ThinkShout has about 50 modules released for Drupal 7! As much as we’d love to dive in and update all of them for Drupal 8 today, that’s not particularly practical. To better focus our work, I analyzed some of these modules so we can prioritize them and look for opportunities to work with our partners and clients to get the most useful, popular, and important modules upgraded to Drupal 8 first.
Of our 50 modules, we started by de-prioritizing anything that was:
Extremely narrow in purpose (Entity Reference Plus Data)
Blocked by another module’s Drupal 8 development (Apache Solr Geo, lots of others)
Offers modest functionality replaceable by custom code (Footer Message) or
Just not seeing much usage (Instagram Realtime)
That left us with around 10 projects, among them MailChimp and Mandrill, which we were already working on. We wanted to pick a manageable number of these remaining modules to get started on.
Based on community usage, the priorities of our clients, and perceived usefulness, it was clear that the Registration module belonged on this list. The story of Registration’s development is connected to the story of ThinkShout’s fledgling years and open source philosophy, so it’s an added bonus that Registration will be part of our early push into Drupal 8.
ThinkShout has also carved out a reputation as experts in the CRM world, with RedHen, our leading Drupal-integrated CRM, and the Salesforce Suite, a fabulous tool for integrating Drupal sites with Salesforce. Though these modules don’t have the 5-digit usage numbers that Registration or MailChimp have, they still have lots of users who are very engaged, and are central to the needs of our clients. We added them to the top of the list for Drupal 8 consideration.
In thinking about the rest of our modules and the nature of our work, it became clear that these three projects really stand out from the rest: they are our "Big 3", and we set about creating a roadmap for developing them on Drupal 8.
You can already see the beginnings of this work! At our team sprint on February 11, we put together an outline for bringing RedHen to Drupal 8, and pushed the first commits to Drupal.org.
These are our sprint faces!
As of February 11, all of the Big 3 have nominal Drupal 8 branches.
As we kick off four Drupal 8 sites in the first part of this year, we will be working with our clients to bring Registration, RedHen CRM, and Salesforce Suite to Drupal 8. All three should update beautifully, as they are built on top of Entity API, which is part of Core in D8.
We will also be focusing our internal open source contribution hours on these three projects to kickstart their jump into the Drupal 8 sea. If you’re looking for awesome CRM or registration systems for your Drupal 8 site, fear not! They are on their way.
We have two Drupal 8 sites utilizing ThinkShout core technologies scheduled for launch this summer, so look for a release of RedHen in the spring!
Our next round of prioritization will depend significantly on the progress of Commerce solutions in Drupal 8: once that landscape settles, we have some projects that will jump up that priority list, including:
Registration Commerce, our favorite paid registration solution
RedHen Donation, our CRM-integrated, single-page donation tool
So if you’re a fan of our Commerce integrations, or Add to Cal, or even little Bean Entity View (I know I am): stay tuned! We love these tools, we love that you’re using them, and we look forward to bringing you even more awesome stuff for Drupal 8 than we have for Drupal 7!
Our Drupal developers will continue sharing Drupal 8 tips with you. We have published articles so far about configuration in Drupal 8, general tips on Drupal 8 development, and on using Twig in Drupal 8.Read more
The monthly security release window for Drupal 6, 7, and 8 core will take place on Wednesday, February 24.
This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 6, 7, or 8 branches, only that you should watch for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).
February 24 is also the end-of-life date for Drupal 6, so this will be the last security release window for Drupal 6.
There will be no bug fix or feature release on this date. The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, March 2, 2016. The next scheduled minor (feature) release for Drupal 8 will be on April 20, 2016.
Thank you! Drupal Association and Drupal Indian Community Members for putting together the most fabulous experience for the Drupal enthusiasts of the community. The Venue sponsor IIT Mumbai needs a special mention.
Our Journey @DrupalConAsia, A short message from each of our Drupal Development team and their learning and contributions at DrupalConAsia