Normal view

Received — 17 December 2025 Drupal - Open Source Content Platform | #Celebr8D8

Module Spotlight: Changelogify

Module Spotlight: Changelogify

Hey Drupal community!

I want to highlight a really useful module I’ve been exploring called Changelogify. If you manage Drupal sites where tracking and communicating what’s changed over time matters, this thing can be a serious quality-of-life boost. 

What It Is

Changelogify is a contributed Drupal module that helps you automatically collect changes happening on your site and publish them as a public changelog. It listens for various site events, groups them into releases, and then makes those changes visible in a structured way on your site. 

Why It’s Handy

Whether you’re maintaining a client site, building a product with frequent updates, or just want better visibility into what’s happened between deployments, this module lets you:

• Automatically capture tweaks and updates instead of manually jotting them down • Organize changes into releases so editors and users can see what changed and when • Surface a public changelog that keeps stakeholders informed and helps reduce support questions 

It takes a lot of the manual bookkeeping out of tracking what’s happened during a sprint or over a release cycle. 

Who Might Like It

• Site builders who deliver regular feature updates • Teams with editors who want transparency into site revisions • Maintainers who want a lightweight way to publish update history without crafting change logs by hand 

If you’ve ever wished Drupal could write its own release notes for you, Changelogify is worth checking out.

🔗 Drupal.org project page: https://www.drupal.org/project/changelogify

Have you tried it yet? What workflows do you use for keeping changelogs up to date on your Drupal projects?

submitted by /u/don__swan
[link] [comments]

Certain Drupal batch functions not working with Cloudflare - returning 502 Bad Gateway

I noticed that the XML Sitemap generation stopped working a couple of weeks ago. When I go to rebuild the sitemap manually, we immediately get a 502 Bad Gateway error.

After much unsuccessful troubleshooting, we tried the Simple XML Sitemap module and surprisingly got the same error.

Disabling Cloudflare fixes the issue but since we need Cloudflare to be active, we need to find out the cause.

  • Using Cloudflare Free Tier
  • Some /batch functions cause a 502 error
  • Pausing Cloudflare fixes the issue
  • We tried creating a rule to bypass caching for the /batch path (no change in the error)
  • The issue occurs with XML Sitemap, and Simple XML Sitemap. However, other batch operations, like rebuilding the permissions work as expected
  • Sitemap generation worked correctly for years, until a couple of weeks ago

I'm hoping for any insight as to what may be causing the failure.

submitted by /u/quantumized
[link] [comments]
❌