Working on a client site right now and it's giving me flashbacks.

42 contrib modules installed. Asked the client which ones they actually use. They could name maybe 8.

The rest? "They were there when we took over the site." Which was 2019. Which means whoever installed them is long gone.

Ran Upgrade Status and it's the usual chaos. Some have D11 equivalents, some don't, a couple are just... abandoned. Last commit 2021.

The one that got me was a custom integration with a CRM that no longer exists. Still enabled. Still trying to ping something every time a form submits. Nobody knew it was there.

D7's been EOL since January anyway so this is all moving eventually but in the meantime I'm building a module inventory spreadsheet from scratch because apparently that's the job now.

Anyone have a good process for this kind of archaeology? Getting tired of reverse engineering everything from database logs.

Hey r/drupal!

If you've been experimenting with the new Drupal Canvas workspace, you probably love how clean the component-driven workflow is compared to legacy approaches. But if you are coming from older setups, setting up a rich component library from scratch can take a lot of repetitive boilerplate.

Live Demo

Drupal.org: Canvas Palette Project Page

I built Canvas Palette — a comprehensive bundle of SDC (Single Directory Component) elements ported straight from my EPT (Extra Paragraph Types) and EBT (Extra Block Types) modules.

Would love to hear what you all think, how you're structuring your SDC libraries, and if you run into any quirks while building with Canvas!

I have inherited a Drupal 10 site where the relationship with the agency that developed and hosts it has broken down almost irretrievably. We have the v10 support end date as a hard deadline for action under threat of deletion, and the agency is quoting ludicrous amounts to do the upgrade and/or give us our site back. Contracts and lawyers are being consulted, but I'm wanting to try do an end-run around all that and at least get our content safely backed up before they decide to pull the plug.

The site itself is a fairly standard marketing site, so nothing interactive or very complex. We have admin account access to the frontend admin pages, but the agency has removed any content export options. We don't have server access, so no command line to install new modules or file system to download files and no database access at all. We have no access to backup files. We're limited to the modules they have installed, which also includes a number of dev and migrate modules they left in the prod clone by mistake which at least gives us Config Sync export.

As an experiment, I've created a test Drupal site, installed and enabled the same set of modules, and imported the prod site config using 'drush config:import --partial' and that all seems fine. Unfortunately the theme is based on their in-house template and we have no access to that for now, so I'm faking it with Olivero, but that's a problem for later.

The next step is to try sync our content to my test site. I've had a google and looked at a few modules like Content Sync and Entity Sync, but they all seem to need a module installed on the origin server and/or database access. I've also looked at the Migrate modules, but they seem aimed at version migrations not server migrations and need direct database access. There is Migrate Source JSON:API but it supposedly only supports Drupal 8.

So, long story short, what options do we have to sync site content when the source is so locked down to us? My instinct is we should be able to do something with JSON:API which we can enable, and if necessary I'll try script something myself, but I'd rather use an existing option written by people who actually know what they are doing!

It's been maybe 20 years since I last did anything with Drupal (although I have more recent Symfony experience), I'm stumbling around in the half-dark here, so forgive if I've missed something incredibly obvious!

Thanks!

Building an RSS news aggregator with Drupal is a write-up of how I used the Aggregator, Rate, Voting API and Views modules to create AnimalRights.fyi. The post covers creating a view with filtering, Twig templating logic, and including custom fields via relationships; building custom modules (including to make Rate use cookies instead of IP addresses to record user reactions); and using the cron to pull in new data.

A while back I posted here about a contrib module I was building called Changelogify.

Someone commented that they liked the idea and would try it once it had security coverage.
Well, it finally does :)

Changelogify now has a stable release covered by Drupal’s security advisory policy.
For anyone who missed the original post, Changelogify automatically captures changes happening on a Drupal site and lets you group them into human readable releases. Things like content changes, module operations, and user changes can become an editable release that you publish as a changelog.

The idea is to bridge the gap between raw logs and the release notes we usually end up writing manually.

Since I first posted it here, I’ve also done quite a bit of work on the module as part of getting it production ready, including:
Drupal 10 and 11 support
expanded event tracking
configuration hardening
better release generation
a draft and review workflow
a themeable public /changelog page
automated testing and CI

Drupal security advisory coverage
Going through the security review process was honestly pretty useful in itself. Reviewers caught things around Drupal conventions, hooks, compatibility, project structure, routing, and testing that made the module better.

So, to the person who said they’d try it when it got security coverage: your move 😄

And seriously, if anyone here uses it on a real Drupal project, I’d love feedback. Especially bugs, missing events you think it should capture, or ways the workflow could fit better into how agencies and Drupal teams handle releases.

Changelogify: Drupal.org/project/changelogify

Install with Composer:
composer require 'drupal/changelogify:^1.2'

The mail just won't send.

The SMTP username and password is correct. I have tested with two SMTP credentials, one that is working on a wordpress site on the same server.

PHP version is 8.3. Drupal version is 10.6.1.

I get similar error with module 'SMTP Authentication Support'.

Here is the error message on verify page when I send a test email:

Failed to authenticate on SMTP server with username "smtpusername" using the following authenticators: "PLAIN". Authenticator "PLAIN" returned "Expected response code "235" but got code "535", with message "535 Authentication credentials invalid".".

