Karen Attfield

When signing up to use Jetpack’s services, we ask that everyone respects our TOS policies. In terms of video content, as the content is stored on the WordPress.com servers this information can be found here – https://wordpress.com/support/mature-content/

Uploading content that breaches those TOS policies would result in suspension when discovered.

We’d recommend only enabling the Jetpack features you want to use on your site. One of the pros of Jetpack is that in having many different features available in the one plugin, you don’t need to add multiple plugins for each preferred feature. Unless you have specific needs for various features that can only be met by another plugin.

Hi there,

Please do leave a question on the Jetpack support forum here – https://www.ads-software.com/support/plugin/jetpack/ – we’ll be happy to help with any issues you are experiencing when updating Jetpack.

We’d recommend only enabling the Jetpack features you want to use on your site.

Various features in Jetpack are actually designed to speed up your site by taking a load off your server – for example the following which are processed at Jetpack’s end:

– Site Accelerator – https://jetpack.com/support/site-accelerator/
– Stats – https://jetpack.com/support/wordpress-com-stats/
– Subscriptions – https://jetpack.com/support/subscriptions/
– Related Posts – https://jetpack.com/support/related-posts/

Similar features elsewhere traditionally make numerous requests to a site’s database.

There are also features such as Lazy Images – https://jetpack.com/support/lazy-images/ – specifically designed to speed up page load time.

That said, the more Jetpack features are enabled, the more processing your site (or in this case customers sites) would have to do, just as if you were adding separate plugins for those features. That’s why we always recommend enabling only the features needed.

In terms of speed and loading times, here’s an independent report that can shed more light on this in terms of Jetpack and it’s features: https://mattreport.com/jetpack-speed/

Hi there @krofek,

I just checked and it looks like Jetpack was reconnected on your site and has connected via the XML-RPC file. It also looks like the most recent post was successfully published to your social media accounts.

I’ll mark this forum thread as resolved for now – if you have further questions please do open a new thread and we’ll be happy to help!

Hi there,

Please note that we primarily provide support in English. For now, I’ll be replying in English, but you can respond to me in your language and I’ll enter your messages into Google Translate.

We would be happy to investigate what may have caused an issue on your site when Jetpack was active. There could be multiple reasons, however if you are happy to share your site URL and what exactly happened after installing and activating the plugin we’ll be happy to investigate what the issue could have been. Thank you!

Hi there!

Digging a bit further, it looks like there were two historic unique blog IDs associated to your staging site URL (the blog ID being what Jetpack uses to identify a site). This other blog ID had stats on it going back to September 2019. I’ve now merged those stats as well. Do those new stats match what you would expect to be seeing? Let us know if not. Thank you!

Hi @aetherscythe

I see there is a ticket from you which I see has had a response since your message here – so we’ll continue to follow up with you via the ticket. As such I’ll close out this support thread in favor of the ticket. In the meantime do you notice the error when you are also logged into WordPress.com within the same browser? If you could confirm that via the ticket we can continue digging in. Thank you!

Getting back to you regarding the last question – the selected language not being kept on saving, based on how you are describing it these options are not likely Jetpack options. This would be another case of reaching out to the author of your multilingual plugin author (if you are using a multilingual plugin) as it’s most likely these options are added by them. Feel free to send us a screenshot of what you see when choosing a language and we may be able to confirm that. Thank you!

Hi there!

Checking your blog at https://zickson.com/blog/ I was able to see the like button loading properly (though with a slight delay).

I tried it in several different browsers and noticed it loading.

You mentioned you’d tried all the suggestions on the above blog post – if you’ve tried with different browsers one other suggestion would be to disable any browser extensions you may have enabled as that could impact on the like button loading for you as well.

Also, is this happening through the WordPress.com app or in a browser window?

Do let us know what you find and that will help us troubleshoot further. Thank you!

Hi there!

We’ve heard back from our development team on one part of this question now. With regard to which pages show up within widget visibility settings, it is expected behaviour for all pages to show up. To Jetpack and to any other plugins on your site, a page is a page. It’s likely only your multilingual plugin (if you are using one) that will make the distinction between a page in English and a page in Italian or another language.

If you are using a multilingual plugin and would like that plugin to extend Jetpack’s Widget Visibility to support this kind of page type, you may want to contact the plugin author to suggest that. Jetpack’s feature includes hooks that allow third-parties to extend it to match their particular needs. Here is a link with hooks relevant to Widget Visibility:

– https://developer.jetpack.com/module/widget-visibility/

In terms of the tree order of pages not being respected, there are existing issues as Widget Visibility won’t cover ‘grandchildren’ of pages – is this what you were referring to? Here is a related issue:

– https://github.com/Automattic/jetpack/issues/2829

For your last question (in the separate thread) regarding the selected language not being kept on saving, we’ll get back to you as soon as we have more information on that. Could you confirm if your site URL where the issue is happening is https://www.visitmontaione.com/? Thank you!

The navigation has certainly changed and our support docs have now been updated, but the import option should be under the Google Search Console box now. If you’re not seeing that, would it be possible to share a link to a screenshot of what you see as soon as you’ve logged in to Bing?

This page has some good information: https://en.support.wordpress.com/make-a-screenshot/

You can then share it through a site such as https://snipboard.io/

Thank you!

Hi Markus,

Thanks for reaching out!

I understand from our separate email exchange that the main issue was not a delay (it comes up immediately) but that beacon data shows the wrong time for your timezone.

I reached out to ViewRanger who confirmed the beacon data itself is always shared in UTC+0 time format. It may be possible to add a timezone option in the map settings pages to help convert the time to match your timezone, however looking into this I realized it will take longer than the time I currently have to give to the plugin. This is something I’ll add to the list of potential future changes though.

In the meantime I’ve added an additional note to the plugin readme page to explain that the plugin is currently configured to show correct times for UK and that matching timezone.

Thanks for giving the plugin a try regardless, and I hope you are still able to make use of it ??

Hi Doug,

I do agree, it is a bit confusing! The confusion is mainly due to the difference between registered users on your website, WordPress.com user roles, and Jetpack subscribers.

I found an older thread here which helps to explain the difference between Jetpack subscribers, registered users and followers: https://www.ads-software.com/support/topic/jetpack-subscription-and-followers-vs-users-vs-subscribers/?replies=15#post-4240396

Hi Doug,

Since you reached out to Jetpack support by email I have responded to you there.