• Resolved Fionder

    (@fionder)


    Hi
    I was checking this website this morning and found that the shortcode I had used for Featured Image Pro Post Grid was not working and there was a blank space after the introduction paragraph. When I tried to edit the page and save it I got a message:

    Updating failed. The response is not a valid JSON response.

    On investigation I established that this is an issue with WordPress 5.6 and on reverting to a backup just before this update was applied it worked again.
    Please can you advise if an update to the plugin is required. As the page concerned is particularly important, I will leave this website on WordPress 5.5.3 until I can get this resolved.
    Thank you.

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

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author A. Jones

    (@nomadcoder)

    Hello. I went to your page and see that the grid is not showing up. I looked at the console and I see a lot of jQuery errors due to jQuery not being loaded by WordPress. This plugin uses jQuery to display the grid after it’s been loaded.

    I did some google searches. This appears to be an issue with version 5.6. I will look into it further, but suggest that you stick with 5.5.3 for now.

    Failed to load resource: the server responded with a status of 404 ()
    jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js:1 Failed to load resource: the server responded with a status of 404 ()
    jquery.min.js,qver=3.5.1.pagespeed.jm.buo63cp1wa.js:1 Failed to load resource: the server responded with a status of 404 ()
    jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js:1 Failed to load resource: the server responded with a status of 404 ()
    cnss.js?ver=1.0:1 Uncaught ReferenceError: jQuery is not defined
    at cnss.js?ver=1.0:1
    frs.js?ver=2.3.1:1349 Uncaught ReferenceError: jQuery is not defined
    at frs.js?ver=2.3.1:1349
    jquery.touchSwipe.min.js?ver=5.6:1 Uncaught ReferenceError: jQuery is not defined
    at jquery.touchSwipe.min.js?ver=5.6:1
    at jquery.touchSwipe.min.js?ver=5.6:1
    (index):125 Uncaught ReferenceError: jQuery is not defined
    at (index):125
    (index):41 Uncaught TypeError: Cannot read property ‘1’ of null
    at window.onerror ((index):41)
    (index):131 Uncaught ReferenceError: jQuery is not defined
    at (index):131
    (index):41 Uncaught TypeError: Cannot read property ‘1’ of null
    at window.onerror ((index):41)
    core.min.js,qver=1.12.1.pagespeed.jm.1DE5hzT0_K.js:1 Failed to load resource: the server responded with a status of 404 ()
    sortable.min.js,qver=1.12.1.pagespeed.jm.-9YQN_SHUy.js:1 Failed to load resource: the server responded with a status of 404 ()
    core.min.js,qver=1.12.1.pagespeed.jm.1DE5hzT0_K.js:1 Failed to load resource: the server responded with a status of 404 ()
    (index):367 Uncaught ReferenceError: jQuery is not defined
    at (index):367
    at (index):367
    (index):41 Uncaught TypeError: Cannot read property ‘1’ of null
    at window.onerror ((index):41)
    sortable.min.js,qver=1.12.1.pagespeed.jm.-9YQN_SHUy.js:1 Failed to load resource: the server responded with a status of 404 ()
    (index):369 Uncaught ReferenceError: jQuery is not defined
    at (index):369
    (index):41 Uncaught TypeError: Cannot read property ‘1’ of null
    at window.onerror ((index):41)
    superfish.min.js?ver=1.7.10:10 Uncaught ReferenceError: jQuery is not defined
    at superfish.min.js?ver=1.7.10:10

    Thread Starter Fionder

    (@fionder)

    Thanks for this. Yes, I restored a backup, which was working, but then WordPress decided to update itself again automatically to 5.6 (which is probably about the time you visited the website)! I have re-restored the backup and have now stopped WordPress from updating automatically and the grid is showing OK for now, but would be grateful if you are able to fix it. Thanks for your help – much appreciated!

    Plugin Author A. Jones

    (@nomadcoder)

    Unfortunately, this is more of a troubleshooting issue than an issue with the plugin.

    It looks like your website might load properly if you disable pagespeed. Pagespeed might be loading an external version of jQuery and this may not work with 5.6. I will see if there is anything that I can do on my end but my plugin will not be the only thing that will not work since many plugins rely on jQuery.

    Thread Starter Fionder

    (@fionder)

    Thank you for this. The Pagespeed function is part of the Blogvault plugin, so I have put in a support request to them. I will keep you updated.

    Thread Starter Fionder

    (@fionder)

    I have just deleted the Blogvault plugin and upgraded to WP 5.6, but got the blank page back, so it doesn’t appear that this is the problem.

    Plugin Author A. Jones

    (@nomadcoder)

    Do you have the ability to create a staging site? Don’t do it yet. I need to look at a couple of things, but some trouble shooting might be required and it would be best for us to do it on a staging site.

    Thread Starter Fionder

    (@fionder)

    Yes, I can create a staging site on Blogvault.

    Plugin Author A. Jones

    (@nomadcoder)

    I was able to verify that the plugin works with version 5.6.

    The first line of errors in the console indicates that the jQuery file can not be found.

    Failed to load resource: the server responded with a status of 404 ()
    jquery-migrate.min.js,qver=3.3.2.pagespeed.jm.Ws-UgblvVg.js:1 Failed to load resource: the server responded with a status of 404 ()

    A 404 error indicates that the file can not be found. Because I see ‘pagespeed’ in the error message, I assumed that this file was being loaded by pagespeed. Some caching applications load an external jQuery file. I think that changes were made to WP 5.6 that disallow this,

    I know what is causing the error, not where it is coming from. I also know that this issue would be causing issues with several plugins that are installed on your site, not just this one.

    The way to resolve this is to go through standard troubleshooting steps. Ideally on a staging site, but you can do this on your live site if necessary.

    Disable caching during the troubleshooting phase & update to 5.6

    1. disable all plugins except for featured image pro. See if the issue is still occurring. If it is, please try switching to a different theme, like twenty-twenty or twenty-twenty-one. See if that resolves the issue. If it does, the issue is with your theme. If it doesn’t, the issue is with this plugin. You can stop here and follow up with me.

    2. If featured image pro works, re-enable each plugin one at a time until the problem occurs. That should help you to narrow down the issue.

    • This reply was modified 4 years, 2 months ago by A. Jones.
    • This reply was modified 4 years, 2 months ago by A. Jones.
    Plugin Author A. Jones

    (@nomadcoder)

    #2: Going back to your original issue while editing – “Updating failed. The response is not a valid JSON response.”

    I have seen this before. It may just be an issue with the block editor. I don’t use it unless a client insists on it, and they never do. This may also be resolved if jQuery is loaded properly.

    • This reply was modified 4 years, 2 months ago by A. Jones.
    Thread Starter Fionder

    (@fionder)

    I have just tried creating a staging site on Blogvault, updated it to WordPress 5.6 and it works perfectly! I am therefore wondering if it could be an issue on the server as I think that is the only difference between the live site and the staging site?

    Thread Starter Fionder

    (@fionder)

    I have the plugin on another site at https://bucks-fizz.biz/members/ and it is working ok on the front end on that site, but it is showing the message in the page editor Updating failed. The response is not a valid JSON response.

    Plugin Author A. Jones

    (@nomadcoder)

    Please check with your host regarding the jQuery issue, hopefully they can figure it out.

    Are you using the block editor? Did you place the shortcode into a shortcode block?

    Thread Starter Fionder

    (@fionder)

    Hi
    Even though I had disabled automatic updates in wp-config.php, WordPress updated to 5.6 again overnight. However, the plugin now seems to be working OK and is displaying correctly. I did install the Classic Editor plugin yesterday but at the time it didn’t seem to make any difference. So whether that has caused it to display normally I really don’t know.
    Thanks so much for your help – much appreciated.

    Plugin Author A. Jones

    (@nomadcoder)

    Interesting! I’m glad that it’s working now.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Plugin has stopped working on WordPress 5.6’ is closed to new replies.