when editing the page using frontend editor, the left panel to edit is blank.
SP Page Builder - Frontend editor, Left Panel Blank
11 replies
Hello
Apologies for the inconvenience. Thank you for the screenshot!
Could you please take a look at the documentation links below, to check if it helps you?
Hi Aria,
All the solution you gave are not related to my issue.
Hello , Ariba we are facing issue on front editor spbuilder
when we edit text area or title editor on frontend editor spbuilder so the left panel on edit is blank and on console we got the following error .
Uncaught ReferenceError: useGoogleFonts is not defined
Uncaught Error: Syntax error, unrecognized expression: #
and on the image edit it is working fine but text and title not working we check the above all solution but does not work for us.
please help us in this is very important for us.
We've moved the website to a staging environment for you to check
moved to staging environment for you to check
when editing the page using frontend editor, the left panel to edit is blank
Hi. This is a typical problem in conflict with third -party extensions or user scripts.
You should turn off one after another third -party extensions until you find the reason.
Hello pavel
I have checked deactivate all plugins one by one but does not work.
I think it is related with spbuilder 3.8.8 we have revert the site to older vesion 3.8.3 in other staging so sp builder works good but not working with updated version 3.8.8.
here is the staging link you need to check for us https://staging-nltsg-nltsgstaging.kinsta.cloud/
also provide us spbuilder 3.8.3 zip folder so we can install here and check.
I am also sharing staging access so you can you check the issue of spbuilder.
I really need to fix this please help help we are chasing you to resolve this since last week.
Hello Douglas
Your issue has been shared with our Senior Agent. He will look into it and get back to you as soon as possible. We appreciate your patience & cooperation very much.
Thank you!
this is a known bug in 3.8.8 .. I reported it over a week ago. I was reverted back to 3.8.7 and the issue was fixed.
Thank you Kieron for enlightening me. Can i know if the issue is fixed with the new update?