All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
myDropWizard.com: We've made 99 Drupal 6 Long-Term Support releases... what does that mean for Drupal 7?
In that time, we have made 99 releases (both Drupal core and contrib) for D6LTS!
Most of those were security releases, but there were also a handful of bug fixes, and most recently, updates to support PHP 7.2. (FYI: As of a couple days ago, PHP 5 has also reached it's End-of-Life (EOL) - do you have a plan to update to PHP 7.1 or 7.2?)
When we were first talking to potential customers about D6LTS, I remember many people doubting that we'd be releasing anything at all!
They'd say something like "Drupal 6 has been around so long, aren't all the security issues shaken out by now?" Almost 100 releases later, and I'd say there was plenty to be done. There still is! :-)
In this article, I'm going to look back on Drupal 6 LTS, and also look forward to what that may mean for Drupal 7 extended support after it reaches its End-of-Life.
Morpht: Drupal and Composer: Part 3 — Converting Management of an Existing Drupal 8 site to Composer
As any developer working with Drupal 8 knows, working with Composer has become an integral part of working with Drupal. This can be daunting for those without previous experience working with command line, and can still be a confusing experience for those who do.
This is the third post in an explorative series of blog posts on Drupal and Composer, hopefully clearing up some of the confusion. The four blog posts on this topic will be as follows:
- Part 1: Understanding Composer
- Part 2: Managing a Drupal 8 site with Composer
- Part 3: Converting Management of an Existing Drupal 8 Site to Composer
- Part 4: Composer for Drupal Developers (Coming Soon)
So you’ve worked your way through parts one and two of this series, and you now understand what Composer is, how it can be used to work with Drupal 8, and how to start a new Drupal 8 project using Composer. But, you started your current project without using Composer, and want to switch to managing your project using Composer. Where do you start? This article will discusses a few strategies behind converting your existing system to Drupal. Fortunately some automated tools exist for converting existing sites to Composer, and in the situation that neither of these tools work, an overview is provided on how to manually convert an existing site
But, before moving on to any of these methods...
Take a backup! As this process will be destructive to your system, make sure you take a backup of your file system, and take a backup of your database. Then go and check to ensure that you have a full backup of the file system, and a full back up of the database.
If you skip this step, or do not do it properly, you may end up with an entirely broken system, so don’t skip this step.Method 1: Composerize (Composer plugin)
Composerize Drupal is a Composer plugin that has been built to convert existing Drupal installations to use Composer. Instructions are on the download page. If this method doesn't work, you can try the Drupal Composerize module:Method 2: Composerize (Drupal module)
The Composerize module is a Drupal module that is built to convert existing Drupal installations to use Composer. At the time of writing, this module has the following disclaimer on the page:
If this method doesn't work, you'll likely have to manually convert your site.Method 3: Manual method
If the above steps fail, your last option is to convert your installation to using the Drupal Composer Template manually. Note that pretty much every system will be different, so these instructions are an overview of the end goal, rather than a complete set of steps that will convert your system. There is a good chance you’ll run into issues along the way that are not covered here, so make sure you took that backup!
Converting a system to the template requires achieving the following goals:
- Setting up the file structure of the system to match the Drupal Composer Template
- Delete old Composer files
- Add the Template file system to your Drupal system
- Set up the configuration directory and the private files directory
- Set up your profiles, modules and themes to be managed by Composer
The Drupal Composer Template is set up to manage the directory above the webroot, as well as the webroot. The webroot is located in the [PROJECT ROOT]/web folder. Therefore you will need this structure:
- / - Project root. Contains various scaffolding files such as composer.json and composer.lock, as well as the configuration export folder, and the webroot folder
- /web - The webroot. Contains all Drupal core, profile, module and theme files.
You'll need to set up your Drupal installation to match this structure, and make sure that the server is set up so that the web root is at [PROJECT ROOT]/web.
Note: Some servers require the webroot to be in a directory with a specific name, such as public_html, or www. In this case, you can try setting up symlinks from the required directory name to the /web directory, so that, for example, [PROJECT ROOT]/public_html is a symlink pointing at [PROJECT ROOT]/web. Your Drupal files will then reside in the /web directory (satisfying the Drupal template), and also be accessible at /public_html (satisfying the server requirements). If this does not work, another option would be to edit the composer.json file (which is added in step 3) and change any paths that point at the /web directory, to point at the directory name you are actually using.Step 2: Delete old Composer files
I'll say it again, because it needs to be said, make sure you took that backup in step 0!
If any of the following files or folders exist in your installation, delete them. Note however that you may want to save the composer.json file for reference if you've manually added any libraries into your existing installation using Composer.
- [PROJECT ROOT]/vendor directory
- [PROJECT ROOT]/composer.json file
- [PROJECT ROOT]/composer.lock file
- [PROJECT ROOT]/web/vendor directory
- [PROJECT ROOT]/web/composer.json file
- [PROJECT ROOT]/web/composer.lock file.
Go here, click 'clone or download' and download the .zip file (note - or clone the Git repository if you prefer)
- Save/move the zip file into the project root folder (the directory above the 'web' folder you created above). You can then unpack it using the following command. Before this step, the file /composer.json should not exist. After this step, if you've done it correctly, this file will exist.
tar -zxvf [FILE] --strip-components=1
- Run the following command from the project root folder. This command will Install the Composer dependencies as well as create the /vendor directory.
- Run the following to ensure your database is up to date, and caches are cleared.
drush updb; drush cr;
This next step is optional, however it will make for a more secure system. First, the following directories need to be created if they don't already exist:
- [PROJECT ROOT]/config/sync
The first folder is where exports of the Drupal 8 configuration system will be exported to. The second folder is the private files folder. Creating both of these directories as siblings to the webroot adds security, as the files are not in a web-accessible location. The next thing to do is tell the system of the location of these files. This is done by declaring the folder paths in settings.php. You can do this by adding the following two lines to the bottom of settings.php:
$config_directories['sync'] = '../config/sync';
$settings['file_private_path'] = '../private';
After this, clear the registry (drush cr;). You can confirm that the configuration directory was properly set by running drush cex sync, and then checking that there are .yml files in the [PROJECT ROOT]/config/sync directory. You can confirm that the private files folder was properly set by going to Admin -> Configuration -> Media -> File System, and confirming that the private files directory is listed as ../private.Step 5: Set up your profiles, modules and themes to be managed by Composer
The final step is to set up Composer to manage Drupal profiles, modules and themes to be managed by Composer. The Drupal Composer Template tracks Core by default, but needs to be informed of the rest of your code. Note that if you do not want to use the most recent version of these profiles/modules/themes, you will need to alter the commands below to set the version you want to install.
Drupal profiles, modules and themes can be installed with the following command:
composer require drupal/[PACKAGE NAME]
For example, if you were using the Administration Toolbar module (admin_toolbar), you would run:
composer require drupal/admin_toolbar
After you have done this, ensure you are up to date with a DB update and cache clear:
drush updb; drush cr;
At this point, your system should be converted to the Drupal Composer Template, with contributed code being managed by Composer.Summary
This article looks at converting exiting Drupal 8 sites to being managed by the Drupal Composer Template. Doing this can potentially be automated using the Composerize Composer plugin or the Composerize Drupal module. In situations where this does not work, the manual directions in this article can be used as an alternative.
In the next and final part of this series, we'll look at how Drupal developers can integrate 3rd party libraries into their custom Drupal profiles, modules and themes.
This module extends the 'Rules' module for Drupal 8.
Today the 'Rules' module has the following restriction:
If you create a new 'User' in a 'Rule' then you can't get access to its custom fields in this 'Rule'.
This module solves this problem.
The example of using:
You can create new users with 'Rules' and populate their fields with a data obtained using 'Webform' module.
The Drupal we all know and love is evolving. The learning curve is shifting, the development paradigm is different, and the community, not only the software, is more ambitious. We felt it was time to build Drupal.tv as a thank you to the wider community. Drupal.tv is live as of January 1st, 2019!
From the community spotlight on Drupal.org: “He's the fellow that is dashing from room to room before the first session begins to set up the AV equipment and checking in with presenters making sure they all "push the red button". Because of him, we are all able attend the sessions we miss while busy elsewhere. He is personally responsible for recording over 800 sessions and donating countless hours of his time.”
Hear his thoughts on the unofficial Drupal recording initiative ( https://www.drupal.org/association/blog/introducing-the-unofficial-drupal-recording-initiative ).
Thank you, Kevin!
A Tweet to start it all
In Oct 2018, Rachel Lawson (@rachel_norfolk) tweeted: “It strikes me that creating a “DrupalTV” site, collating all YouTube session videos, would be possible in Drupal core these days. Tagging, searching, the lot. Could be a fun project? I’m sure one of our hosting providers would help…”
As fate would have it, Ashraf Abed (@ashabed) of Debug Academy was looking for the upcoming semester’s class project and came across the tweet. Debug Academy always does a real, new project in class as it’s the best way to learn programming and to build credibility.
Yes, newbie Drupalers built this site.
Drupal’s learning curve is shifting. The focus of many ongoing core initiatives is improving developer experience, and not only for senior programmers.
This project was built (& continues to be built) by a team of new Drupal developers, led by one Acquia “Grand Master” certified Architect (Ashraf Abed, Debug Academy’s CEO).
The backgrounds of the team include (but are not limited to):
- 4 experienced backend developers with 0 Drupal experience
- 1 experienced front end developer with 0 Drupal experience
2 self-taught web developers with 0 Drupal experience
- Former career: Library and Information Science
- Former career: Teacher (PHD in history!)
- 2 self-taught with light site building experience in earlier versions of Drupal
- 1 Drupal Grand Master / Architect (Ashraf)
To illuminate this a bit more: Ashraf was not allowed to contribute any code on the project during the semester, which ended on December 22nd, 2018 (1 week before this site’s launch). That is to ensure that the new developers gain proper experience building the project. So the majority of this project truly was built by non-Drupal developers. We’ll share more about those developers in an upcoming article, with their permission.
And if you’re thinking “the experienced backend developers did most of the work”, that simply is not the case. The majority of the work on the project was contributed by the rest of the group.
Furthermore, as is the naturally occurring case with most Debug Academy semesters, the development team was highly diverse. Over 70% of the team members come from backgrounds that tend to be minorities in our field, and we were lucky to benefit from their ideas and expertise.
What’s now and what’s next?
Kevin Thull provided us with a list of DrupalCamp videos, of which we’ve imported 100%. Thanks to Wendy Abed, Kevin, and Ashraf for importing the DrupalCamp and DrupalCon videos. We’re at over 3,500 videos!
In the near future, we will also add free Drupal training videos created by various providers. All videos on this website will always be free.
You may have noticed some videos are tagged with conferences. In fact, all videos are tagged with conferences, but you can only see the published ones.
We ask DrupalCamp organizers to reach out so that they can populate their own conference pages. Debug Academy’s next cohort will built out the conference (meetups, Drupal Camps, Drupal Cons) functionality on the website to make conferences (past & future) easy to find.
Searching / Sorting / Filtering
The site’s search is powered by the Search API module(s). The plain text search actually works quite well - search for a conference name, a topic, etc, and you will find all videos from that conference/topic.
As part of next semester’s project, we will be tagging talks with topics and speakers, which will enable us to use faceted search on the website.
We want this site to be globally useful. We plan to import video captions as well as and enable the multilingual features available in Drupal core. And if you are recording Drupal conferences in your country, reach out to us with your youtube playlist!
Video submissions are open to the public! Approved content administrators will have the ability to import entire playlists from youtube, but anyone can import an individual video! Anonymously submitted videos will be created as “Drafts”, and our team of alumni and approved moderators will approve appropriate videos (thanks, Drupal core content moderation!)
Debug Academy students and alumni will continue to build and maintain the website as a non-profit project for the Drupal community. We will periodically share articles about what new Drupal developers were able to build using the website.
After next semester’s project, we may reach a point where smaller Drupal Camp events do not need to create/maintain their own website. Instead, they could simply create a conference page on Drupal.tv and use their time on higher value initiatives, like running a great conference, as usual! :)
How can you help?
At the moment, we have plenty of development capacity for the project, and we would like this project to continue to enable graduates of Debug Academy to land their first full time jobs as Drupal developers. You can help by spreading the word!
Follow us on twitter @drupaldottv, sign up for our newsletter (in the footer) to hear about new videos and articles, and simply share this website to the wider Drupal community!
We'll be reaching out to our alumni to do a separate piece on them with their inputs and permission. We launched on New years, but it turns out that's an inconvenient time for many contributors. Who would've known?!
And I’d like to give a special shout out to the founder of Drupal, Dries Buytaert, for allowing us to use the domain drupal.tv for this project!
Happy new year, everyone!
A lot of my work over the last few years has been working on migrations between various versions of Drupal. That usually means that I need to configure a local Drupal development environment with more than one database. And although this is relatively easy to do with Lando, I often have to look up how I did it before. So, I figured I should write it down and share with everyone else at the same time..lando.yml
Adding a database to an existing Lando environment is as easy as adding a few lines to the .lando.yml file and restarting.
Often, your .lando.yml file might already have configuration in it. If the services line already exists, just put the new configuration underneath with the correct indentation. You can see examples of more complex configuration files at any of the links in the previous paragraph.settings.php
Now, you will need to tell Drupal about the new DB. To do this, go to the command line and type lando info. In the output, you should see something like this:
"port": "not forwarded"
With that information, you can add the new DB configuration to Drupal's settings.php file.
$databases['old_db']['default'] = array (
'database' => 'database',
'username' => 'mysql',
'password' => 'password',
'prefix' => '',
'host' => 'legacy',
'port' => '3306',
'namespace' => 'Drupal\\Core\\Database\\Driver\\mysql',
'driver' => 'mysql',
Note that, by default the host name is going to correspond to the name of the service/container and will not necessarily be the same as the name of the database (or the name of the Drupal DB alias, for that matter). In other words, you should find the host and port values in Lando's internal_connection array. If, for some reason, you need to have a custom database name, credentials, port numbers or something else, you can refer to the links above.Tags:
With the year winding down the month was a little quiet, but we still got some good contributions going.Client sponsored
Thanks to our awesome clients for giving us a chance to help make open source software better for everyone.
- Bayo Fodeke rerolled a patch for Multiple Selects module to fix an error that can show.
- Chris Runo came up with a workaround to allow the Permissions by Term module to limit it per vocabulary.
- Dan Polant suggested an alternative solution for making sorts work in config entity queries and uploaded a patch to improve the UI on the Lingotek Translation module.
- Mark Casias uploaded a fix for using Devel with Admin Toolbar.
- Melissa Bent created a fix for a bug in the Tamper module and worked out a fix that allowed the CodeCoverage library to properly load its dependency files.
- I created a patch for Baidu Push to indicate that the Language module is actually required, a patch for Guardr to add back in the project prefixes, and created a new Drupal.org Links module.
Mediacurrent provides some extra time during the week for folks to scratch their own itches, and sometimes people triage issue queues instead of watching football on TV :-)
- Melissa provided us some examples for using nested menu items on the YAML Content module.
- Stephen Lucero continued working on improvements for his Switches module.
- I helped reroll and tidy up some patches for the Context module, triaged the Metatag module and Date module’s issue queues a bit, and released Search & Replace Scanner v7.x-1.1 and Panels Everywhere 8.x-4.0-beta1
A little light this month, but there are still two good blog posts from our team.
- Tara Arnold introduced the many sessions that Mediacurrent staff will be presenting at DrupalCon Seattle 2019.
- Becky Cierpich took a step beyond simple localization into the greater design considerations that are necessary for a multilingual site.
We squeezed in four Contrib Half Hour meetings into the month, despite the company being closed for Turkey Day.
November 1st - Issues lab
November 8th - run-tests.sh
November 15th - Q&A
November 29th - Testing lab
Lots of folks were working on their presentation proposals for DrupalCon Seattle 2019. see Tara’s blog post for details. There are also several events coming up soon that we’ll be attending, including DrupalCamp NJ and Florida DrupalCamp in February and then NERDSummit in March.Stay warm!
That’s it for this month. Hope everyone in the Northern Hemisphere stays warm, everyone in the Southern Hemisphere enjoys their summer, and the folks in the middle don’t brag too much!
Anyone familiar with the Drupal core development lifecycle will know that presently the Drupal community supports two major versions at any one time: the current major release and its immediate predecessor. This means that at ComputerMinds we are currently helping our clients support and develop both Drupal 7 and Drupal 8 sites. So the obvious question that we get asked is ‘when is it time to upgrade’?
We can’t properly answer this question without bringing the next major release, Drupal 9, into the mix. So let’s look at the development timeline for these three versions. According to a blog post by Dries both Drupal 7 and 8 will have an end of life of no later than November 2021 with Drupal 9 being released roughly a year earlier in June 2020 to give site owners enough time to move over to Drupal 9. It is worth noting that from November 2021 only Drupal 9 will be supported. Dries outlines these dates with a whole bunch of details in this blog post.
Historically, migrating between major versions has been a considerable chunk of work as major versions aren’t backwards compatible; however, the good news is that migrating from Drupal 8 to Drupal 9 should be a very straightforward process - so long as you’ve kept your Drupal 8 site up-to-date! This is good news for anyone that’s already taken the plunge into the world of Drupal 8 as the migration process shouldn’t really be any more involved than a minor upgrade. This is because the only real changes will be to remove deprecated code and update dependencies, such as Symfony (Symfony 3 has an end of life of November 2021, hence this date being cut off for support for Drupal 8).
For site owners still using Drupal 7 the question of when to upgrade is slightly more complicated. Do you wait for Drupal 9 and skip Drupal 8, or should you upgrade now? As previously mentioned we can be reasonably confident that upgrading from Drupal 8 to Drupal 9 will be a straightforward process, so we don’t need to worry about having to redo lots of work a couple of years down the line if we do migrate to Drupal 8 now. So the question of when to migrate really varies depending on your current circumstance and preference.
Some site owners will want to benefit from new functionality added in Drupal 8 so will want to upgrade their Drupal 7 sites as soon as possible, whilst obviously factoring in how difficult and expensive the migration will be. Others will be perfectly happy sticking with Drupal 7 until support has ended, at which point they will have to port over in order to keep their site secure. Another piece of good news for anyone weighing up their options with Drupal 7 is that support for Drupal 7 will also be extended to November 2021 (previously support would have ended for Drupal 7 as soon as Drupal 9 was released) so this gives you another year to implement your migration to Drupal 9.
So the short answer of when to migrate your Drupal 7 site is really whenever is good for you. There’s no immediate rush and if you do opt to migrate to Drupal 8, as long as you keep your site up-to-date, upgrading to Drupal 9 when the time comes should be a cinch!
The Unused Files menu module displays every unused files from your website, that can be filtered by file type and status.
The unused files list is can be seen through the administration menu by navigating in Content > Files > Unused Files, or by the link to /admin/content/file/unused
In this list you can see every file that is not used by one of the fields from the content of your website, like your nodes or taxonomies. It lists the file main informations like the name, type, author, date and status.