• Resolved janew

    (@janew)


    I don’t know who needs to hear this, but viewing Console without Jetpack I have no issues. After installing Jetpack, Console shows one Error and one Warning.
    Error:
    VM45:1
    Uncaught SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at XMLHttpRequest.xhr.onload (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:3010)
    at XMLHttpRequest.send (<anonymous>:1:774)
    at Object.wpLikes.displayWidget [as success] (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:3015)
    at Object.ajax (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:2206)
    at Object.success (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:2968)
    at ??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:2220
    at Deferred.execute (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:1511)
    at Deferred.resolve (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:1514)
    at receive (??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:1658)

    Warning:
    ??/wp-content/js/postmessage.js,/wp-content/js/jed/jed.js,/wp-content/js/wpcom-proxy-request.js,/wp-content/js/likes-rest-nojquery.js?m=20200826:3007
    [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help, check https://xhr.spec.whatwg.org/.

    I don’t know what any of that means, and it doesn’t seem to affect the site, so maybe it’s not important, but wouldn’t it be nice to provide a plugin that doesn’t throw errors?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello,

    We’re sorry to see that you’re getting this issue. We’re not able to replicate this issue with the latest version of Jetpack and WordPress.

    Can you please do the following steps and let us know the result?

    – Make sure that your site is up-to-date with WordPress 5.6, Jetpack 9.2.1, and other themes and plugins.
    – Where did you see this issue? Please give us the link. Feel free to redact your site address.
    – Does the issue persist if you disable all other plugins except Jetpack, and switch your theme to a default theme like Twenty Twenty? NOTE: please make a backup of your site including both files and database before doing this.

    Thread Starter janew

    (@janew)

    Yes, fully up to date WordPress and Jetpack. Error and Warning both occur with all other plugins disabled. Running TwentyTwenty with a child theme. Shows on Post not on Page.
    Sorry, can’t share the link.

    Plugin Support Jen H. (a11n)

    (@jennywp)

    Hi @janew,

    I’m not sure this is related to Jetpack, so I’d also recommend reaching out to your web host’s customer service team to see if they have any guidance to offer as well.

    Are the Error and Warning showing up in multiple different browsers, or is it specific to a single browser?

    Thread Starter janew

    (@janew)

    Original post error message copied from Chrome. This is Firefox:

    Uncaught SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
        onload jQuery
        send https://widgets.wp.com/likes/master.html?ver=202052#ver=202052&lang=en-ca:1
        jQuery 7
            displayWidget
            ajax
            success
            makeProxyCall
            execute
            resolve
            receive

    The issue is that we’re not able to replicate the issue on our end. We need to have a look at your site.

    As you do not want to post your site address here, please contact us via this contact form. Please include a link to this thread.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Error and Warning’ is closed to new replies.