And BTW I did “blackcloud” cloudflare to see if the issue was there and did not see a difference.
Hi there,
Thanks, I configured them correctly but no luck.
I saw similar issue too with multi-site before, and it’s because of HTML content. Example, let say you add Content Area element, the issue will be triggered but not with other elements. That’s because Content Area has default text that contains <span>. Try removing those HTML elements in your Content Area and it will work okay.
I’ll add this to our issue tracker but I’m not saying it’s a bug, not yet. Let’s wait for further inputs 
Thanks!
Thank you for this. Its my wish this will be worked out! I upgraded to Pro for this.
There was only one element with a Content Area and I can easily change that to a custom menu so no problem there.
I’l stand by for more imput
Sure, we can’t rule out that this is a bug since it works well on other users sites, and even on our installations. Hence, we’ll need more information so we can move forward
Thanks!
So I noticed code from Gramarly, a browser extension I was using , on some of the posts I was writing so I decided uninstall it from my computer.
This apparently solved the problem. I can now save headers.
Grammarly is an extension that corrects grammar right on your browser.
Your other users should be aware of this interaction between Gramarly and iframe
Hi there,
Thank you very much for taking the time and inform us here regarding the conflict. This will help our other customers if they encounter such an issue.
Thank you for your contribution to our community.
I’m having the same problem. Losing my mind over it! I’ve noticed that it seems to happen when I have too much data to save?
Have tried increasing the memory as mentioned about. But still having the issue?
Hey @kylehill,
Do you have Grammarly browser extension like @TaverasJose had? If not, try these other solutions:
-
If you’re using a CDN, please clear the CDN’s cache and disable optimization services.
-
Test for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
-
Remove custom CSS, Javascript and templates.
-
Reset your htaccess file by renaming it to
.htaccess-bak. Then in WP Admin Menu, go to Settings > Permalinks and just click the Save Changes button. -
Contact your host to increase your allocated memory or do it yourself by adding this code in your wp-
If nothing helps, open a separate thread and give us access to your WordPress admin and FTP in a Secure Note there.
Thanks.
One thing that CLEARLY causes this problem is using any text in your headers. If you open a field and use any form of text including headings, or text, that WILL make your headers disappear. Try creating one without text fields and see what happens.
Hey @TaverasJose,
Browser extensions like Grammarly have scripts that changes can alter contents in an input field. In the case of Grammarly, that is its main purpose. The reason why you could not save is its script conflicts with Pro. This is not a bug but rather a scenario that is unavoidable. If you’re building with Pro or any type of builder, it is best to use a browser without addons or extensions.
Thanks.
Adding double quotes " in custom html content (text on content area") like in
<span class="thisismyspanclass">Look at this wonderful text</span>
It will break your footer on Save operation.
When refresh the page the header / footer completely disappear from editing.
You will see it but when you click edit nothing happens. On site header / footer completely dissapear.
The only way to retrieve it is to manually modify the post (the ID of the post, you see it when hover EDIT button), by getting his content and correct the issue the content area, for the content area is around here:
_type": "content-area",
"_region": "footer",
"content": "<div class=
in the mysql database.
Any chance u can explain this further?
What I wanted to say is that before working again and again and lose time to do same headers / footers again you could retrieve that custom post ID from data base (at last recover and correct the code).
You will need access to the database and a tool like PhpMyAdmin or Adminer to access and modify the content of that specific post.
The Custom Builder save the content of headers and footers as custom post types, you will find them in the database. Go to a header / footer and hover the button edit to see it’s ID in the form of http://www.yourdomain.com/x/#/footers/10178 What you need is that number 10178 as in this exemple. Then go to database and search for “10178”, you will find some tables. From memory the content is in table wp_posts in the field post_content on the article with that ID.
Looking like this {"regions":{"footer":[{"title":"Bar 1","_type":"bar","_region":"footer","bar_base_font_size":"16px","bar_z_index":"10","bar_position_top":"relative","bar_margin_top":"0px","bar_margin_sides":"0px","bar_scroll":false,"bar_bg_color":"#f4f4ed",..........
Copy that content and use a Json editor to find the “content” that you want to modify. There are some online like https://jsonformatter.org/json-editor that could format the code to a readable version.
The problem consist in Builder not correctly saving the JSON content, thus making errors on page render. Until developers can reproduce and admit this bug, we users can’t do anything but help each other and get around the problem.
Cheers.
Hi there,
Thank you for the input. It seems that you have problems saving the Header/Footer. That is impressive that you do have the skills to change things around but most probably there is something going on your installation that the save is not working.
Please kindly open up a separate thread and give us detailed information about the case and we will be more than happy to help you around and find the problem cause.
If it is something related to our code we will create a detailed report and if possible the solutions as a bug to our development team.
If it is an environmental factor we will try to rule out some common cases and ask you to do different kinds of tests to make sure about that.
Thank you for your understanding and cooperation.
Hi again in this thread this was written:
"I saw similar issue too with multi-site before, and it’s because of HTML content. Example, let say you add Content Area element, the issue will be triggered but not with other elements. That’s because Content Area has default text that contains . Try removing those HTML elements in your Content Area and it will work okay"
This is true. Adding text elements to a content area will trigger this error.
Is there any way around this? Text elements are an essential part of these content areas and its a pitty not to be able to add written content in them. A shortcode maybe?
Hi there,
From what I can tell it’s a multisite conflict. Regretfully I don’t have a workaround or solution to offer at this time. We’ll look into why that could be failing in multisite for a future release. You should still be able to use text elements, but don’t add custom HTML elements inside them.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.