Commenting in Drupal hasn't noticeably changed in 15 years. That changes now.
Commenting in Drupal hasn't noticeably changed in 15 years. That changes now.
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.
I've been maintaining the matrix_api module on Drupal.org since 2016, nearly a decade of it doing one thing well: posting Drupal events into a Matrix room. This year that changed.
Gabor asked in Slack about how people contributing to Drupal manage multiple different Drupal versions, and different contributed module branches, when using AI agents:
KSER is a community radio station. Community radio doesn’t get downtime — or a huge IT budget.
We started maintaining KSER’s Drupal 5 site in 2013, even though Drupal 5 had already reached end-of-life. For more than a decade, we kept it secure, stable, and useful while the station put its resources where they mattered most.
Now KSER has a new home on Drupal 11 and Drupal CMS, with Drupal Canvas for easier content management and a persistent audio player that keeps the station streaming while visitors move through the site.
Sometimes the right answer isn’t “rebuild now.” It’s maintain what you have well, then replace it when the time is right.
On July 17, WordPress shipped an emergency security release for a vulnerability chain now being called wp2shell.
While your site is running, things change. A content editor tweaks a configuration setting. A security vulnerability surfaces in a dependency. A production fix gets applied directly instead of going through the normal release process.
From early days, "views" has been the killer feature of Drupal. Views is a powerful querying tool built into Drupal that allows dynamic lists and displays of content to be created without writing custom code.