With Drupal 12 on the horizon and Drupal 10 reaching end of life in December, I'm facing two challenges. First, I need to upgrade my current site from Drupal 10 to Drupal 11. Second, I need to update my contributed modules to support Drupal 12, while still supporting Drupal 10.  

To address these challenges, I’m experimenting with an AI agent skill and a corresponding DDEV command, drupal-core-switcher, that toggles my application between the previous, current, and next versions of Drupal core and compatible contributed modules.

Are you facing similar challenges? Is having a drupal-core-switcher skill and command helpful?  If you are procrastinating on upgrading to Drupal 11, would you use AI to help you do it?

Great news: Contrib Kanban is back thanks to Matt Glaman.

As a result you can get an overview of every issue with a given tag again. For example, everything that is tagged with "rosetta" from the DrupalCon Rotterdam DriesNote.

I liked the idea, but the project could use some visual polish and a dash of fun!

So here it is: an improved UI and an issue roulette.

Spin it, take the issue that stops under the marker, and get to work. You get three re-rolls.

What do you think and what needs to be improved?

---

Some stuff is still in a Github PR but here are the links.

Website: https://contribkanban.com/
Github repo: https://github.com/mglaman/contribkanban.com

For years my workflow to solve a problem in Drupal was as follows.

First I try to find someone else who had the same problem and if there is a patch available. If there is a patch I use it. If the patch doesn’t apply, I fix it for the module version I’m using and publish the updated version. If I’m the first with that problem I report it and try to find a solution. If the solution is generic enough, I share it with the community so more people can build on top of it.

These days things have changed. We use Claude Code to fix the issues now and sometimes it ends up patching stuff in core or in contrib modules. When I suggest my coworkers share the result with the community they refuse. They can ask Claude to fix future issues so there is no need to share. But I also think they don’t understand the code and that is why they don’t want to share it.

So I wonder. If everyone starts doing the same, who is going to contribute to Drupal? Do you know if the contributions have decreased this year due to AI?

Hello author here!

What is DruBOM: a Drupal module that lists every component a site uses, checks for known vulnerabilities and exports an SPDX 3.0.1 SBOM, requiring no third party libraries installation.

In this post I outline what the module does, how it has improved and how it was built; I hope you enjoy the post and the module, and feedback is welcome.

https://www.paolomainardi.com/posts/drubom-next-gen-drupal-supply-chain-security/

When I started my postion as a Drupal Web Developer I inherited a very poorly maintained Drupal site. It was on Drupal 9 when I started, a week before it went EOL. It took me a year to clean it up enough to make the jump to D10, and that was with a lot of help from my predecessor, who we had to bring in on a consulting fee, and while he was great and wicked smart, he was not a great teacher. I've been in my position for 3 years and have been so bogged down in front end content management that I haven't had time to do anything other than regular D10 patches. Now we're looking to jump to D11, since D10 is going EOL, and this new PHP nonesense is driving me up the wall trying to figure out how to fix all this without torching the site.

At this point I'm looking for a company who can come in and clean up all the wonky database mess we have, figure out what packages are being used, and basically clean up the back end of the site so I can have a clean build to work with. Who can I reach out to for a consultation and figure out how I can get this site back to a manageable build?

This may be of interest to some folks.

At Kitchener Public Library. I'll be speaking on the Hosting Panel, so I hope to see some of you there! 😄

This game was made just to teach people about the Drupal AI ecosystem, but it is hopefully fun to play for anyone.

The game can be played online or downloaded here: https://macpackwala.workflows-of-ai.com/

Some more information here: https://workflows-of-ai.com/blog/i-vibe-coded-a-point-and-click-game-to-learn-about-the-drupal-ai-ecosystem

If you can't patch yet.

I can't load drupal.org for the last few minutes. Some pages have been unavailable longer than that. Most of the down detectors say it is still up, but not for me. I am in St. Louis.

Anyone else seeing this? Thanks.

My take is that contributing to and growing an open-source project is easier with AI than without it. Still, while working on the Webform module's security issues, I was terrified that a single AI-generated misstep would draw vitriol.

