--- url: 'https://dxpr.com/markdownify/taxonomy/term/1023' title: 'Fix a problem | DXPR' author: name: Anonymous updated: '2026-10-23T14:31:17+00:00' copyright: 'Copyright DXPR. All rights reserved.' type: website summary: "Fix the most common DXPR Builder problems in a few minutes. Pick the row that matches what you see. Each page lists the causes that come up most often in DXPR support, with the fix, and ends with a check that proves it worked. I want to ... Use Needs get the editing controls back on a page The editor does not appear Access to the browser console clear a licence warning or a rejected product key Licence and product key errors Administer DXPR Builder configuration keep my edits after a reload Changes do not save The browser's Network tab upload images and keep them on the site Images do not upload or disappear Access to the media settings show visitors what I see in the editor Visitors see something different A private browser window repair one element that looks or acts wrong An element looks or behaves wrong A test page finish an update that went wrong Problems after updating Composer and Drush fix an AI feature AI troubleshooting AI settings access Do these five checks first Most tickets are solved by one of these steps. Go to Configuration > Development > Performance (/admin/config/development/performance) and click Clear all caches, or run drush cr. Run pending database updates at /update.php, or run drush updb -y. Run drush pm:list --filter=dxpr and compare the versions with the latest release on drupal.org. Press F12, open the Console tab, reload the page and note any red error. Create a new empty page, add one Text element and save it. If that works, the problem is in the original page's content or in something it loads. Before you open a ticket Include these details in your first message. Support asks for them every time, and tickets without them take a day longer. DXPR Builder, Drupal core and PHP versions The exact error text from the browser console and from Reports > Recent log messages (/admin/reports/dblog) Whether it also happens on a new empty page Whether it also happens with consent banners, tag managers and aggregation modules disabled A one-time login link to a staging copy, if you can share one Confirm the fix Reload the page in a private browser window and point at the content area. The container bar shows View mode, More and Save, and the console shows no red errors. What's next? Editor basics explains each control once the editor is loading." tags: - 'Manage the site' image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg' published: true og: site_name: DXPR 'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.' --- ## [Fix a problem ](/hc/documentation/learn-dxpr-builder/troubleshooting) Fix the most common DXPR Builder problems in a few minutes. Pick the row that matches what you see. Each page lists the causes that come up most often in DXPR support, with the fix, and ends with a check that proves it worked. | I want to ... | Use | Needs | |---|---|---| | get the editing controls back on a page | [The editor does not appear](/hc/documentation/learn-dxpr-builder/troubleshooting/editor-not-loading) | Access to the browser console | | clear a licence warning or a rejected product key | [Licence and product key errors](/hc/documentation/learn-dxpr-builder/troubleshooting/licence-and-product-key) | **Administer DXPR Builder configuration** | | keep my edits after a reload | [Changes do not save](/hc/documentation/learn-dxpr-builder/troubleshooting/saving-fails) | The browser's Network tab | | upload images and keep them on the site | [Images do not upload or disappear](/hc/documentation/learn-dxpr-builder/troubleshooting/images-and-media) | Access to the media settings | | show visitors what I see in the editor | [Visitors see something different](/hc/documentation/learn-dxpr-builder/troubleshooting/visitors-see-something-else) | A private browser window | | repair one element that looks or acts wrong | [An element looks or behaves wrong](/hc/documentation/learn-dxpr-builder/troubleshooting/elements-look-wrong) | A test page | | finish an update that went wrong | [Problems after updating](/hc/documentation/learn-dxpr-builder/troubleshooting/after-updating) | Composer and Drush | | fix an AI feature | [AI troubleshooting](/hc/documentation/learn-dxpr-builder/ai/troubleshooting) | AI settings access | ## Do these five checks first Most tickets are solved by one of these steps. 1. Go to **Configuration** > **Development** > **Performance**(`/admin/config/development/performance`) and click **Clear all caches**, or run `drush cr`. 2. Run pending database updates at `/update.php`, or run `drush updb -y`. 3. Run `drush pm:list --filter=dxpr` and compare the versions with the latest release on drupal.org. 4. Press F12, open the **Console** tab, reload the page and note any red error. 5. Create a new empty page, add one Text element and save it. If that works, the problem is in the original page's content or in something it loads. ## Before you open a ticket Include these details in your first message. Support asks for them every time, and tickets without them take a day longer. - DXPR Builder, Drupal core and PHP versions - The exact error text from the browser console and from **Reports** > **Recent log messages** (`/admin/reports/dblog`) - Whether it also happens on a new empty page - Whether it also happens with consent banners, tag managers and aggregation modules disabled - A one-time login link to a staging copy, if you can share one ## Confirm the fix Reload the page in a private browser window and point at the content area. The container bar shows **View mode**, **More** and **Save**, and the console shows no red errors. ## What's next? [Editor basics](/hc/documentation/learn-dxpr-builder/editing) explains each control once the editor is loading.