Is there a simple way for mail notifications to work with Drupal 10?

@here Board Election Extension

We've discovered that our voting platform, Helios, had a mail delivery outage or queue delay, resulting in the final two reminder messages not being delivered until after the deadline for some voters.

Therefore, we have extended the election.

The Board Election is now closing Monday 17 August, 23:59 UTC

That is:

- 7:59pm Eastern, Aug 17
- 4:59pm Pacific, Aug 17
- 05:30am on 18 Aug - India time
- 9:59am on 18 Aug - Australia time

Search for messages from "[[email protected]](mailto:[email protected])"to find your ballot

Learn about the candidates and the election timeline here:

https://www.drupal.org/association/board/elections/election-2026-dates-and-candidates

This election uses approval voting: rather than picking just one candidate, you may vote for every candidate you approve of, and the candidate approved by the most voters wins. More on how approval voting works:

https://en.wikipedia.org/wiki/Approval\_voting

Questions or trouble voting? Contact [[email protected]](mailto:[email protected])

🗳️ Board Election Reminder: Voting is currently open for the 2026 Drupal Association At-Large board seat! The Board Election is closing today 14 August, 23:59 UTC

That is:
- 7:59pm Eastern, Aug 14
- 4:59pm Pacific, Aug 14
- 05:30am on 15 Aug - India time
- 9:59am on 15 Aug - Australia time

Search for messages from "[[email protected]](mailto:[email protected])"to find your ballot

If you were signed up as a Ripple Maker (Drupal Association member) as of 24 hours before the election opened you should have received a ballot from Helios Voting. ( [[email protected]](mailto:[email protected])).

Voting began 22 July at 00:00 UTC and closes 14 August at 23:59 UTC.

Learn about the candidates and the election timeline here:
drupal.org/association/board/elections/election-2026-dates-and-candidates

This election uses approval voting: rather than picking just one candidate, you may vote for every candidate you approve of, and the candidate approved by the most voters wins. More on how approval voting works:
en.wikipedia.org/wiki/Approval_voting

Questions or trouble voting? Contact [[email protected]](mailto:[email protected])

This morning after upgrading to 11.4.5 I cannot access config menu. Error is The website encountered an unexpected error. Try again later. It ha been a few hours, no change. I just checked the Statis report, same error. I can get into the recent log messages. I think I see the entry but have no idea how to fix. Here it is:

Message: Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'locale_file.hash' in 'SELECT': SELECT "locale_file"."project" AS "project", "locale_file"."langcode" AS "langcode", "locale_file"."version" AS "version", "locale_file"."timestamp" AS "timestamp", "locale_file"."hash" AS "hash", "locale_file"."last_checked" AS "last_checked" FROM "locale_file" "locale_file" WHERE ("project" = :db_condition_placeholder_0) AND ("langcode" = :db_condition_placeholder_1); Array ( [:db_condition_placeholder_0] => bartik [:db_condition_placeholder_1] => en-gb ) in Drupal\locale\CurrentImportStorage->get() (line 68 of /home/shirmkth8bfz/public_html/windsofhawi.com/drupal/core/modules/locale/src/CurrentImportStorage.php).

Below that is a much longer backtrace. Will post it if necessary. Any ideas?

drupal-wiki.com, why is it called that way? I mean does it have anything from Drupal? Seems like a closed system which isn't open-source obviously.

We have a content type with a multi-select field with (let's say) options A, B, C, D. A ton of nodes already have the field populated with content. We need to add an option E, and would like to have it selected if B is also already selected.

Is Views Bulk Operations with Views Bulk Edit our best (or only) option?

Codex can build / fix modules, develop the core of Drupal today, almost no developer needed already, what will be the future for this type of software communty ?

We've audited a lot of Drupal 7 sites this year.

Same things keep showing up.

Modules nobody uses but nobody removed either. They just sit there. Unmaintained. Invisible until they're not.

Integrations the original developer built in 2016 and never wrote down. Current team has no idea what connects to what. We've had to reverse-engineer CRM connections from database logs because there was no other record they existed.

Custom themes nobody wants to touch. PHPTemplate, built when the site launched, last modified when someone added a banner in 2020. The institutional knowledge of how it works left with whoever built it.

PageSpeed scores under 40 on mobile. Not because the hosting is bad. Because nobody has looked at performance since the site went live.

And no process for security advisories. Drupal published 30 in July 2026 alone. Most of these teams knew about zero of them.

The one thing the better-maintained sites have in common: someone actually runs Upgrade Status and does something with what it finds. That's it. Not complicated.

Curious what others are seeing out there. Same patterns or different?

Did anybody go to day one?

If so, how was it? I can't really find any videos from it online yet... Seems like it's smaller than years prior?

The election for the community-elected At-Large board seat ends 14 August at 23:59 UTC.

If you’re a member of the Drupal Association as a Ripple Maker, check your inbox for a ballot from Helios voting bot with the subject line “Vote now: Drupal Association 2026 At-Large Board Election”.

Also do take a moment to learn about the 8 candidates running, and vote for the person who you trust to advocate for the things that you believe are important: https://www.drupal.org/association/board/elections/election-2026-dates-and-candidates

To quote an awesome person from Drupal slack: “We are going through a lot of change right now. The board, our community, our entire industry globally - everything is changing. This vote matters.”