Manoj Jamble

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.

Hi team,
I tried cloning the site again using the recommended steps, including cloning the files first, removing Jetpack, adding wp_environment_type as staging in wp-config.php, and then cloning the database. The site still connected to the staging URLs.

I also tested multiple cloning approaches and found that if I remove the jetpack_options and jetpack_private_options entries from the database for each site in the multisite, before the first login, the sites do not connect to staging.
Additionally, the safe mode or fresh connection prompt is not appearing for this site.

One more request, I attempted to connect both live and staging so that the connections would not override each other, but after cloning, WordPress.com displayed two connections with staging URLs. This was confusing, and currently, WordPress.com still shows those staging URLs as connected, even though they are not connected from the WordPress dashboard.
Could you please remove the following staging URLs from WordPress.com/sites?

• https://wordpressmu-1371008-5139897.cloudwaysapps.com/
• https://staging.untimelybooks.com

Hi Sebastian,

Thank you for the update and for rechecking on your end.

I have coordinated with the hosting provider, and XML-RPC was previously restricted by a security rule. We have now allowlisted all Jetpack IP addresses as documented here:
https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

When accessing xmlrpc.php directly via a browser, the request is evaluated using our local IP addresses, which are not included in the allowlist. Jetpack’s servers however are now properly allowlisted, so the browser check does not reflect the actual Jetpack connection status.

Could you please run the connection test again from your side using the Jetpack service IPs? If any additional IP ranges need to be included, we can add those promptly.

Appreciate your continued assistance.

Hi,

I had added the WP_ENVIRONMENT_TYPE constant in the wp-config file for the staging environment as per the documentation. However, it seems to have been removed, and after cloning the live site to staging, the sites got connected to the staging URLs again.

I’ve now disconnected the staging sites, reconnected the live ones, and re-added the staging environment constant in the wp-config file. The correct URLs are now showing in WordPress.com, but the sites are not appearing as connected.
[screenshot: https://www.awesomescreenshot.com/image/57120015?key=fd6de2d87aa6e70def5d467e8ef6ad3a]

Could you please check if the setup looks correct? Also, when I click on Jetpack Cloud from WordPress.com, it opens the screen shown below, but nothing happens when clicking on any site there:
[screenshot: https://www.awesomescreenshot.com/image/57120034?key=f0a5d9f31b2984aced82001bd075fae4]

Thank You!

Hi Killian ,

Thanks for the detailed explanation. It cleared most of my doubts.

Are you currently using the post type “pages” to display your products?
Yes, we are using WordPress pages to list the products. These pages redirect to the cart or, for untimely books, to /book/<book-name>, which serves as the product details page. This is a custom-designed page and not the standard WooCommerce product page.

Regarding Matomo, the e-commerce feature must be enabled. Have you configured it accordingly?
Yes, the setup appears correct. You can verify this screenshot: https://tinyurl.com/23w33wmo

What makes you say that the e-commerce tracking is not working?
As you mentioned, it is likely working partially. Some data is visible here: https://tinyurl.com/25y3osfb, whereas other data is missing: https://tinyurl.com/259of7o3

Could you guide us on how we can enable full e-commerce data tracking for this setup, given the custom product pages?

Thank You!!

Hi,

I’m using the Connect Matomo plugin ([https://ww.wp.xz.cn/plugins/wp-piwik/]) for multisite tracking, along with Tracktastic for WooCommerce tracking. However, it seems that the WooCommerce data tracking isn’t working correctly. Could you please help check if I’m missing any configuration steps or if additional setup is required?

Thank you.

Hi Team,

I just noticed that all my sites are now showing as connected to the staging environments instead of the live sites. Could you please check why this happened? And please correct the urls.

I suspect it might be due to cloning the live site to staging. If that’s the case, could you advise how I can avoid this issue in the future?

Here is a screenshot for reference: https://tinyurl.com/27kk46cz

The live site links are:
https://cosmos.coop/
https://metapsychosis.com/
https://untimelybooks.com/

Thanks!

• This reply was modified 7 months, 4 weeks ago by Manoj Jamble.

Thank you for the support, issue is resolved after whitelisting the IP’s.