• Resolved cloudshift

    (@cloudshift)


    Hey,

    since the last update the PlugIn is now active for pages and there is no way to deactivate this. We hide the featured images at pages as they are not used so it was not possible to save any changes on any page any more without deactivating the plugin.

    Please exclude pages or make them optional as any other CPT.

    Thanks, Julian

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author MS

    (@corgmo)

    Hey Julian, this shouldn’t be an issue as the plugin checks if there is a featured image present on the post/page/cpt before checking the size, so if you don’t have any featured images added to your pages the check won’t happen and the page publishing will work as normal.

    Thread Starter cloudshift

    (@cloudshift)

    Well but still it does! There is no featured image and not even a box to add one because I hide it via CSS and still I got the error message of your plugin for all pages and nobody could save a page anymore. We’re using an NGINX server if this might be an issue.

    Plugin Author MS

    (@corgmo)

    Could you show the featured image box in the CSS and send me a screengrab of the error please, if that’s ok?

    Plugin Author MS

    (@corgmo)

    Also, if you create a new page, does the problem still happen?

    Hi!

    I am seeing this error as well. Have noted it for the last week or so. It causes Gutenberg to hit admin-ajax.php an average of 25 attempts per edit page load.

    Uncaught SyntaxError: Unexpected token < in JSON at position 0
        at JSON.parse (<anonymous>)
        at Object.success (mfis-admin-block-editor-scripts.js?ver=5.3.2:57)
        at i (jquery.js:2)
        at Object.fireWith [as resolveWith] (jquery.js:2)
        at x (jquery.js:4)
        at XMLHttpRequest.c (jquery.js:4)

    I am not sure if this is worth mentioning but when I noticed the error initially, it was hitting admin-ajax.php upwards of 200+ attempts per edit page load. My first response was to disable and then re-enable the plugin. In this case, the caching might have been helping repeat the editor load. Unsure.

    Plugin Author MS

    (@corgmo)

    @cloudshift – I’m closing this ticket as not had a response from you for about a week or so. Happy to reopen, if you’re still having issues.

    @harrowsmithmag can you start a new thread please with your support topic? It would be useful to see what the response is from the admin-ajax.php that is causing the JSON error. Could you add that to your new support topic please.

    Done and done!

    My other forum topic was sent for administrative review (not sure why) but for expediency…

    TypeError: Cannot read property 'requestContent' of undefined

    Plugin Author MS

    (@corgmo)

    Is that the response from the admin-ajax.php when you view it in the Network tab in dev tools? What you’ve sent just looks like a console error.

    Going to move this over to the new thread.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Not uable since last update’ is closed to new replies.