Many have reported getting the “Front end conflict” when using SiteGround’s staging environment. We’ve been able to confirm this is because their staging provisioner does not properly update the site and WP urls. Our products use the WordPress “home_url” function to know how to talk to WordPress. Because SiteGround doesn’t update these URLs, any WordPress plugins using that function will reference the production site. This is very bad because it means you’re not in a truly isolated environment. So the “Front end conflict” error is because the application is unable to reach the server due to SiteGround misconfiguring the URLs.

As a workaround, you can go to Settings > General in your dashboard and update the URLs yourself to reflect the staging URL in your address bar. You’ll need to change it back before you push the staging changes to production.

SiteGround are actively looking into fixing their staging environment and in the mean time the above workaround should be sufficient.

In addition Cloudflares auto minification feature can break layouts and cause issues with the builder. In your Cloudflare speed settings make sure both JS and CSS minification is disabled. X and Pro already serve minified files which means having this feature enabled in Cloudflare will cause a re-minification of the files resulting in syntax errors and issues.

Table of Contents

• Flexbox
• Navigation
• Content Areas and Custom Content

Flexbox

Navigation

Content Areas and Custom Content

You will see options for both the primary icon and the secondary icon. The primary icon is for the “static” non interaction icon. The secondary icon is the “interaction” icon for when someone hovers over the menu item.

Table of Contents

• Introduction and the “Anchor” Partial
• The “Particle” Partial
• The “Dropdown,” “Modal,” and “Off Canvas” Partials
• The “Text” Partial
• The “Background” Partial
• The “Search” Partial
• The “Cart” Partial

Introduction and the “Anchor” Partial

The “Particle” Partial

The “Dropdown,” “Modal,” and “Off Canvas” Partials

The “Text” Partial

The “Background” Partial

The “Search” Partial

The “Cart” Partial

Caching

If you have caching plugins installed please ensure you’ve cleared all caches and disabled the plugin and have removed any defines they may add to the wp-config.php. For example W3 Total Cache adds two defines to the wp-config.php. In addition make sure all code added by any caching plugin has been removed from the .htaccess file.

Cloudflare

If you are using Cloudflare, it should be either temporarily disabled when building your site and making modifications or ensure */x/* is added to your page rules for exclusion within your Cloudflare settings.

Custom Code

If you have added any custom code to either your child themes functions.php or custom CSS/JS within the editors. Ensure that all code is validated, there are no errors or incorrect outputs. Any incorrect code could potentially cause issues and break the editor.

Security Plugins and Custom Hosting Rules

It is known that some security plugins and also hosts security rules may block the content builder endpoints. If you’re experiencing the issue mentioned in this article. Try temporarily disabling any security plugins you may have active and contact your host for assistance.