Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Chris

    (@nordtomme)

    Quick follow-up and note: I realized that this actually is more critical than I first said. I can’t edit any posts (not just posts using Selz) while the plugin is active, and my Selz shortcodes don’t work while the plugin is inactive. So if you how either of us might fix this, that would be much appreciated. ??

    Plugin Author Selz

    (@selz)

    Hi Chris,

    Apologies that you’re seeing this. We’ll take a look and try and get a fix out for this ASAP.

    Thanks
    Sam

    Plugin Author Selz

    (@selz)

    Hi Chris (@nordtomme),

    Are you able to supply us the following info as we’re struggling to reproduce the issue here:
    – WordPress version
    – Selz plugin version
    – The content of the post which is causing the issue

    Or is there a public page we can see with the problematic content on?

    Cheers
    Sam

    Thread Starter Chris

    (@nordtomme)

    I’m using the latest version of both WordPress and the Selz plugin.

    It happens to pretty much all my posts, but not necessarily straight away. It is perhaps connected to trying to add images to a post.

    I can give you admin access to a development version of the site, if you want to investigate. Send me an email at christian at skriftlig dot no (from the Selz address you want associated with the account), and I’ll set it up. ??

    Thread Starter Chris

    (@nordtomme)

    New update:
    It seems like there’s more than one thing that can trigger the error, but the quickest way to reproduce it for me, was to drag’n’drop an image into the editor. (The expected behavior would be that the image got uploaded and inserted into the post. The actual behavioris that the image is uploaded, but error occurs when trying to insert it.)

    Trying to insert an image through the regular image block also creates an error, which blocks access to the media library.

    I tested with previous versions of the plugin, going backwards one version at the time. As far as I can tell, the last version that did not cause this problem was v. 1.9.3.

    Plugin Author Selz

    (@selz)

    Hey Chris,

    Thanks for your help with this. We’ve found a fix and deployed the fix in the latest version. Please update the plug-in and report back.

    Regards,
    Sam

    Thread Starter Chris

    (@nordtomme)

    Great! Thanks. I’ll have a look later today.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘“The editor has encountered an unexpected error”’ is closed to new replies.