Commenting in Drupal hasn't noticeably changed in 15 years. That changes now.
13 Oct 2026
Drupal.org aggregator
Freelock Blog: Drupal Meets Matrix 03 - Better Conversations with Advanced Comment Threads
Drupal Meets Matrix 03 - Better Conversations with Advanced Comment Threads
13 Oct 2026 5:00pm GMT
Omega8.cc: One Garage, Many Engines
In March 2012 a developer asked us for a PHP version per platform, a per-site override on top, and a way to tell Drush which PHP to use, and I turned the Provision half down myself, because the Ægir backend's command-line PHP was hard-wired into the Drush wrapper and had to be running before any task could change it. Fourteen years and a few small text files later, BOA-5.88.866 closes that gap: one line in cli-per-platform.info gives a platform its own command-line PHP, so a Drupal 7 codebase keeps its drush on PHP 7.4 while the Drupal 11 build beside it gets 8.5, in the same account, with no ticket to anyone, and a task which would run a site's code on a PHP its core cannot handle is refused before PHP even starts, with the line that fixes it printed in the message. It works because every command in your shell and every Ægir task for your account now passes through BOA's shell wrapper, which picks the version before any PHP is running at all.
13 Oct 2026 2:16pm GMT
Specbee: Need better image galleries in Drupal? The Media Scroller module adds a large main image, synced thumbnail navigation, and simple configuration without custom templates.
Need better image galleries in Drupal? The Media Scroller module adds a large main image, synced thumbnail navigation, and simple configuration without custom templates.
13 Oct 2026 11:08am GMT
rachel_norfolk: I’m always blown away by the Driesnote slides
I'm always blown away by the Driesnote slides
I've watched a lot of Driesnotes. A lot. Goodness me, I don't even know how many.
Over the last few years, and I promise to find out exactly how many, Dries has had a lot of help with the design of them from an awesome designer at Acquia who I just have to shout about - ASH.
(yes, absolutely go give the shout outs!!)
- Read more about I'm always blown away by the Driesnote slides
- Log in with GitHub or Google to post comments. Or, if you came across this post via Mastodon, just reply there!
13 Oct 2026 10:49am GMT
12 Oct 2026
Drupal.org aggregator
Droptica: Drupal security updates in the AI era: why “we’ll patch next sprint” no longer works
Most Drupal site owners I talk to handle Drupal security updates the same way. These are the fixes the Drupal Security Team publishes for core and contributed modules. A developer sees the security advisory. A ticket goes into the next sprint. The patch goes live a few days later, sometimes two weeks later.
12 Oct 2026 5:45pm GMT
Dynamosys Insights: Playwright for Drupal: A Practical Guide to Test Automation
A Drupal update should come with confidence that your important workflows still work. Learn how to introduce Playwright, build useful browser tests, and make automation part of your release process.
12 Oct 2026 4:43pm GMT
Security public service announcements: Upcoming critical Drupal core release on October 14, 2026 - PSA-2026-10-12
Date:
2026-October-12
Description:
There will be a Drupal core security release for all supported branches on October 14, 2026 between 16:00 and 21:00 UTC. (To see this in your local timezone, refer to the Drupal Core Calendar.) Based on our analysis this vulnerability rates at 19/25 on our risk calculator.
The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.
We recommend updating to the latest supported patch (bugfix) release for your site's version of Drupal before October 14, so that you can address any other upgrade issues before the security window.
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.
Affected versions
All currently supported versions of Drupal core are affected, including:
- Drupal 11.4.x
- Drupal 11.3.x
- Drupal 10.6.x
Drupal 12.0.0-beta1 is also affected. New beta releases will be provided following the security updates for the supported branches.
All versions of Drupal prior to 10.6.x, as well as all versions of Drupal 11 prior to 11.3.x, are end-of-life and no longer supported. Sites on those versions should update as soon as possible to avoid this and other publicly disclosed vulnerabilities.
Disclosure policy
Neither the Security Team nor any other party is able to release any more information about this vulnerability until the announcement is made. Security release announcements will appear on the Drupal.org security advisory page, which has RSS feeds. The announcement will also be made public on:
- The
#security-teamchannel of the Drupal community Slack - Bluesky
- Mastodon
- X (formerly Twitter)
- By email for those who have subscribed to our email list. (To subscribe to the email list: log in on Drupal.org, go to your user profile page and subscribe to the security newsletter on the Edit » My newsletters tab.)
Coordinated By:
- Bram Driesen (bramdriesen) of the Drupal Security Team
- catch (catch) of the Drupal Security Team
- Damien McKenna (damienmckenna) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Lee Rowlands (larowlan) of the Drupal Security Team
- Dave Long (longwave) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Michael Hess (mlhess) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
12 Oct 2026 4:10pm GMT
Gspikes: Cleaning a Decade of Drupal Database Cruft Before You Migrate
The eight-step Drupal 7 database cleanup we run before every migration: caches and logs, revisions, deleted fields, files, spam accounts, content you will not bring, and the module data you leave behind, in the order that costs least and saves most.
12 Oct 2026 3:48pm GMT
The Drop Times: Who Has the Authority to Slow AI Down?
Questions about the pace of advanced artificial intelligence are no longer confined to the research teams building it. Former OpenAI safety leader David Robinson described his decision to leave the company in a 3 October essay for The Atlantic, challenging the assumption that developers can release increasingly capable systems and address risks as they emerge. Former Anthropic researcher Jacob Coxon had raised concerns about competition between AI laboratories in a September interview with WIRED. Their warnings point to a conflict between the speed of development and the time required to evaluate its consequences. Neither departure demonstrates that the industry has actually slowed down.
That tension has reached public hearings and internal disputes. At a 5 October hearing, New York City Council members questioned representatives of major AI companies and heard testimony from former researchers at Anthropic, OpenAI and Google DeepMind. Three other former OpenAI safety researchers, Jasmine Wang, Tomek Korbak and Mikita Balesni, subsequently disputed the company's stated grounds for their dismissal. They warned that uncertainty over acceptable contact with external evaluators could discourage scrutiny. OpenAI rejected the suggestion that they had been dismissed for raising safety concerns and said its policies on sensitive information had been breached. The underlying dispute remains unresolved.
Public oversight offers a possible route beyond those competing accounts, but proposals must be distinguished from protections already in force. New York City lawmakers have discussed third-party validation, reporting and protections for people who flag risks. These measures would need to be enacted and implemented before their practical effect could be assessed. Independent evaluation also raises a harder question than whether a company publishes safety reports: who receives the findings, who can challenge the evidence and who has the authority to require a change before deployment? A review process may identify dangers without having the power to alter a release decision.
These questions extend beyond arguments about catastrophic AI scenarios. Organisations that develop or operate software routinely face uncertainty, conflicting incentives and decisions that affect people outside their own teams. Open-source communities confront some of those problems through public issue histories, reviews and shared maintenance, although those processes are not substitutes for the legal and institutional oversight proposed for advanced AI. What matters is whether concerns can move from warnings to decisions, with clear accountability when evidence is contested. The question is not only whether someone is willing to say that development should slow, but whether anyone outside the organisation can make that warning count.
Follow The DropTimes on LinkedIn, X, Bluesky, and Facebook, or join #thedroptimes on Drupal Slack.
Kazima Abbas wrote and curated this issue of Editor's Pick.
12 Oct 2026 2:55pm GMT
Drupal AI Initiative: Leading the Open AI Conversation: Drupal at Digital Leaders' AI Week 2026
Author: Will Huggins
The narrative around enterprise AI is changing. Digital leaders - from CMOs looking for campaign velocity to CISOs managing vendor risk - are no longer just asking for new AI features. They are asking for AI infrastructure they can actually trust. They want to know how to maintain brand sovereignty, ensure content provenance, and scale AI operations without creating unmanageable compliance risks.
This shift in the market perfectly aligns with the mission of the Drupal AI Initiative: to establish Drupal as the premier open-source AI platform for digital experiences.
This October, the conversation takes a national stage at Digital Leaders' AI Week 2026, the UK's largest online festival of AI learning. And the Drupal community is front and center.
While Drupal AI is fundamentally a technology initiative, its real-world impact comes from the thought leadership of the people building it. At AI Week, members of the Drupal ecosystem will share strategies that go far beyond the CMS, showing how open-source principles are solving the hardest challenges in enterprise AI adoption.
Here is a look at two key sessions you won't want to miss.
The Technology Is Ready. Is Your Organisation? Why AIMS Will Define the AI Leaders
When: October 16, 2026
The technology to generate content, personalise experiences, and orchestrate complex user journeys is already here. But as many organisations are discovering, having access to an AI model is not the same as having a scalable AI operation.
In this session, we will explore the critical gap between technological capability and organisational readiness. The focus will be on the necessity of an AI Management System (AIMS) - a structured approach to governing AI adoption.
This is where Drupal AI's philosophy truly shines. When we talk about Drupal as an "AI platform," we are talking about built-in governance. Organisations locked into proprietary platforms often struggle to adapt their AI infrastructure as new models emerge or regulations change. Lightweight SaaS tools, conversely, often lack the rigorous audit trails enterprise IT requires.
This talk will illustrate why the organisations that win in the age of AI will be those that prioritise structural sovereignty - the ability to control their own data, choose their own models, and enforce their own brand guidelines at scale. It's the exact reason why the Drupal AI Initiative developed the Context Control Center (CCC), ensuring that AI-generated content is always grounded in verified, human-authored brand rules.
Tell Me It's AI By Actually Telling Me It's AI: Designing Provenance Data Users Actually Trust
When: October 15, 2026
As AI-generated content floods the web, user trust is becoming the most valuable currency in digital experience. How do organisations prove that their content is accurate, authoritative, and compliant?
This session tackles the critical challenge of provenance data. It's not enough to simply label something as "AI-generated"; organisations need to design systems that users can fundamentally trust.
This aligns perfectly with Drupal's Grade A rating for Software Sovereignty. Drupal's architecture is built on transparency and community governance. The platform doesn't just generate content; it provides the branch-based versioning, strict approval workflows, and deep audit trails necessary to track exactly how that content was created.
When an AI agent in Drupal proposes a layout optimisation or drafts a translated page, it operates within a highly governed environment. Humans remain firmly in the loop. This session will explore the broader implications of this approach, arguing that trustworthy AI requires safeguards built into the core architecture, not bolted on as an afterthought.
Join the Conversation
The future of digital experience is being built on open, model-agnostic foundations. The Drupal community's strong presence at AI Week 2026 reflects our commitment to leading this transformation, ensuring organisations can move fast, stay in control, and own their digital operations permanently.
We encourage everyone in the Drupal community - and anyone responsible for digital strategy in their organisation - to register for these free sessions.
👉 Register for AI Week 2026 Here
To see how these principles are being put into practice today, explore the Drupal AI interactive demos.
12 Oct 2026 2:10pm GMT
Jacob Rockowitz: Running with scissors: Using AI to explore, build, maintain, contribute, and secure Drupal
Running with scissors: Using AI to explore, build, maintain, contribute, and secure Drupal" is the title of my DrupalCon Orlando session proposal. I've been using and writing about AI as a Drupal developer for the past year, and I look forward to sharing my experience with fellow Drupalers at the conference. There is so much discussion about AI and Drupal, and I'd like your help with my DrupalCon session proposal.
We should assume most session proposals will focus on AI inside and outside Drupal from the perspective of site owners and builders. Meanwhile, if we want to encourage people to try Drupal, we also need to sell it to developers. My goal is to sell "using AI to explore, build, maintain, contribute, and secure Drupal" to developers and vibe coders, while acknowledging the challenges and risks by comparing how fast we've had to adopt AI to "running with scissors."
Running with scissors
I first heard the expression "Running with scissors" in the title of Augusten Burroughs' memoir. I enjoyed reading that book, and now I am listening to the audiobook while working on this blog post. A subtle takeaway from the memoir is that sometimes you may find yourself "running with scissors' involuntarily (or voluntarily), and you have to decide how to handle that scenario.
Related to AI, "running with scissors" captures the extremely fast, collectively exceptional pace we're in: a remarkably massive societal shift, comparable to the Industrial Revolution, is unfolding. The Industrial Revolution took decades to unfold, whereas the AI Revolution is unfolding in a few years, especially among software developers.
The AI Revolution is probably the right term, and it could foreshadow AI winning the revolution, leading to humankind's demise. BTW, this won't be the focus of my session...Read More
12 Oct 2026 1:32pm GMT
The Drop Times: EU Cyber Resilience Act: What Drupal Suppliers Must Assess
Shared code creates shared security needs. European product rules raise a more specific question: who must act?
12 Oct 2026 8:36am GMT
11 Oct 2026
Drupal.org aggregator
#! code: Drupal 11: Don't Create Node During Content Import
Importing content with the Default Content module is really useful when populating a site with content. There's an increasing number of recipes and modules that can be used to populate a site with content either for setup or demonstration purposes.
Default content is really useful when figuring out how a system works as it can show relationships between content types that are not always simple to discern through the site itself. It also has a place when deploying content between sites as you can package up some default content and include that in a deployment step.
Occasionally, you'll want to tweak the content that is imported for different situations; with the reasons why you would want to do this being numerous. It might just be that you have a demo site and you wanted to tweak the content imported to better tailor it for the user. You could have a single recipe that contains the content and want to alter that for a specific demo.
I needed to do this selected default content import on a recent site as I was installing. A contributed module was used to populate the site with content to create a collection of examples. Although the content was good, I didn't want to import it all as some of it didn't make sense for a couple of scenario that I was looking at. That lead me to seeing if I could alter the content automatically as it was imported into the site, rather than manually delete content after the fact.
In this article we will look at some of the actions I tried to prevent content from being imported, before moving onto what the actual solution was. If you are following along at home, it is assumed that you already have a default content process setup and are just looking for change what content is imported without altering the source files.
11 Oct 2026 5:54pm GMT
Drupal Patterns: From Architecture to Innovation: Interactive Forms with htmx 4
Drupal's Form API comes with built-in tooling to allow any form element to initiate a submission. When combined the support for returning HTML fragments in htmx 4, it's very easy to make an interactive form for your users.
11 Oct 2026 1:36pm GMT
10 Oct 2026
Drupal.org aggregator
Freelock Blog: Drupal Meets Matrix part 2: Live Comments with ECA and HTMX
Drupal Meets Matrix part 2: Live Comments with ECA and HTMX
A comment thread in Drupal works totally fine. You fill in a form, click submit, and your comment gets posted. Same way it has for over 20 years.
But if somebody else replies when you're on the page, you don't see anything change, you don't get any notification.
10 Oct 2026 7:00pm GMT
Dominique De Cooman: DrupalCon Rotterdam: building Drupal’s AI future together
Opening DrupalCon, a summit
Saturday, October 10, 2026 - 19:41
10 Oct 2026 5:41pm GMT