Jetpack’s synchronization happens when you make changes to a post or a page, or when you make changes to any of your site settings. There is also a scheduled synchronization happening once a day, and of course a global sync happening when you first connect Jetpack to WordPress.com.
You may also see communications between your site and WordPress.com whenever someone posts a comment on your site, if you use Jetpack Comments. Since the comment form is hosted on WordPress.com, this communication has to happen.
Other than that, you shouldn’t see any communication or synchronization between your site and WordPress.com when a reader visits your site. If you do, could you give me more details about it so I can look into it?
Thanks!
Sure!
The only information I have right now are traces from New Relic. We have many custom post types with archive-{post-type}.php files.
On index.php I’m seeing requests to jetpack once or twice and from the archive files as well. Going through the list of events you gave me:
– A post or page is not being changed
– Site settings aren’t changing (that I know of)
– Is happening within less than days gap on subsequent requests
– We do not allow comments or use Jetpack Comments
What is meant by site settings? Is that any update to wp_options? Are there any other parameters that you know of that could trigger any kind of connection to jetpack.wordpress.com? I’m seeing the calls being made from the ‘shutdown’ action.
On index.php I’m seeing requests to jetpack once or twice and from the archive files as well.
How do these requests look like? Could you send me a few examples via this contact form, so I can dig into this a bit more?
http://jetpack.me/contact-support/
What is meant by site settings? Is that any update to wp_options?
Yes, exactly.
I’ll see what I can do about sending those traces over.
In the mean time I’ll get everything updated and investigate any updates that may be happening to wp_options. FWIW it seems triggering the syncs on any update to wp_options seems like bad practice since any 3rd party plugin has access to changing those settings unless the syncs are only triggered by admins on admin pages that is.
Thanks again for your help on this!
FWIW it seems triggering the syncs on any update to wp_options seems like bad practice since any 3rd party plugin has access to changing those settings unless the syncs are only triggered by admins on admin pages that is.
We only monitor specific options in wp_options (Site title, description, timezone, permalinks, and a few others that are relevant to Jetpack modules), so a sync wouldn’t be triggered by changes to options specific to 3rd party plugins.
