Sami Falah

@shanti123 Hi, I’m not seeing that error on your site at the moment. It’s possible the error displayed after installing 13.1.1 due to caching on the site. For your site, since there appears to be a Jetpack connection issue, I’d recommend deleting the Jetpack plugin, then reinstalling the Jetpack plugin and reconnecting it. Let us know if you continue to see errors after that ??

Thanks for the report! We identified the issue and have shipped a fix in Jetpack version 13.1.1 which is available now.

Thanks for the report! We identified the issue and have shipped a fix in Jetpack version 13.1.1 which is available now.

We identified the issue and have shipped a fix in Jetpack version 13.1.1 which is available now.

Thanks for the reports! We’re actively taking a look at this and will provide more information shortly.

Thanks for the reports everyone. Jetpack version 12.2.1 has been released which includes a fix for this issue: https://www.ads-software.com/plugins/jetpack/

Thanks for the additional information.

In the screenshot, I see Jetpack version 11.8.4 referenced, so it doesn’t appear as though the errors are the result of the recent Jetpack 11.9 version update.

Additionally, I’ve checked all example pages in various web browsers and have not been able to reproduce a Jetpack related error. This is more developer oriented, but one can generally check a web browser’s “console” for any JavaScript errors, such as in Chrome: https://developer.chrome.com/docs/devtools/open/

This Ahrefs support article seems relevant: https://help.ahrefs.com/en/articles/5419017-why-am-i-seeing-a-409-conflict-error-in-my-ahrefs-site-audit

It may be possible that the request Ahrefs makes to that particular Jetpack file is being blocked by your hosting provider or some other piece of your website configuration; not necessarily that something is “broken” on the site. From what I see Jetpack is functioning as expected on the site, and pages load without error.

Hope that information helps!

Hi @travelcompositions

I’m not familiar with the “Ahrefs” service. Does it give you particular page URLs where the JavaScript error has occurred? If it does could you please share one.

I did come across one page for example using a Jetpack Form at the bottom: https://travelcompositions.com/aloha-box/

But I’m not seeing any instances of the mentioned JavaScript error on that page or others as I browse around.

Hello @wafwaf ??

As mentioned in the Jetpack 11.9 release post, we’d love to hear any feedback you have on the updated Stats dashboard via this survey!

If you prefer to continue using the traditional stats dashboard for the time being, there is a toggle in Jetpack > Settings > Traffic > Jetpack Stats (section) > "Enable a new Jetpack Stats experience"

Thanks for clarifying. I’ll share your feedback, though I’m not aware of any plans to revert to the previous interface for inviting users in that fashion.

One thing you might consider is manually sending invite emails out from your email address. You could share a link to a page on your website with the Subscribe Block added to it:

https://jetpack.com/support/jetpack-blocks/subscription-form-block/

That way people could opt-in to receiving notifications of new posts.

Hi there ??

The Users page on WordPress.com has had a recent update. For Email Followers, there should now be a “Email Subscribers” tab on the Users page which you can use for the same purpose.

1 issue I came across that -scaled images block the plugin from functioning

When looking at a specific image, currently wp_get_attachment_metadata is called, which contains an array of sizes which would have been generated for an image. Those are assumed to reside in the same directory as the parent image which could be one cause for failure.

Any more info on an image you tried this with and saw a failure for?

Thanks for the report! I’ve created an issue here to track:
https://github.com/samiff/wp-strip-image-metadata/issues/2

Do you have an example image you could share where the image orientation isn’t being preserved as expected?

Thanks for the details, I’ve created an issue to track the request: https://github.com/samiff/wp-strip-image-metadata/issues/1

I’d like to kindly ask you to add the ability to remove “description” of uploaded images in real time too. Some plugins automatically add unnecessary data

Hi there,

Do you have any examples of extra data being added by other plugins I can test on my end? I’m not sure if we’re talking about standard metadata fields here, or something else.