• Resolved Jean Pierre

    (@jeanpierre77)


    After the jetpack plugin update my website is showing an error:

    Doing some crawl with ahref it shows 302 errors

    Page has broken JavaScript
    Page has broken CSS
    Example:
    `https://topgrows.com/wp-content/plugins/monarch/js/custom.js?ver=1.4.14
    404

    Please et me know how can I fix this

    Thanks in advance.
    Jean pierre

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Anonymous User 18700194

    (@anonymized-18700194)

    Hi @jeanpierre77

    Looking at the example that you provided, this error is referencing a third-party plugin. Do you have an example that references Jetpack or more information on why you believe Jetpack is causing the error?

    Additionally, I see that Jetpack isn’t properly connected with your site. As a first step here, would you please delete Jetpack and then reinstall it? You can follow these steps to do that:

    1. Start at **Plugins** → **Installed Plugins**.
    2. If Jetpack is currently active, click **Deactivate** to disable it. Then click **Delete** to remove it from your site:
    3. Go to **Plugins**? → **Add New**.
    4. Search for “Jetpack by WordPress.com”.
    5. Click **Install** and then **Activate**.

    When Jetpack is installed, click the green **Set up Jetpack** button to reconnect.

    This handy guide explains that process in more detail:

    https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

    You shouldn’t lose any settings or any of your stats or subscribers in doing so, as that info is stored in our system here.

    Thread Starter Jean Pierre

    (@jeanpierre77)

    Thanks for your replay

    I had to disable the Jetpack plugin, because fatal WordPress error

    Do I have to switch it on?

    I think this was caused by the jetpack plugin because this error shown just after updating the plugin

    Plugin Support MadHatter (a11n)

    (@madhattersez)

    We would only be able to help troubleshoot if you get Jetpack active and connected again.

    If you make sure that all of your other plugins and core of WordPress are updated before uninstalling and reinstalling it, you shouldn’t see an error caused by Jetpack.

    If you do, though, please note the error here to let us know and we’ll take another look. Thanks!

    Thread Starter Jean Pierre

    (@jeanpierre77)

    Hi there,

    I already did all tasks:

    jetpack is active (after deleting and re-instal, and connected again)
    All themes, plugins and WordPress are up to date, and with no issues.

    I did a crawl with ahref and I still get the same error:
    https://stats.wp.com/e-202203.js
    Not crawled

    https://topgrows.com/wp-content/plugins/rocket-lazy-load/assets/js/16.1/lazyload.min.js
    404

    https://topgrows.com/wp-content/plugins/simple-sitemap/lib/assets/css/simple-sitemap.css?ver=3.5.4
    404

    Most likely, the JavaScript and CSS file had been moved, renamed, or deleted but the link to it was not modified.

    As I told you before this happens after updating Jetpack plugin and showing critical WordPress error

    Hope you can help me to solve this issue.

    Thanks in advance.

    Plugin Contributor Dan (a11n)

    (@drawmyface)

    Hi there

    Your stats appear to be working fine, so I wouldn’t worry about the stats js file showing as not crawled.

    The other two 404s are for separate plugins. If you see the same error when Jetpack is deactivated, then this is not related to Jetpack. You may want to try reinstalling those plugins to see if that helps.

    Note that our developers are aware of an issue that causes a fatal error when upgrading Jetpack, and we’ve confirmed this error shouldn’t cause any issues on your site. The error resolves itself during the process of updating the Jetpack plugin, and the error should not occur again now that the plugin update is complete.

    If you have any further questions, please let us know.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Page has broken JavaScript’ is closed to new replies.