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.
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.
One morning in October, Luciano Galfione walked through his family’s textile factory in Buenos Aires, a cavernous warehouse where some of the more than 100 employees spin, knit, and dye...
With AI, headless CMS, and composable architectures growing fast, where do you see Drupal developers fitting in by 2026? What skills do you think will matter most?
I'm trying to migrate content from a WordPress site to a fresh Drupal 11 installation using the contributed wordpress_migrate module (the UI/GUI process).
I'm running into an issue where the module's setup UI fails to detect my destination fields, likely because my Drupal structure uses modern, non-standard field types (Media Entity Reference) and custom machine names, while the module expects the old default settings.
I need advice on the correct YAML configuration to manually map these fields.
1. 📝 Body Field Issue
The WordPress content body (content:encoded) is not being recognized for import.
Drupal Destination Field Name:field_content
Drupal Field Type:Text (formatted, long)
Expected Field Type (by Module): Likely the standard body field with type Text (formatted, long, with summary).
Goal: How should I structure the process: section in my migrate.migration.wordpress_post.yml to map content:encoded to my existing field field_content?
2. 🖼 Featured Image Issue (Crucial: Media Entity)
I cannot map the WordPress Featured Image because my Drupal setup uses the modern Media Entity reference approach.
Drupal Destination Field Name:field_featured_image
Drupal Field Type:Entity reference (Referencing Media Entity of type Image).
Expected Field Type (by Module): Likely a basic Image file field type.
Goal: What is the recommended multi-step process: pipeline (using file_copy, entity_generate, or migration_lookup) to take the WordPress image URL, create a Media Entity in Drupal, and reference it in my field_featured_image field? Working YAML examples for migrating WXR attachments to Media Entities would be highly appreciated!
3. 💬 Comments Migration
The WXR file contains comment data. Is there any hope to migrate comments (users, body, timestamps) to the native Drupal comments using the wordpress_migrate module or does this typically require another separate migration definition?
The Covid-19-era bubble had not yet burst when the CEO sat down to write an email, hoping to woo Tiger Global. It was early on in the pandemic, and he...
Dec 15, 16:19 UTC Resolved - From 08:28 to 13:03 UTC, Our Engineering team observed an issue with Spaces Access keys for DOCR in AMS3 region. During this time, users encountered an error with "403 (InvalidAccessKeyId): The access key ID you provided does not exist in our records" while accessing spaces keys. Our team has fully resolved the issues as of 13:03 UTC. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
On paper, Singapore is a terrible location for a data center. With average temperatures hitting 33 degrees Celsius (91 degrees Fahrenheit) and relative humidity levels of above 80%, the country...
I found this Views Migration module on Drupal.org — it helps you migrate Views from Drupal 7 to Drupal 10/11 easily! 🚀
🔹It lets you import your D7 Views via the UI or using Drush commands. 🔹You can also import specific views using --idlist and roll them back if needed. 🔹Works with Drupal ^10 || ^11 and is maintained with stable releases. 🔹Useful for migrating Views that otherwise aren’t handled by the core Migrate API.
If you watched the DrupalCon Vienna keynote and wanted to actually try the stuff shown on stage (Canvas, AI workflows, site templates, orchestration, etc.), we just published a working demo you can spin up in seconds.
What you get: • A fully configured Drupal 11 site modeled after the keynote • Canvas + AI features wired up (AI requires adding a secret in DevPanel) • Runs in a cloud dev environment — no Docker, no local setup • You can break it, inspect it, edit it, rebuild it • Good for learning, experimenting, or agency demos
We are huge fans of SimplyTest.me for quick, ephemeral testing. However, we noticed a gap in the ecosystem for when you need a dev environment that lasts longer than a few hours but doesn't require a full local Docker setup.
With Drupal Forge, we’ve built a system based on DevPanel that allows environments to auto-pause rather than being deleted after 6 hours, allowing you to "un-pause" and pick up where you left off later.
My question for the devs here: Do you find yourself using Cloud IDEs (like GitPod or our VS Code integration) for actual collaborative coding? Or do you strictly use these tools for quick demos?
We are trying to decide if we should double down on features like "Real-time Collaboration/Parallel Programming" or focus more on simple template hosting.
Gutenberg editor is enabled in content types and available gutenberg blocks are placed in nodes. Now client wants to migrate these blocks to one of other Drupal website of there’s. One option is they can be mapped to paragraph types. Second option mapped as custom blocks. There are approx 200 nodes with gutenberg blocks.
This is Drupal to Drupal migration. Can any one please guide in this ?
One in five new cars sold globally is now electric. So what’s it actually like to own one? Are EV drivers constantly hunting for chargers and sweating over battery percentages,...
Dec 11, 00:00 UTC Resolved - From 18:57 UTC to 22:05 UTC, customers may have experienced issues accessing the Recovery Console due to a service interruption. During this time, Droplet functionality remained unaffected, and customers were still able to use the Recovery ISO option via SSH.
Our Engineering team has confirmed that the issue is now fully resolved, and Recovery Console access has been fully restored and is operating normally.
If you continue to experience any difficulties, please open a ticket with our Support team. We apologize for the inconvenience caused.
Dec 10, 22:43 UTC Monitoring - Our Engineering team has deployed a fix to resolve the issue causing the Recovery Console to be unavailable.
We are currently monitoring the situation to ensure access is fully restored and stable. Please note that Droplet functionality was not impacted by this issue.
We will post another update once we confirm the issue is fully resolved.
Dec 10, 20:33 UTC Investigating - Our Engineering team is actively investigating an issue causing the Recovery Console to be unavailable.
Droplet functionality is not impacted. If customers need recovery iso, they can still select the "Boot from Recovery ISO" option in the recovery tab as seen in the guide here https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-iso/ but will need to use SSH to access their droplets.
We apologize for the inconvenience and will share an update once we have more information.
Dec 10, 19:08 UTC Resolved - As of 18:15 UTC, our Engineering team has confirmed the issue impacting accessibility of App Platform static websites has been resolved. Service has been restored and are now functioning normally.
We appreciate your patience and regret the inconvenience caused. If you continue to experience any issues, feel free to open a Support ticket for further investigation.
Dec 10, 18:41 UTC Monitoring - Our Engineering team has implemented a fix impacting the availability of App Platform static websites. Users should now experience improved performance when accessing the sites.
We are actively monitoring the situation and will provide an update once we can confirm the issue has been fully resolved.
Dec 10, 18:08 UTC Investigating - Our Engineering team is currently investigating an issue impacting App Platform static websites. During this period, users may notice 404 Not Found errors while accessing the sites.
Our team is actively working on identifying the root cause and implementing the fix.
We apologize for the inconvenience and will share an update once we have more information.
Login
Drupal - Open Source Content Platform | #Celebr8D8
