Drupal Autocomplete Patch Rejects Invalid New Tags in Tests
How Drupal Sites Track AI Requests, Token Costs and Budgets
What Two Developers Taught Me About Drupal Outside Web Summit
Handling Media in Drupal CMS
You’ve installed Drupal CMS and now you need to add images, documents, and videos to your site.
The good news is that most of the setup is already done.
Drupal core provides Media and Media Library, and Drupal CMS adds extra modules and configuration on top so it all works straight after you install it.
In the video above, you will learn how media works in Drupal CMS. We’ll upload and crop media, embed it in CKEditor, display a media field with Drupal Canvas, see how responsive images are set up, and map remote video metadata into a custom field.
LocalGov Day Speakers Outline Austria’s Digital Sovereignty Plans
Not Fitted to This Model
On Thursday 19 November PHP published five releases and seventeen security advisories, seven marked critical, a day after a notice which said only that the critical ones need non-default configuration or uncommon setups. A hosting stack is nothing but non-default configuration, so we read every advisory against the way BOA, the open-source Ægir stack we host Drupal and Backdrop on, runs PHP, and checked two of them on a test server. Five of the seven want something BOA does not give them, and the other two hang on a site's own code. One rated high did concern us, through a PHP-FPM setting we had switched on ourselves in October, so since about an hour after the release the agent on each BOA server switches it off by itself, at the price of a log and before any PHP was upgraded. By 16:33 UTC the fixed 8.2.36, 8.3.37, 8.4.28, 8.5.13 and the first general release of PHP 8.6 were on the stable trees with the upgrade forced, and PHP's own fix on our 8.1.34. Talking Drupal #579 - Women in Drupal
Today we are talking about Woman, Drupal, and Woman in Drupal with guests Ashleigh Fox, Sinduri Guntupalli, and Rachel Lawson. We'll also cover Legal as our module of the week.
For show notes visit: https://www.talkingDrupal.com/579
EvolveDigital NYC 2026 Speakers Address CMS Decisions, Drupal Crawlers and AI
The DropTimes Townhall Explores Reaching Audiences Beyond Drupal
Replacing drush site:install in Drush 15
Drush 15 dropped site:install, and core's dr install only installs to SQLite. Here is the small script I wrote to install Drupal into MySQL the way Drush 13 did, plus a DDEV command and a CI step that use it.
Recalls at Race Pace
On Wednesday 18 November two security releases landed within three hours: nginx 1.31.9 with ten fixes, four of them reachable on a BOA server, where every site speaks HTTP/2, HTTP/3 and TLS 1.3, and Drupal core's critical SA-CORE-2026-017, a remote code execution through the installer. Both carry the mark of this year, since Drupal's advisory credits a scanner from an AI lab and nginx's change log an AI security firm. On BOA, our open-source Ægir hosting stack for Drupal and Backdrop, the installer has answered 404 on every site since 2012, which we proved again with 84 requests, so site owners update core this week instead of this hour. For nginx the security floor built for PHP in October was extended the same evening, so a BOA server below 1.31.9 books an upgrade for itself inside thirty minutes, automatic updates off or not. Two and a half hours from the go to the stable trees, with AI doing the legwork and a human holding the keys, and why we think that is no longer optional. Giving an AI Agent Its Own Linux User (Without Breaking DDEV)
TL;DR: My coding agent runs on my WSL2 machine as its own Linux user, with its own home directory and its own rootless Docker daemon. DDEV runs as that same user, in my terminal and in the agent's. My workflow did not change. This post explains why I did it, what it took, and what broke along the way.
The surprise came quickly: My agent had a terminal open in a client project, about to run ddev composer install, and I wanted to know what it could reach if a task ever went sideways. The answer was: everything. The agent ran as my user, so it could read my SSH keys, push with my Git and gh credentials, reach everything on the Windows side through /mnt/c, and talk to a Docker daemon running as root. Its permission system asked before every Bash command, and I approved commands in five-second intervals, all day. At some point I stopped reading the prompts and clicked allow blindly. That was the moment I knew the agent and I needed a different kind of protection.
An agent with a shell can wreck the machine it runs on (delete files, fill the disk), take it over (steal credentials, plant a backdoor, use the Docker socket), write code that does more than the task asked, ship private code and secrets somewhere else, or reach network services it was never meant to touch. Wherever it runs, those risks travel with it.
SQL Sync for DDEV: Drush-Style Database Sync for Any SSH Server
Anyone who has worked with Drupal knows this command:
drush sql-sync @prod @self
One command, and the local site has a copy of the production database.
I use Drush a lot, so I wanted the same thing for my personal projects. They are Laravel, WordPress and plain PHP sites, and they live on all sorts of hosting: shared accounts, VPSs, dedicated boxes — a good number of them running cPanel, which itself runs on shared and dedicated hosting alike. What I had instead was the usual mix of phpMyAdmin exports and one-off scripts that I had to remember each time.
DDEV does have pull providers. The ready-made ones are for hosted platforms like Pantheon and Acquia, but the examples it ships also include an rsync one, for pulling a dump down from a plain server over SSH. I do not want to overstate the gap: that example works. But it is a starting point you adapt, not a finished tool. Every project needs its own provider file, written and kept up to date separately, and sanitize is on you. I kept missing the Drush shape: one aliases file, the same command in every project, and sanitize taken care of. So this add-on is that shape, packaged: ddev-sql-sync.
One thing to state up front: I designed this add-on, and it was built and tested with the help of an AI agent, Ryan (Muse), working under my direction. There is a bit more about that at the end.
Where I use it:
Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-018
drupalDate: 2026-November-18Security risk: Moderately critical 14 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:UncommonVulnerability: Gadget chainAffected versions: <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13CVE IDs: CVE-2026-132166Description: Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site. This so-called "gadget chain" presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.
This issue is not directly exploitable.
This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize().
Install the latest version:
Drupal 11
- If you use Drupal 11.4.x, update to Drupal 11.4.13.
- If you use Drupal 11.3.x, update to Drupal 11.3.22.
- Drupal 11.2.x and below are end-of-life and do not receive security coverage.
Drupal 10
Drupal core - Critical - Remote code execution - SA-CORE-2026-017
drupalDate: 2026-November-18Security risk: Critical 18 ∕ 25 AC:Complex/A:None/CI:All/II:All/E:Proof/TD:UncommonVulnerability: Remote code executionAffected versions: <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13CVE IDs: CVE-2026-132165Description: Drupal core ships with an install.php file for installing Drupal core.
Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution.
Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. In addition to upgrading, the Drupal Security Team recommends securing the Drupal installer after installation.
Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU.
Drupal Steward protection:
This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.
The Work We Want: AI, Code Directors, and Collective Power
Drupal CRM integration for pre-qualified inquiries
An informed buyer shouldn’t have to repeat their research to sales. Drupal CRM integration can connect forms and agent endpoints to your CRM without losing intent, consent evidence, or inquiries during an outage. DrupalCamp Spain 2026 Speakers Examine AI Reliability and Human Agency
Association Website Design: Lessons From the 100 Largest US Associations
Contributor Training: Advanced coder.ddev.com Usage

coder.ddev.com gives you a DDEV environment in the cloud, with nothing installed on your own machine. Since the announcement it has grown a Drupal issue picker, a freeform template for any DDEV project, and several ways to run Claude Code inside a workspace.
Here's our November 11, 2026 Contributor Training on advanced coder.ddev.com usage:
The slides are available at rfay.github.io/advanced-coder-presentation, with source at github.com/rfay/advanced-coder-presentation.
What coder.ddev.com Iscoder.ddev.com is a free, experimental service built on the open source Coder project. Each workspace is an isolated Docker-in-Docker container (using Sysbox) with DDEV, Docker, Git, VS Code, and Claude Code already installed. The tools run on the server and use the workspace's files and configuration.
It is experimental. There are no guarantees about uptime or data retention, and a workspace that sits idle for 14 days is deleted, so keep your work in Git.