12 Nov 2026

feedDrupal.org aggregator

The Drop Times: Drupal and the Missing Photographer

A photo may carry its creator's name on a webpage but lose that information when downloaded. Maurice van Loon explains what he found on Dutch heritage websites and why he developed two Drupal modules to address attribution and media provenance.

12 Nov 2026 10:07am GMT

Stuart Clark (Deciphered): Consumer Node Preview 1.0.0-rc1; preview for Fully Decoupled Drupal sites

Drupal's preview screen with Frontend, Drupal and JSON:API tabs. The Frontend tab frames the druxtjs.org page Getting started with Druxt inside the site's own header and breadcrumb. A Show changes against the live page toggle is on and reports 2 changes: the title gains the words from zero, and in the first paragraph piece of content is struck through and replaced with page.

Press Preview on a Fully Decoupled Drupal site, and Consumer Node Preview 1.0.0-rc1 shows the unsaved page in the frontend your readers will see: the title you just changed and the text you just rewrote, rendered by the site that will publish them.

Drupal's own Preview renders the node in Drupal's theme, not your frontend, so editors save a draft to check it. Next.js draft mode smooths that workaround, but still needs a saved revision. Consumer Node Preview works on what's still in the edit form, for the person writing it, before anything is saved.

Anything that reads JSON:API can be on the other end. Druxt Node Preview 0.1.0 is the Nuxt one, already running druxtjs.org's previews.

Continue reading →

12 Nov 2026 9:00am GMT

Drupal Core News: Migration support for Drupal 6 and 7 sites will not be in Drupal 12

The Migrate Drupal module, which is required for migrating Drupal 6 and 7 sites, will be removed from Drupal core in the next major release, Drupal 12. Also removed is the Migrate Drupal UI module, which provides a basic user interface for running a migration. Both of these modules will not be moved to a contributed project, as is often done for removed extensions.

This means that legacy Drupal sites will not be able to migrate directly to Drupal 12 and later. Legacy sites should migrate to Drupal 11 and then upgrade to Drupal 12.

This was decided in [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL and also discussed in Future of migrate in core in a post Drupal 7 world.

Decreasing need for Migrate Drupal

The decision to remove the Migrate Drupal module is driven by several factors:

  • A strategic track for Drupal is modernization and we want all Drupal sites to enjoy the benefits of Drupal 11 and beyond.

  • Setting a clear deadline for sites to use Migrate Drupal in core may help some sites schedule the work without delay.

  • The percentage of Drupal sites using Drupal 6 or 7 continues to decline.

  • Sites can migrate to a supported release of Drupal up to 3 years after the end of life for Drupal 7 and 12 years after the end of life for Drupal 6. This is because Drupal 11 will be supported until mid to late 2028.

  • After 2028, it will still be possible to migrate to Drupal 11 in a development environment, then update to Drupal 12 (or beyond) prior to launching a site.

Migrate Drupal will not become a contributed project

Following from the above, Migrate Drupal will not become a contributed project

Migrate Drupal is coupled to many core extensions and it is technically difficult to move all the code to a single module. Moving the code to a single module is a required step in moving a core extension to a contributed project. That task would require a fair amount of contributor and committer time. Instead, we prefer to encourage that time and effort is spent on improving the Migrate API itself.

Recommendation

Drupal 6 and Drupal 7 sites should complete migrations to Drupal 11 by mid 2028.

12 Nov 2026 2:54am GMT