---
url: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/troubleshooting/after-updating'
title: 'Problems after updating | DXPR'
author:
  name: docs-sync
  url: 'https://dxpr.com/users/docs-sync'
date: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: article
summary: 'Something broke right after an update'
tags:
  - 'Fix a problem'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  updated_time: '2026-10-23T14:31:17+0000'
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
schema:
  '@context': 'https://schema.org'
  '@graph':
    -
      mainEntity: {  }
    -
      '@type': TechArticle
      headline: 'Problems after updating'
      description: 'Something broke right after an update'
      image:
        '@type': ImageObject
        url: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
        width: '1200'
        height: '630'
      datePublished: '2026-10-23T14:31:17+0000'
      dateModified: '2026-10-23T14:31:17+0000'
      author:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      mainEntityOfPage: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/troubleshooting/after-updating'
      articleSection: 'Fix a problem'
    -
      '@type': WebPage
      '@id': 'https://dxpr.com/hc/documentation/learn-dxpr-builder/troubleshooting/after-updating'
      description: 'Something broke right after an update'
      breadcrumb:
        '@type': BreadcrumbList
        itemListElement:
          -
            '@type': ListItem
            position: 1
            name: Home
            item: 'https://dxpr.com/'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
      inLanguage: en
---
[Help Center](/hc)/[Documentation](/hc/documentation) /[Learn DXPR Builder](/hc/documentation/learn-dxpr-builder) /[Manage the site](/hc/documentation/learn-dxpr-builder/manage) /[Fix a problem](/hc/documentation/learn-dxpr-builder/troubleshooting) # Problems after updating.

Something broke right after an update

 Learn DXPR BuilderManage the siteFix a problem

   ## In this guide

 Related guides

- [Updating](/hc/documentation/learn-dxpr-builder/getting-started/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.2 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](/hc/documentation/learn-dxpr-builder/troubleshooting/editor-not-loading). 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](/hc/documentation/learn-dxpr-builder/getting-started/migration-1x-to-3x).

## 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](/hc/documentation/learn-dxpr-builder/getting-started/updating) for the routine update procedure.