Issues

If you have the Classic Editor or Disable Gutenberg plugin activated, there is a chance that when you save the Builder on the frontend, it will generate a double Builder content badge in the editor.

To resolve the double Builder content:
- With the Classic Editor or Disable Gutenberg plugin still activated, edit the page in the backend, delete the double Builder content badge (or delete all) in the content editor, and save the page.
- After confirming that the double content is gone, disable the Classic Editor or Disable Gutenberg plugin to avoid this issue happening again.

If you have mod_pagespeed enabled on your server, please disable it. It can cause conflicts to prevent the Builder from turning on.

If you have "Mollie Payments for WooCommerce" plugin activated, the frontend Builder will not load the modules correctly. There are a lot of console errors caused by the plugin. Once you disable the plugin, the frontend Builder will load properly. If you experience this issue, please report to the plugin's author. As a temporary solution, you can disable that plugin when you need to edit the frontend Builder. Reference: https://themify.me/forum/topic/issue-builder-with-mollie-payments#post-938187

A recent update from Site Kit plugin also affected Themify Updater. If you are receiving an error message related to Site Kit & Themify Updater, please report to Site Kit's author. Reference: https://themify.me/forum/topic/themify-updater-error#post-939246

If you are using Themify v7 and Cloudfare and encountering issues (eg. things not working properly), check if you have Rocket Loader enabled. Please disable it. Rocket Loader is currently a beta feature and it is known to cause conflicts with a lot of third part scripts.

To disable Rocket Loader, open up your Cloudflare dashboard and go to the Speed tab. Scroll down to "Rocket Loader", and toggle the feature off.

If you have LiteSpeed Cache or Nginx-Cache installed on the server and see broken stylesheet like the screenshot below, it is likely due to the cache. To verify if it is related to the server cache: switch to another theme and then view the site with incognito (private) mode. If it doesn't show the theme that you've switched, the issue is related to the cache. Try to clear/disable the cache on the server.