Alin (a11n)

Hi @daymobrew,

Thanks for your confirmation! When using Jetpack in Offline mode, some features that rely on external connections, like DNS queries, may not function as expected. The warning you’re seeing is likely due to this limitation.

Since you’re working in a local environment, these warnings can be safely ignored. They won’t affect your local development. However, if you need to test features that require a connection, you might consider setting up an online staging site for a more accurate experience.

Let me know this helps or if you have any questions!

Best,
Alin

Hi @greentp,

It’s great to hear that the workaround resolved the issue for you.

If you have any more questions or need further assistance, please let us know.

Best regards,
Alin

Hi @greentp,

Thank you for the follow-ups.

What you found is correct, and to add to that, the notice appears because some Twenty themes still call add_theme_support( 'jetpack-geo-location' );, even though Jetpack 14.3 intentionally deprecated Jetpack_Geo_Location. The deprecation was part of streamlining Jetpack’s features, and this specific module no longer has an active replacement.

You can read more about that in this public GitHub issue.

Let us know if this helps.

Hi @ylara,

Thanks for reaching out! I tested this on a similar setup using Boost 3.8.0, Filter Gallery Free 0.2.0, and Neve theme 4.0.1, but I wasn’t able to replicate the issue. This suggests that the “Defer Non-Essential JavaScript” feature may be affecting something specific to Filter Gallery Pro.

Since the plugin developers have the best insight into how their scripts load and interact with optimization tools, I recommend reaching out to them for guidance. They can confirm whether any adjustments are needed to ensure compatibility with Boost.

Let us know if you have any other questions. We’d be happy to help!

Hi @lmverberne,

I wanted to follow up and quickly clarify something:?Jetpack Social?and the?Sharing?feature are actually separate. </span>Jetpack Social is designed to automatically share your posts on social media, while the Sharing feature adds buttons for visitors to share your content.

It sounds like the Sharing feature needed to be turned off, and I’m glad that resolved things for you!

If you ever need to review or adjust Jetpack Social’s settings instead, you can find them under:

• Jetpack → Settings → Sharing (if using the Jetpack plugin)
• Jetpack → Social (if using the Jetpack Social plugin)

I hope this helps, but feel free to let us know if you need any further assistance!

Kind regards,
Alin

Hi Lucas,

That’s fantastic to hear! I’m really glad the steps worked and that the sharing buttons are now gone from your site.

If you’re finding Jetpack valuable, we’d really appreciate it if you could take a moment to leave us a review. Your feedback helps us improve and continue providing the best experience possible.

If you ever need to adjust your Jetpack settings or explore other features that might help with your site’s goals, feel free to reach out—we’re always happy to help!

Wishing you all the best with your site!

Best,
Alin

Hi Lucas,

Thank you for clarifying! I see that the Sharing feature from Jetpack is currently enabled and displaying sharing buttons at the bottom of your posts. If you no longer wish to use this, you can disable it by going to Jetpack → Settings → Sharing tab, then scrolling down to the Sharing section and toggling it off. This will completely remove the sharing buttons from your site.

I understand that you want to disconnect Jetpack. From what I can see, XML-RPC access is blocked, which prevents Jetpack from connecting. If this was done intentionally and you no longer wish to use Jetpack, you can completely remove the plugin from the Plugins page in your WP-Admin. This will remove Jetpack, its connection, and all of its features from your site.

I hope this helps, but if you have any questions, please let us know.

Best regards,
Alin

Hi @jules-colle,

Thank you for reaching out! I checked on our end, and your site https://blankenberge-brugge-so.lokaaloverlegplatform.be is already classified as non-commercial in our system.

Can you try checking your stats again and let me know if the warning still appears? If it does, could you provide a screenshot of the message you’re seeing? This will help us investigate further.

Regarding your multisite network, the non-commercial classification is applied per site, not to the entire network. This means each site needs to be reviewed individually. If you’re seeing similar issues on other sites, let me know which ones, and I’d be happy to check their status as well.

If you prefer to stay private, we can continue via email if you use this contact form.

Looking forward to your update!

Hi @lmverberne,

Just to clarify, when you say Jetpack Social is still present on every page, are you referring to social sharing buttons, links, or something else?

Also, could you let me know how you uninstalled it—did you deactivate and delete the plugin from your site’s dashboard, or was it removed another way?

If possible, sharing a link to a page where you’re seeing this would also help us investigate further.

Looking forward to your reply!

Hi @jhofer1,

If you’ve already created the “Analytics” tab as a child page, please make sure to also uncheck the “Hide” box for this tab in Jetpack CRM > CRM Settings > Client Portal under the “Client Portal Pro Page Settings” section.

This will ensure that the “Analytics” tab is visible to your clients in their portal.

Let me know if this helps.

• This reply was modified 1 month, 3 weeks ago by Alin (a11n).

Hi @broder,

It’s great to hear that you managed to get it working despite the initial warning. If you encounter any further issues or need more assistance, feel free to reach out again.

That said, I’ll mark this as resolved for now.

Best regards,
Alin

Hi @aclassifier,

Thanks for your patience! I ran some tests on a similar setup (latest WordPress, Jetpack, WP-OPtimize, UpdraftPlus). I wasn’t able to replicate the warnings you’re seeing. Given that both you and another user suspect a possible caching conflict, it’s best to wait and see what the WP-Optimize folks find in the other thread you opened.

Best regards,
Alin

Hi @brenmc1971,

I am glad we could help. If there is anything else related to the WordPress app itself, feel free to reach out again anytime.

Best regards!
Alin

Hi @abnetceo,

Thank you for reaching out! I’m happy to assist.

From your description, it seems the issue is related to your WordPress installation being in the /wp/ subdirectory. Jetpack relies on the xmlrpc.php file for communication, and the 404 error at https://www.abnet.co.jp/xmlrpc.php indicates it’s not accessible from the root directory.

To resolve this, ensure the xmlrpc.php file is present and accessible. If needed, you may need to adjust your server configuration to properly route requests.

Additinoally, verify that there are no security plugins or server settings blocking access to the?xmlrpc.php?file.

You can use the debug tool to check the status of the Jetpack connection and also troubleshooting steps:

https://jptools.wordpress.com/debug/?url=https://www.abnet.co.jp/

Let us know if you have any further questions!

Hi @kerimusta,

Thank you for your patience. I’ve spent some time investigating the issue further and was able to reproduce it on your site by simulating a slow CPU using the DevTools Performance tab in my browser (with 6x CPU slowdown and cache disabled). However, I couldn’t replicate the issue on a fresh test site using the same theme (OceanWP) and only Jetpack active.

This leads me to believe that there might be a conflict with another plugin on your site. To help isolate the cause, could you try the following:

1. Temporarily disable all other plugins except Jetpack.
2. Test if the issue still occurs with just Jetpack and your theme active.

If the issue no longer appears, the conflict is likely with one of the other plugins. You can re-enable the plugins one by one to identify which one is causing the problem.