Skip to content

Visitors see something different

Make the page look for visitors the way it looks for you. The usual causes are a cache in front of the page, Bootstrap missing for visitors, a text format filter, or a page saved by an older release.

Visitors see old content

A builder save clears Drupal's caches for that page, so old content usually comes from a cache outside the builder.

  1. Clear all caches. If the content updates, a Drupal cache was the cause.
  2. Go to Configuration > Development > Performance and check Browser and proxy cache maximum age.
  3. Behind Varnish or a CDN, install the Purge module or lower the maximum age for builder pages. DXPR Builder sends no purge requests.

Tip: a View placed in the page shows the rows of its own cache. If those rows are old, edit the View, open Advanced, set Caching to Tag based and clear caches.

Visitors see no styling or no icons

  • Columns, buttons and spacing look unstyled. Builder content needs Bootstrap 5 CSS, and your theme does not load it. Go to DXPR Studio > DXPR Builder > General Settings > Bootstrap and set Sideload Bootstrap files to Bootstrap 5.
  • The console refuses a stylesheet with MIME type text/html. The page points to an aggregated CSS file that no longer exists, and the server returned an error page instead. Clear all caches so pages point to current files.
  • Icons are missing on a page saved with an older release. The saved HTML lists the icon fonts the page needs, and older saves may lack that list. Open the page in the editor and save it.

Scripts or embeds are stripped for visitors

Editors see raw builder content. Visitors see it after the text format filters when Apply text format filters to frontend content is on at General Settings > Text Filters.

  1. Turn that setting off, or give the field a text format without HTML restrictions.
  2. Put third-party scripts in an HTML element. The builder removes <script src> tags from every other element.
  • Nothing reacts to clicks, or the console says bootstrap is not defined. Carousels, tabs and collapsibles run on Bootstrap 5 JavaScript, and the page has none for visitors. Set Sideload Bootstrap files to Bootstrap 5, or load Bootstrap 5 from your theme.
  • The carousel does not move on its own. Disable auto-play is ticked in the carousel settings. Untick it, set Auto-play interval, and save.
  • Counters, parallax or video backgrounds stay still after an update. The editor decides at save time whether a page needs the builder's front-end script. Open the page and save it again.

Confirm the fix

Open the page in a private window. Content, styling and interactive elements match what you see with View mode set to Preview.

What's next?

Caching for the cache layers that apply to builder pages.

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