Flatsome UX Builder not loading

Hi @kanikawadhawan

I’m waiting for the builder+theme from the authors. As soon as I have it I will check
But in your case, it looks like you have a Content Security Policy that prevents the iframe of the editor from loading.
Check the file .htaccess. It looks you have X-Frame-Options set to both DENY and SAMEORIGIN. You should keep only SAMEORIGIN. If you don’t find it in htaccess, you have maybe a plugin that adds the policy X-Frame-Options.

In any case, this has nothing to do with Specific Content For Mobile.
But I don’t exclude that after solving the issue related to the content security policy you will still not be able to load the editor on the mobile pages like the other users. I think you have two issues.

For the cause related to Specific Content For Mobile, I can help as soon as I have the builder. For the content security policy, I can only suggest checking the .htaccess file and if other plugins add a content security policy in the backend.

I have the same problem builder does not load image (just showing loading…) and displays errors at console

Hi @patentapc

I will be happy to solve this conflict with Flatsome, but I’m still waiting for an answer from the authors. This is a premium theme, and I still don’t have it available.
If you want, you can share the zip files of the theme and builder and I will check. Maybe doing so will be faster than waiting for an answer from the authors.

In that case, please send me the sharing link using the contact form at https://josemortellaro.com/contact/

Hello @patentapc @itsmeade @kanikawadhawan

the authors of Flatsome very kindly provided me with the theme and I was able to solve this issue on my installation.
The next version of the plugin will definitively fix it. Until it’s public you can solve it by installing Freesoul Deactivate Plugins. Do the following:

• Install and activate Freesoul Deactivate Plugins https://www.ads-software.com/plugins/freesoul-deactivate-plugins/
• Go to Freesoul Deactivate Plugins => Custom URLs => Frontend URLs (important, FRONTEND, NOT BACKEND, because the editor loads the page inside an iframe)
• Add a row and write exactly this: *uxb_iframe*
• Disable Specific Content For Mobile on that row
• Save the options

You should not have problems anymore. IF you still have problems let me know.
The new version of Specific Content For Mobile will be published in a couple of days if you prefer to wait.

I can’t find where exactly write that “uxb_iframe”

• Install and activate Freesoul Deactivate Plugins https://www.ads-software.com/plugins/freesoul-deactivate-plugins/
• Go to Freesoul Deactivate Plugins => Custom URLs => Frontend URLs (important, FRONTEND, NOT BACKEND, because the editor loads the page inside an iframe)
• Add a row and write exactly this: *uxb_iframe*
• Disable Specific Content For Mobile on that row
• Save the options

Please see this picture: https://freesoul-deactivate-plugins.com/wp-content/uploads/2022/01/fdp-disable-specific-content-for-mobile-on-ux-editor.png

You will have no rows in the beginning. Click on “Add URL” to be able to write *uxb_iframe*.

Of course, you need to install Freesoul Deactivate Plugins if not done yet.

Hi everyone, Thanks for the plugin which is great and intuitive. In my case if that can help you, I had the same problem as most of the people here. When I wanted to make changes on my page, the page got stuck on “Loading Ux Builder”.

This happened on some sites and others not, I deduced that it perhaps came from a plugin, after having investigated, I was able to find the cause, for my part it is “W3 Total Cache” , when I turn it off it fixes the problem. this was due to a new option they had set up in this plugin, I unchecked that and reset the configuration to default and problem solved.

Hello @akdconception @patentapc @itsmeade @kanikawadhawan

The new version of Specific Content For Mobile fixes the issue with UX Builder.

If you have similar problems caused by other plugins, you can now use Editor Cleanup For Flatsome.
It’s an add-on of Freesoul Deactivate Plugins, that should be also installed.
After activation, you will find “Editor Cleanup” under the admin menu of Flatsome, and you can disable all the plugins that prevent the editor from loading.

I have the same problem with my website. I have downloaded the Editor Cleanup For Flatsome, but still, whenever I create a new blog post and open with the UX Builder, the wheel keeps spinning forever.

However, when i open the other pages that i have published already, it’s working. May i know how i could fix the issue?

Hi @veroleung

I can’t reproduce the problem. All works without problems for me.

Have you tried completely disabling Specific Content For Mobile? This is to be sure the problem is really caused by SCFM. If the problem still occurs with SCFM disabled, we will check why Editor Cleanup For Flatsome is not helping.

First, I would like to confirm that I have and did the same as you.

Is WordPress updated to v. 5.8.3? Do you have the last version of Specific Content For Mobile (0.1.8.3)? Is maybe your installation a multisite?

This is what always works for me:

– Go to Editor Cleanup => Outer Editor => disable all the plugins
– Go Editor Cleanup => Inner Editor => disable all the plugins
– Go to Posts
– Click on Add New
– Click on Edit with UXBuilder

If it doesn’t work, have a look at Plugins => Must-use. Do you see any mu-plugin there?
Can you also check if you have one of these files?:

wp-content/advanced-cache.php
wp-content/db.php
wp-content/db-error.php
wp-content/install.php
wp-content/maintenance.php
wp-content/object-cache.php

Depending on your answers I will give you more suggestions

Does this have a fix

When I click “Edit with UX Builder” I get spinning wheel forever

When I click “Edit product layout with UX Builder” it works but I don’t want to edit the whole layout just the specific page.

This is what I get in the console:

Uncaught TypeError: Cannot read properties of null (reading 'insertBefore')
    at index.js?ver=3.2.1:2:120601
    at Module.<anonymous> (index.js?ver=3.2.1:2:120651)
    at Module.283 (index.js?ver=3.2.1:2:120655)
    at a (index.js?ver=3.2.1:2:1328)
    at wc.app.0 (index.js?ver=3.2.1:2:4053)
    at index.js?ver=3.2.1:2:4064

Hi @giodev1

are you sure the issue is caused by Specific Content For Mobile and that you have the last version 0.1.8.6 for Specific Content For Mobile?
It seems the console shows a problem related to WooCommerce or a WooCommerce add-on.

Have you disabled Specific Content For Mobile to be sure it’s the cause of the issue?

Try Editor Cleanup For Flatsome. It’s an add-on of Freeesoul Deactivate Plugins. So you need both of them.

I suggest you do the following:

Install and activate Freesoul Deactivate Plugins if not active yet
Install and activate Editor Cleanup For Flatsome
Go to Flatsome => Editor CLeanup

1) Click on “Outer editor cleanup”, disable all the plugins, and save. Do you have again the error?
2) Click on “Inner editor cleanup”, disable all the plugins, and save. Do you have again the error?
3) Click on “Editor actions cleanup”, disable all the plugins, and save. Do you have again the error?

If the error disappears:
4) Enable Specific Content For Mobile in the outer editor. Do you have again the error?
5) Enable Specific Content For Mobile in the inner editor. Do you have again the error?
6) Enable Specific Content For Mobile in the actions. Do you have again the error?

Please, give me the answers for 1), 2), and 3)
If the error disappears, please, give me the answers also for 4), 5), and 6).

If you realize that Specific Content For Mobile is not the cause of the issue, Use Editor Cleanup For Flatsome to understand which plugin is giving the issue.

Remember in the outer editor usually, you can disable all the plugins. In the inner editor, you should disable the same plugins that you would disable in the frontend. Usually, In the actions cleanup, you can disable all the plugins.

Did 1,2 and 3 and the problem still persists.

Hi @giodev1 if the problem persists it means Specific Content For Mobile has nothing to do with this issue.

To confirm it, please, disable Specific Content For Mobile in the page of plugins.
If you still have the same issue, I suggest you contact the authors of Flatsoome.