Skip to content

The editor does not appear

You open a page and nothing happens when you point at the content, or the controls show but the settings dialog never opens. Work through the causes below in order. The first four cover most cases.

I am on the node edit form

The editor runs on the page itself, not on the edit form. Save the node, open the page and point at the content area. The editor also stays off on revision pages, such as /node/12/revisions/34/view.

The page shows a product key or licence message

The editor stays off while one of these messages shows:

  • "DXPR Builder needs a product key to work". No product key is set. Go to DXPR Studio > DXPR Builder > General Settings (/admin/dxpr_studio/dxpr_builder/settings) and fill in the License section.
  • "Oops, the no-code editor is not loading here". The message names the cause: too few user licences, the content item limit of your plan, or an account without a valid email address. Follow Licence and product key errors.
  • "Access to DXPR Builder is blocked because of a payment or licensing problem". DXPR blocked the site's domain. Contact DXPR through the link in the message.

The console shows 401 or 403 errors from cdn2.dxpr.com

With Asset source set to Cloud, the editor scripts load from cdn2.dxpr.com with your product key in the URL. A 401 or 403 means the CDN rejected the key. Check the License section of General Settings, then follow Licence and product key errors. If the requests time out instead, a firewall blocks the CDN; see Using DXPR Builder behind a firewall.

The editor stopped after an update

  1. Run drush updb -y (or visit /update.php).
  2. Run drush cr.
  3. Open one builder page and save it again.

If the log reports a missing file inside the module folder, the code on the server is incomplete. Reinstall the code:

  1. Delete the modules/contrib/dxpr_builder folder.
  2. Run composer require drupal/dxpr_builder.
  3. Run drush cr.

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

The controls show, but settings dialogs never open

The console shows bootstrap is not defined, or an error about getOrCreateInstance. The editor's dialogs run on Bootstrap 5 JavaScript. The page has none, or the theme loads Bootstrap 3 or 4 instead.

  1. Go to General Settings and open the Bootstrap section.
  2. If your theme does not load Bootstrap 5, set Sideload Bootstrap files to Bootstrap 5 and click Save settings.
  3. If your theme loads Bootstrap 3 or 4 JavaScript, stop loading it or switch to a Bootstrap 5 theme.

The console shows a JavaScript error from another script

Another script on the page is breaking the editor. In support tickets the culprits were cookie consent banners, tag managers, a MailChimp embed and a New Relic browser agent. Themes caused it too, through a Webpack bundle or their own Bootstrap 3 or 4 JavaScript, and so did JavaScript minifiers.

  1. Go to Configuration > Development > Performance and turn off JavaScript aggregation. Reload.
  2. Disable consent, analytics and monitoring modules one at a time. Reload after each.
  3. Switch to a core theme such as Olivero for one test.

What the result tells you:

  • Fixed by step 1: a minifier is the cause. The editor's helper libraries, such as Sortable, are aggregated with the rest of the page, so Sortable is not defined with aggregation on points here. With Advanced CSS/JS Aggregation, change the minifier from JSqueeze to JSMin.
  • Fixed by step 2: keep that module disabled on editing pages, or report the conflict to its maintainer.
  • Fixed by step 3: the theme's JavaScript is the cause. Stop loading Bootstrap 3 or 4 JavaScript from the theme, and set Sideload Bootstrap files to Bootstrap 5.

The page shows "The website encountered an unexpected error"

The log shows a stack trace through DxprBuilderService that names a View or a block class from another module.

For editors, the builder lists every View display and block plugin so you can add them to pages. For every visitor, it renders the blocks and Views placed in the page. One broken View or block that throws an error in either step takes the page down.

  1. Open Reports > Recent log messages and find the View or module named in the trace.
  2. Fix or delete that View, or disable that module.
  3. Clear all caches.

The editor never shows on one content type

  1. Go to Structure > Content types > (type) > Manage display.
  2. Set the format of the builder field to DXPR Builder.
  3. Repeat for every view mode that renders the field, not only Default.

Note: the editor needs a field with a value to attach to. When you save a node, DXPR Builder fills an empty field that uses the DXPR Builder format in the Default display. A node saved before you changed the format stays empty: edit it and save it once.

Only some users see the editor

Check these for the account that sees no editor:

  1. At People > Permissions (/admin/people/permissions), the role has Edit with DXPR Builder.
  2. The role may also edit that content, for example Basic page: Edit any content. The editor loads only for users who can update the page.
  3. The account has a valid email address. Licensing needs one.
  4. On the user's edit form, Exclude from DXPR builder editing is not ticked.
  5. At DXPR Studio > DXPR Builder > User Profiles, the profile for that role has Start editor when page loads ticked. When it is off, the controls appear only after a click on the eye icon of the container controls.

Another editor locked the content

A warning says "The content ... is locked by" a colleague, and the container shows only a Locked button. That editor clicked into the container and has not saved yet; the lock clears when they save. Ask them to save, or click Locked and confirm to take over. If you both keep editing, the last save wins.

Confirm the fix

Reload in a private 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?

Problems after updating if the editor broke right after a release.

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