- This topic has 17 replies, 3 voices, and was last updated 2 years, 11 months ago by
.
-
Posts
-
I’m getting the terrible error: The editor encountered an unexpected error.
The error appears on all my websites that use Generatepress in the Safari browser. I don’t know what to do, that didn’t happen, and I only need to use safari for personal reasons. Other themes work normally without error.
Customer Support
Hi there,
the editor belongs to WordPress, and the Theme won’t cause it to error like that.
Its most likely a cache or plugin conflict.
First check the site in a Private Browser, as it has no cache and no extensions.If the issue persists, temporarily disable all plugins, clear the browser caches and try to edit a post.
Let me know.
I’ve already done all the tests, and the bug disappears if I use another theme, only in Generatepress that the error happens… On all my sites with different rules, even without a cache plugin… I’ve already tried to clear the browser cache and all the data, even so the bug continues, both in Safari and in Safari Bate and Anonmy.
Customer Support
Can you create a staging site for us to do some digging and provide an admin login via the private info field ?
Let me know!
Sorry for the delay, here’s the data… Really all websites with Generatepress are giving this, but only in Safari. Even after today’s update, the error continues. As much as it is fickle, the frequency is huge, it makes it impossible to write articles, clear cache, cache rules, different cache plugins, DNS, it’s no use.
Is this a staging site?
We will need to do some testing, and turn on/off plugins, we can not do this on a live site with traffic.
Let me know!
Yes, it’s a site that doesn’t get as much traffic! Like, almost zero!
Does the error persist if you disable the Child Theme ?
And how would i trigger this error ? I have edited a post in Safari ( 15.4 on MacOS 12.3 ) – is it on post save/update ?
The mistake is inconstant, but when it appears it is a sacrifice to disappear. I have to keep updating over and over again, clearing the cache and so on. Then one hour I can edit one or two posts, then the error comes back. Regardless of whether it is a Child or a parent theme.
Can you ask your host to enable debugging and see if they can provide an error log ?
Can I enable wordpress debugging or is it another type of debugging? I’ll see if I can find any nginx reports.
Enable WordPress debugging.
Debbug activated
let us know what’s in the error log 🙂
- You must be logged in to reply to this topic.
