Issue After Updating Jetpack Plugin

  • Resolved Manoj Jamble

    (@manoj239)


    2 months, 2 weeks ago

    Hi Team,

    We are encountering an issue after updating the Jetpack plugin to the latest version on our live site.

    After the update, opening any page on the site triggers a search popup automatically. The popup appears to be broken, and it does not display a close button. Because of this, the popup blocks the page and makes it inaccessible to users. This behavior is unexpected, as the search popup is not intended to appear on those pages.

    We tested the same update on our staging environment, where the latest version of the plugin works correctly and the issue does not occur. However, on the live site the problem persists immediately after the update. Refer this screenshot.

    As a temporary workaround, we reverted the plugin back to version 15.1.1, and the site functions normally again without the popup issue.

    Could you please help us identify what might be causing this behavior on the live environment and advise on how we can safely update the plugin to the latest version?

    Please let us know if you need any additional information such as screenshots, console logs, or environment details.

    Thanks!

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support fujifika (a11n)

    (@fujifika)

    2 months, 2 weeks ago

    Hi @manoj239 ,

    Thanks for the detailed report and for the great troubleshooting you’ve already done!

    The behavior you’re describing, Jetpack’s Instant Search overlay auto-opening on every page load and appearing broken/frozen, is actually something we’ve seen before. The root cause in that case was WP Rocket’s JavaScript file optimization interfering with how Jetpack Search initializes. I can see that your site is using WP Rocket so it’s likely that this could be the cause here too.

    When WP Rocket minifies, combines, or defers Jetpack Search’s JS assets, it can break the overlay’s event handling, causing it to trigger on page load instead of only when a user clicks the search button.

    To resolve this:

    1. Go to WP Rocket > Settings
    2. Under Excluded JavaScript Files (WP Rocket guide), add the following (one per line):
    /jetpack/
    jp-search
    i18n-loader
    wp-i18n
    1. Save your settings
    2. Clear all caches – both WP Rocket’s cache and any server-level or CDN cache (I see you’re also running Cloudflare, so purge that cache as well)
    3. Then update Jetpack to the latest version

    These exclusions ensure WP Rocket leaves Jetpack Search’s JavaScript untouched.

    If the issue persists after applying these exclusions and clearing caches, let us know and we might need to ask for some more details!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    2 months, 1 week ago

    Hello @manoj239,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter Manoj Jamble

    (@manoj239)

    2 months, 1 week ago

    Hi Stef,

    Thank you for following up. We applied all the suggested exclusions, cleared WP Rocket’s cache, purged Cloudflare, and updated Jetpack to the latest version — however, the Instant Search overlay is still auto-opening and remaining frozen on every page load on the live site.

    One interesting detail worth noting: the issue does not replicate on our staging site, which has the same configuration.

    Could you let us know what additional details or logs would help narrow this down? Happy to provide whatever is needed.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    2 months, 1 week ago

    Hello @manoj239,

    Thanks for the updates 🙂 If I understand correctly, the Search overlay issue is only happening on your live site, while everything works fine on staging, and you’ve already gone through the checks from the forum thread. Is that right?

    Since the configuration is the same, this usually points to something specific to the live environment. To help us narrow it down, could you please check a couple of things:

    • Browser console errors: Open your browser’s developer tools (Console tab), reproduce the issue, and let us know if you see any red error messages (a screenshot is perfect).
    • Logged-in vs logged-out: Does the issue happen in both cases, or only when logged in/out?
    • Caching / CDN / security layers: since the live site behind something like Cloudflare or another CDN, and/or using any server-level caching or security features (bot protection, script optimization, etc.) it’d be good to turn them off again and see what happens.
    • Just to double-check, are there any differences between staging and live in terms of:
      • active plugins (including must-use plugins)
      • theme or child theme files
      • optimisation settings

    If possible, also check the Network tab in your browser tools and see if any requests related to search or WordPress.com are failing.

    This should help us pinpoint what’s interfering with the overlay on the live site; we’re happy to take a closer look once we have that info 👍

    If you’re not comfortable in sharing all this info in this public forum, you can contact us via this contact form and mention this thread. Look forward to your reply, thanks!

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

You must be logged in to reply to this topic.