All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
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.
It’s time for me to amble into my garage and offer up an assortment of the strange things that I find there. It’s a bit of a post-Christmas tradition here at the stew. I have to make room for all the coal Santa keeps bringing me for some reason… Each has an adventure seed baked in so feel free to pick them up for your players. After all, one gnome’s trash is another’s treasure.
As is tradition, I’m offering up more than one version of some of these items: a mundane one, and additional details of a more fantastic nature — suitable for use in your supernatural horror, fantasy, or sci-fi campaigns.
Paper and ink: This could be a simple sheaf of paper and an inkwell, or a calligraphy set, or in a modern game could simply be printer paper and ink. In any case it’s eye catching, high quality and a steal at the price being asked.
Mundane: Upon use it is discovered that the ink is invisible when it dries and some of the paper has already been used. The notes uncovered lead on some sort of scavenger hunt. Who set it up, and what is the end result likely to be? Is it worth tracking down all the clues?
Fantastic: This appears to be normal ink and paper, but writing or printing using the paper and ink appear normal then slowly transform into different documents over time.
A set of gardening tools: A bundle of tools for tending plants — a set of snips, a small hand rake, and a trowel — wrapped in a canvas satchel featuring a map.
Mundane: secreted in the handle of the trowel is another piece of fabric with some cryptic lines and holes that overlay the map on the satchel. Leading to buried treasure perhaps?
Fantastic: In addition to the map and the riddles, the trowel itself acts as a lodestone at various locations.
An old filing cabinet: A cabinet for keeping papers and files of common construction. A little worn out but still functional.
Mundane: A false bottom conceals a weapon, a stash of cash and a diary that may lead to more. Who did this belong to and how did it get sold at a yard sale?
Fantastic: The cabinet is haunted of sorts. Strange sounds come from it and there are flashes of movement in the corner of your eye when it is nearby. Can solving the mystery of the diary put these spirits to rest?
An animal leash: A leather leash with several sets of numbers etched on its sides, and a metal handle. The sets of numbers are coordinates. The first leads to a site off some wilderness walking trails with a grave marker and a vault door that requires more than one key to open. Maybe the other coordinates have the other keys.
A grave site: The deed to a grave site. Supposedly never used, but being sold for just a little cash. Seems worth the gamble.
Mundane: According to the cemetery, the plot is indeed unused, yet it appears to be occupied. Unearthing the site reveals only a large metal box containing a vampire slaying kit, a diary with names and locations, and a note addressed to the PCs directly. Where did this come from? How did they address it to you and is there a madman out there slaying “vampires”?
Fantastic: With a little more fantasy, those vampires are probably real and likely aren’t happy someone has all their addresses.
A vintage tool: A complex mechanical tool. Old but in good condition. It would be useful for a PC’s crafting. The tool works but It’s missing an optional part that’s complicated enough that jury-rigging one is unlikely. Local crafters can’t provide one, because they don’t know what it’s supposed to accomplish. However, they can interpret the machine’s maker’s mark, so the original craftsman can be tracked down.