• Resolved knowledgearc

    (@knowledgearc)


    after activating the plugin, the dreaded error in the topic title occurs, deactivating the plugin fixes it. but it wasn’t a problem until after installing yoast, but then after uninstalling yoast, the error remains. possibly with another plugin there is a conflict, but i renabled all other plugins and all isfine unless i activate otter

    its unfortunate as i was using the columns one but cant now and have it on existing pages

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • I am having the same issues, it just started. Activating Classic Editor helps, but when I switch to Block Editor, I get the same error message.

    Plugin Author Hardeep Asrani

    (@hardeepasrani)

    Hey there,

    We tried to reproduce this issue on our side and weren’t able to reproduce. Can you both provide us with the following information so we could try to reproduce it?

    • Which version of WordPress are you using?
    • Which version of Otter are you using?
    • Can you provide us with the list of the active plugins and active theme?
    • Are you using regular WordPress or WordPress Multisite?
    • Which user role are you currently using?

    It will also be great if you could open your browser console. And send us a screenshot of the generated errors when you open Block Editor which causes the error.

    Here’s a guide on how to open browser console on different browsers: https://webmasters.stackexchange.com/questions/8525/how-do-i-open-the-javascript-console-in-different-browsers#77337

    Thank you for the report. We would love to help you out and eliminate this error from our plugin.

    I deactivated all plugins and activated one by one, and found it was Jetpack. After deactivating Jetpack, everything was working again.

    Plugin Author Hardeep Asrani

    (@hardeepasrani)

    Thanks. Same happens with WooCommerce Blocks + Otter, which is caused by WooCommerce and we’ve already reported this issue to them.

    It’s possible Jetpack is using the same code as WooCommerce as they’re from the same company. We will investigate this error and update you what’s causing it.

    Are things smooth as before once you’ve deactivated Jetpack?

    They are, everything working perfectly, thanks. ??

    Plugin Author Hardeep Asrani

    (@hardeepasrani)

    I tried a site with Jetpack installed (Free version with all Modules active) and couldn’t reproduce this issue. ??

    Is there anything I’m missing?

    Thread Starter knowledgearc

    (@knowledgearc)

    Atomic blocks was also causing the problem but they pushed out an update that fixed it.

    Will gather some info for you

    Thread Starter knowledgearc

    (@knowledgearc)

    This morning, after activating otter, the error is no longer there. Perhaps Atomic making an update somehow affected Otter?

    Plugin Author Hardeep Asrani

    (@hardeepasrani)

    @knowledgearc So this is not happening anymore?

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘The editor has encountered an unexpected error. Attempt Recovery Copy Post Text’ is closed to new replies.