Thanks for reaching out. The file seems to be part of some messages/notices that Jetpack displays, Do you have any notices by Jetpack on your admin page at the moment? If so, can you please take a screenshot of the notice and send it across?
Hi, I was using WordPress 4.7.5 at the time of the mixed content problem.
There were no notices in the admin page from Jetpack at that time.
However, we’ve just upgraded to WordPress 4.8 and the Jetpack Admin notice about enabling Vaultpress backups came up after the update.
We closed it and now the mixed content problem is gone.
Thanks for your reply.
To add to this however, although the mixed content issue is fixed, we are seeing the following request in our logs every single time we load a page in the admin page:
wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=&_wpnonce=cdf8d1cc12
There are no notices showing in the admin area from Jetpack or any other plugins.
Hi,
We’re still seeing this in our logs every time we load a page in WP-Admin
/wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=&_wpnonce=1dc587fb6e
To be clear, there is no notice showing at all.
Martin
Hi Martin,
That’s from Just In Time Messaging (JITM) checking the path of the page and then seeing if a message needs to be displayed or not – in most cases and yours it’s just returning an empty string. You could completely turn off any messages using the filter stated here:
https://github.com/Automattic/jetpack/blob/master/class.jetpack-jitm.php#L338
Hi Lamday,
Thanks very much for your reply.
I’ve tried disabling JITM by adding the following code to our functions.php file:
add_filter( 'jetpack_just_in_time_msgs', '__return_false', 99 );
However, the issue persists. On every single page load in WP Admin, we something like the following on our server:
/wp-json/jetpack/v4/jitm?message_path=wp%3Aedit-post%3Aadmin_notices&query=paged%253D6&_wpnonce=97ab0770dc
Each query of this type takes about a second to execute.
To be clear, this problem only started when we installed Jetpack 5.0, so I think it may be a problem with the plugin?
Many thanks,
Martin