Let's talk about our Drupal gardens and engage in an open dialogue among those who are AI-pilled, AI-curious, and AI-cautious.

A year ago, I attended a one day drupal training camp and met a few absolutely wonderful people.

So encouraging and just consistently hyping me up any time I got stuck. I tried to download the cms on my chrome book with Linux emulated and forgot to give it enough disk space and they didn't let that keep me behind.

They instead introduced drupal forge to me and made sure I left with some knowledge which I can't thank enough.

However, icl I kinda got lost and could not learn any more cause the difficulty increased tenfold so I never picked it up again but, I'd really like to learn it purely to make my, one day, mentors proud💚

This is mainly targetted at the broader AI community, but it also has a section what we mean to implement in AI Image Crop module

I am running two docker services that use the same Drupal instance.
The first one, let's call it "http", serves the site, and the second one, let's call it "amqp" runs a drush command that listens to AMQP messages (via rabbitmq) to alter content.

The amqp service process tasks that outlive a normal request; a task can take up to several minutes.

I am experiencing cache issues between both services: when a configuration is updated on the "http" service, the "amqp" service still uses a cached version, and when an entity is updated on "amqp" service, the "http" service still shows the old cached version.

I managed to fix the first issue by calling "ConfigFactory::reset" before retrieving the config object when a new message is processed, but this seems like a dirty fix, and I don't see how I can apply such a fix for the issue regarding entities.

Has anyone experienced such an issue ?
Any ideas of how to deal with this ?

P.S: I have APCu and memcache enabled, but the issue appeared before memcache was installed.

Any help will be highly appreciated.

A demo on the work that I've been doing on exposed slots in Drupal Canvas.

This is still a proof of concept, we are not there yet.

I hope this demo gets people as excited as I am about this feature.

I think this one is very important to drive Canvas adaption.

Let me know what you think!

MR: https://git.drupalcode.org/project/canvas/-/merge_requests/1359

I've been thinking about how much money gets wasted on development and staging environments that sit idle most of the time.

For example, DigitalOcean still charges you for a Droplet even when it's powered off. The only way to stop compute charges is to destroy it entirely.

But then you have to deal with snapshots, restoring env vars, networking, etc. whenever you need it again.

I'm curious how other developers deal with this. Do you just leave everything running and accept the cost? Destroy and recreate environments manually?

Especially sketchy is that it goes back to 8.x so any unsupported sites floating around out there could be in trouble

Remark: I work at CKEditor as a Developer Advocate 🥑

Drupal 12 is in beta since DrupalCon Rotterdam, and today both official CKEditor contrib modules got their matching 2.0.0-beta1 releases:

• CKEditor 5 Plugin Pack 2.0.0-beta1
• CKEditor 5 Premium Features 2.0.0-beta1

What to know before you try them:

• 2.x requires Drupal 12 and is not compatible with Drupal 10 or 11. The 1.x line stays for Drupal 10.3+ and 11.
• Both modules have to be upgraded together with core, in one Composer operation:

``` composer require \ 'drupal/core-recommended:<sup>12.0@beta'</sup> \ 'drupal/core-composer-scaffold:<sup>12.0@beta'</sup> \ 'drupal/core-project-message:<sup>12.0@beta'</sup> \ 'drupal/ckeditor5_plugin_pack:<sup>2.0@beta'</sup> \ --no-update

composer update --with-all-dependencies ```

• Already on Drupal 12 without the modules? Then just composer require 'drupal/ckeditor5_premium_features:^2.0@beta' 'drupal/ckeditor5_plugin_pack:^2.0@beta'.
• Both betas switch to the CKEditor 5 UMD installation method that Drupal 12 uses. Premium Features also adds a collapsible AI container, AI Chat context configuration, configurable heading levels in the document outline, clipboard mode for collaboration, and Arabic-Indic numbering for footnotes.

I tried to kick this off a bit during DrupalCon Rotterdam, the slides give the high-level idea of the 1.x vs 2.x split: CKEditor in Drupal: News in Content Editing

Are the release notes clear? If anything in the upgrade path is confusing or breaks on your Drupal 12 test site, say it here and I will pass it on to the module maintainers.