Troubleshooting

5 min read Updated

The Page Builder Tab Is Missing

The Page Builder tab shows only on the post types you enable. Pages and posts are enabled by default. To add the tab to another post type, such as a custom post type from a plugin:

  1. Go to SettingsPage BuilderGeneral.
  2. Under Post Types, select the post type.
  3. Click Save Settings.

The Page Builder tab shows in the Classic Editor. If the post opens in the Block Editor, add a SiteOrigin Layout block instead, or see Which Editor Opens.

Page Builder Could Not Load This Layout

Page Builder shows this notice when it can’t build the saved layout in the editor:

Page Builder could not load this layout. Updating the page will not save the incomplete builder view; reload to try again.

The layout data may be damaged, or a script error stopped the builder while it loaded the layout. Page Builder locks the builder to protect your layout. You can’t edit the layout until it loads. If you update the page, Page Builder keeps the saved layout as it was.

To fix it:

  1. Click Reload page.
  2. If the notice shows again, note the error message below it.
  3. Temporarily deactivate your other plugins, apart from Page Builder and the SiteOrigin Widgets Bundle, and reload the page. If the layout loads, activate the plugins again one at a time to find the conflict.
  4. If the layout still doesn’t load, restore an earlier revision of the page. Page Builder saves the layout with each revision.

If you need help, post the error message on the support forum.

Missing Widgets

Widgets come from WordPress core, plugins and themes. If you add a widget to a page and then remove the plugin or theme that provided it, the widget is missing. In the builder, it shows as Missing Widget, or under its usual name if Page Builder knows which plugin provides it. To fix it:

  1. Go to PluginsSiteOrigin Widgets. The SiteOrigin Widgets Bundle lists its widgets here, and so do plugins that add widgets to it, such as Livemesh SiteOrigin Widgets. A plugin can be active while one of its widgets isn’t. Activate the widget. If a page uses a Widgets Bundle widget that you deactivated, the Widgets Bundle activates it again for you.
  2. If you can’t find the widget there, go back to the page you’re editing and open the missing widget. Its form shows the widget’s class name, and the plugin to install if Page Builder knows it. Use this to find the plugin or theme that provided the widget, then check whether that plugin or theme is active.

Styles Missing or Wrong With Caching or Optimization Plugins

Caching and optimization plugins can move, combine or delay CSS. If a Page Builder layout looks broken, or its styles load late, check these settings at SettingsPage BuilderLayout:

Page Builder Layout CSS Output Location
Where Page Builder prints the CSS for each layout.

  • Automatic is the default. When you view a page built in the Page Builder interface, its CSS goes in the header. The CSS for layouts that load later, such as SiteOrigin Layout blocks and widget areas, usually goes in the footer.
  • Header puts the CSS for layouts built in the Page Builder interface in the header. The CSS for SiteOrigin Layout blocks and widget areas usually still goes in the footer.
  • Footer puts all layout CSS in the footer.

If your optimization plugin expects all the CSS in one place, try Footer.

Inline Styles
Outputs the main margin, border and padding styles inline, in the HTML of each row, column and widget, to reduce potential Cumulative Layout Shift. Mobile and tablet styles still come from the layout CSS. It is disabled by default.

After you change a setting, clear your caching plugin’s cache and check the page again.

There Is a Newer Version of This Widget’s Content Available

There is a newer version of this widget’s content available.

The notice has Restore and Dismiss buttons. It warns that Restore replaces the current widget contents, and that you can revert by refreshing the page before you update it.

SiteOrigin Widgets Bundle widgets show this notice when your browser has a newer copy of the widget’s content than the saved widget. The Widgets Bundle keeps this copy to protect unsaved changes. Unsaved changes usually happen when you leave or reload the editor before you save. If you have no unsaved changes, click Dismiss. If you do, click Restore to bring them back.

The browser keeps this copy only for the current browser tab. If the notice keeps showing when you haven’t made changes, click Dismiss, or close the tab and open the editor in a new one.

Migrating from Page Builder – Think Up Themes Compatible

Page Builder – Think Up Themes Compatible is a fork of SiteOrigin Page Builder. After a plugin is forked, the forking author, in this case Think Up Themes, is responsible for its development and support. To move from the forked version to SiteOrigin Page Builder:

  • Uninstall the forked versions of SiteOrigin Page Builder and the SiteOrigin Widgets Bundle.
  • Install SiteOrigin Page Builder and the SiteOrigin Widgets Bundle.
  • Replace the Think Up Themes widgets with SiteOrigin widgets.

Think Up replaces our widgets with theirs, so you can’t carry over widget data. Back up your site before you make this change. Test the move on a local or test server first if you can.