I’m primarily a Laravel dev with a mix of React and Vue. I’ve been just barely dipped my toe into experimenting with Drupal since a lot of the things I build are really centered around content management.

My question is how much of an uphill battle down the road will it be to integrate very customized fields into the admin UI? I’m thinking things like maps, basic multimedia editing, niche drag-and-drop stuff. If there’s a library or I have the hours to build it out in React this is pretty straightforward in Laravel, but I haven’t found a ton on this in Drupal. I don’t believe in forcing systems to do things that aren’t a good fit, and I’m wondering if I’m trying to fit a square peg in a round hole by looking at Drupal for this kind of thing.

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.

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?

Hi everyone,

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?

Thanks!

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.

Check it out: https://www.drupal.org/project/views_migration

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 ?