Update DXPR Builder.

Keep the module current with Composer and `drush updatedb`

Learn DXPR BuilderStart hereInstall and update

Update DXPR Builder to get bug fixes, new features and security fixes. You update the code with Composer, then let Drupal convert settings and content with drush updatedb. Use this page for updates within the 3.x series. Coming from 1.x or 2.x? Follow Migrating from DXPR Builder 1.x or 2.x instead.

Before you start

  • Back up the database:

    drush sql:dump > backup-$(date +%Y%m%d).sql

  • Read the Changelog and the GitHub releases page for changes that need action, such as the move to Font Awesome 7.

  • Try the update on a staging copy of the site first.

Update the module

  1. Update the code:

    composer update drupal/dxpr_builder --with-dependencies

  2. Run the database updates. You can also visit /update.php instead:

    drush updatedb

    Some updates convert every DXPR Builder field value in batches. On large sites they take minutes, not seconds.

  3. Rebuild the caches, so browsers receive the new style sheets and scripts:

    drush cache:rebuild

What you see

Pages with DXPR Builder content look as they did before. Hover one as an editor and the control bars appear; make a small change and click Save to check that saving works. General Settings still shows your product key under License.

DXPR Builder general settings page

Then open Reports > Status report (/admin/reports/status). Next to DXPR Builder content migrations it says All migrations completed.

If you don't see the new version

  • The editor still behaves like the old version. The browser keeps the old editor files. Reload with Ctrl+Shift+R, or Cmd+Shift+R on a Mac.
  • The status report says "Some DXPR Builder content migrations have not been completed". Content still waits for conversion. Open View migration status in that message, or go to /admin/dxpr_studio/dxpr_builder/migration-status, and click Run all pending migrations.
  • Pages look wrong or elements are missing. See Problems after updating for the causes and fixes.

If the update breaks the site and nothing above helps, roll back:

  1. Restore your database backup:

    drush sql:cli < backup-20260901.sql

  2. Restore the version you were on, for example 3.0.0-beta19:

    composer require 'drupal/dxpr_builder:3.0.0-beta19'

  3. Rebuild the caches:

    drush cache:rebuild

What's next?