BugWP logo BugWP
Back to Community
Home / Community / Plugin → Page builder by siteorigin

Troubleshooting Common Page Builder by SiteOrigin Plugin Conflicts

32 threads Sep 9, 2025 Plugin → Page builder by siteorigin

Content

Page Builder by SiteOrigin is a powerful tool, but like any WordPress plugin, it can sometimes conflict with other elements of your website. Based on community reports, here are the most common types of conflicts and how to systematically resolve them.

Common Symptoms of a Plugin Conflict

  • The Page Builder interface does not load on a page or post.
  • Content appears correctly in the editor but not on the front end.
  • Widgets or rows that should be side-by-side stack vertically.
  • Third-party shortcodes, forms, or elements (like Google Maps) do not display.
  • Modals or popups from other plugins appear behind the Page Builder interface.

How to Identify the Conflict: The Baseline Test

The most reliable method to identify a conflict is to perform a baseline test. This process helps you determine whether the issue is caused by another plugin or your theme.

  1. Switch to a Default Theme: Temporarily activate a default WordPress theme like Twenty Twenty-One or Twenty Twenty-Two. If the issue is resolved, the conflict is likely with your original theme.
  2. Deactivate All Other Plugins: If the issue persists after switching themes, deactivate all plugins except for Page Builder by SiteOrigin. If the problem is now fixed, you know another plugin is causing the issue.
  3. Reactivate One-by-One: Reactivate your other plugins one by one, checking your site after each activation. When the problem returns, you have found the conflicting plugin.

Specific Conflict Scenarios and Workarounds

1. Optimization & Minification Plugins (e.g., Clearfy)

Problem: These plugins can break the layout, causing rows and widgets to stack incorrectly.

Solution: Go into the optimization plugin's settings (often under settings like Performance > Minify) and deactivate all HTML, CSS, and JavaScript minification and combination settings. Reactivate them one by one to identify the specific setting causing the problem.

2. Gravity Forms with Conditional Logic

Problem: Forms may not appear when inserted using the Gravity Forms widget.

Solution: Instead of the dedicated widget, insert the form using its shortcode inside a SiteOrigin Editor widget. Be sure to untick the "Automatically add paragraphs" setting in the widget.

3. Z-Index Conflicts (e.g., MP Timetable)

Problem: Popup windows from other plugins appear behind the Page Builder interface.

Solution: This is typically a styling issue (CSS) that the other plugin's authors need to resolve. They need to increase the z-index value of their modal popups. A temporary workaround is to build the element (e.g., a timetable shortcode) on a page without Page Builder, copy the shortcode, and then paste it into a SiteOrigin Editor widget.

4. iFrame and Script Embeds (e.g., Google Maps)

Problem: Embedded content like Google Maps shows in the editor but is blank on the front end. This is a known limitation within certain widgets like Tabs, Tiles, and Accordions.

Solution: Embed maps or iframes using a Custom HTML widget placed directly in a row or column, rather than nested inside another widget. For complex layouts, the SiteOrigin Premium plugin offers a Tabs addon that resolves this specific issue.

5. TinyMCE Editor Extensions Not Loading

Problem: Buttons for other plugins (e.g., kk Star Ratings) do not appear in the toolbar within Page Builder text widgets.

Solution: This often requires the third-party plugin to ensure compatibility. Contact the support for the plugin whose button is missing for further assistance.

What to Do After Finding a Conflict

Once you identify the conflicting plugin or theme, you have a few options:

  • Check for Updates: Ensure both Page Builder and the conflicting software are updated to their latest versions.
  • Seek Support: Report the issue to the support team of the other plugin or theme. Providing them with details helps them create a fix.
  • Look for Alternatives: If the conflict cannot be resolved, you may need to find an alternative plugin that provides similar functionality without conflict.

By methodically testing and using these workarounds, you can usually resolve conflicts and get your site building back on track.

Related Support Threads Support