Skip to content

Problems after updating

Finish an update that went wrong. In nearly every case the code was updated but the database was not, a leftover copy of the module is in the way, or a dependency is missing.

Run the update in the right order

  1. Back up the database.
  2. Run composer require drupal/dxpr_builder, with a version constraint if you pin releases.
  3. Run drush updb -y (or visit /update.php).
  4. Run drush cr.
  5. Open one builder page and save it again.

Important: never uninstall the module to update it. Uninstalling deletes saved templates, profiles and settings.

Composer shows an error

  • "Could not find a version of package drupal/dxpr_builder matching your minimum-stability". 3.x is published as beta releases. Allow them in the constraint: composer require 'drupal/dxpr_builder:^3.0@beta'.
  • "Could not find a matching version of package dxpr/dxpr_builder". The package on drupal.org is drupal/dxpr_builder. Replace dxpr/dxpr_builder with drupal/dxpr_builder in composer.json, then run composer update drupal/dxpr_builder.
  • Composer refuses because the folder is not managed by Composer. A copy was uploaded by hand. Delete modules/contrib/dxpr_builder and run the require command again.
  • "Disk quota exceeded" or "write failed". Free disk space on the server before you retry.

The database update fails

  • "Unable to install modules key due to missing modules key". 3.x needs the Key module, and update 9020 installs it. Its code is missing because the module was not installed with Composer. Run composer require drupal/key, then drush updb -y again.
  • A named update hook fails. Run drush updb -vvv and include the full error in your ticket.
  • "module 'dxpr_builder_page' is missing its dependency module field_group". The DXPR Builder Drag and Drop Page submodule needs Field Group. Run composer require drupal/field_group, then drush en dxpr_builder_page -y.

Pages look broken after the update

Some releases convert old markup, such as Owl carousels and circle counters, in batches during drush updb. Items that fail stay pending.

  1. Go to DXPR Studio > DXPR Builder > Content items > Migrations (/admin/dxpr_studio/dxpr_builder/migration-status).
  2. If a migration shows Pending, click Run now, or Run all pending migrations.
  3. Check Reports > Recent log messages for the items a batch skipped.

Composer refuses a Drupal core major upgrade

DXPR Builder 3.x supports Drupal 10.1 and later, and Drupal 11.

  1. Check the release notes of DXPR Builder, DXPR Theme and DXPR Theme Helper for the version that supports the new major.
  2. Run Upgrade Status to see which packages are not ready.
  3. Pin the core major in composer.json. An unconstrained composer require drupal/core-recommended can pull the next major by accident.

The editor broke right after the update

Follow The editor does not appear. The top causes there are the ones that follow a partial update: pending database updates, stale files, and an aggregation cache built from the old release.

I am migrating from Glazed Builder

DXPR Builder 3.x no longer converts Glazed class names in stored content. Update to the last 2.x release first and run its database updates, then update to 3.x. See Migrating from DXPR Builder 1.x or 2.x.

Confirm the fix

drush updb reports no pending updates, drush pm:list --filter=dxpr shows the intended versions, and a re-saved builder page renders the same in the editor and for a visitor.

What's next?

Updating DXPR Builder for the routine update procedure.

Something wrong or missing on this page? Report it or edit the page.