- This topic has 3 replies, 2 voices, and was last updated 6 years, 7 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
I see this has been reported before but I repeatedly see this error only when using sections:
FWIW I see this with WP when using other tools like Visual Composer, and Site Origin Page Builder. I’ve seen this across multiple versions of WP, using different browsers, and on different hosts. There’s something in Sections and other page builder tools that trips this error.
Any ideas on a permanent fix?
Thanks,
Paul.
Hi Paul,
Can you tell us which plugin is triggering it?
If it’s triggered by a plugin I’m not quite sure if we can fix it?
The sections add-on is like a simple page builder itself so you shouldn’t use it with other page builders.
Let us know 🙂
GP Premium or specifically the Sections tool is what triggers the error. Stop using Sections and the error never occurs. I haven’t used Sections with any other page builders – I have seen the same error in the past when I have used other page builders. They all trigger the same error immediately after making a change and hitting the update button.
Hmm like Tom mentioned in that post GP doesn’t give such error.
Can you try disable all non-GP plugin and see if it’s still there when Sections is activated?
GeneratePress
© 2024 EDGE22 Studios LTD.