Igor Zinovyev (a11n)

Hello @nmschaller !

Thank you for reporting the problem! Could you please tell us more about what you are doing, and where you are expecting to see a different result?

We have visited your site and tried subscribing to different categories, it looks like it’s working fine now. We can see that the page title is correctly displayed as “KE Blog (Fran?ais)”, as well as the category in the newsletter subscription dialog.

As for the page URL – WordPress doesn’t allow non-ASCII symbols in page slugs, so it would have to be “/category/blog-francais/”.

If I have missed the problem, please let me know, I’m happy to take another look and show it to the developers again.

Thanks!

Hi @darrenseuk !

I have gone back to WP Engine and worked on the web rules and tested it with my own IP. Your IP’s should now be able to connect and only your IP’s

The connection test looks all green now! I can’t access XMLRPC on your site from my working computer, but I’m assuming that WP Engine have whitelisted all Jetpack’s IPs, and that’s what matters.

You shouldn’t have to reconnect Jetpack anymore, and your posts should go out to social media on time.

Please let us know if you notice any other problems!

Hi!

I’m sorry to hear you’re having problems adding subscribers to your client’s site! Can you give me any more details on what is happening instead? Do you or your client see any error messages?

As for Jetpack Stats – I can see that someone has already been in contact with our Happiness Engineers recently about the site, and they removed the restriction. To use Jetpack Stats, please follow the flow on this page to certify that your site is non-commercial:
?
https://wordpress.com/stats/purchase/
?
1. Check the boxes that apply to your site, which make it non-commercial.
2. You will be given the opportunity to make a contribution toward the service if you would like. Any contribution is greatly appreciated!

Hello Claudio!

I have confirmed that your website is for non-commercial use only and, therefore, qualifies for our Free Stats plan. I have adjusted this in our records.

To use Jetpack Stats for non-commercial sites, please follow the flow on this page to certify that your site is non-commercial: https://wordpress.com/stats/purchase/

1. Check the boxes that apply to your site, which make it non-commercial
2. You will be given the opportunity to make a contribution toward the service if you would like. Any contribution is greatly appreciated!

Let us know if you have any trouble!

Hi!

We do have a filter that allows changing the slideshow captions for images, if I understood the question correctly.

It can receive up to two parameters, the first one is the proposed caption content based on the post excerpt, and the second one is the attachment ID in case you need it.

Hopefully that helps!

Hi!

The deprecation notice you are seeing is caused by a minor issue in the code that can potentially become a problem in the future. Most plugins have these issues with code, but you shouldn’t be seeing that message from either of them because this message is intended to be shown to developers.

It’s possible that some part of the code is enabling WordPress debug mode, and this is why you’re getting this message on the screen. Here are some examples of how the debug mode can be enabled.

It’s also possible that the server that hosts your site is configured to show these notices by default, but if you haven’t made any changes to it’s configuration, it’s unlikely to be the cause.

Thank you!

We’ll let the user know to update your plugin as soon as the new version appears.

I’m assuming that you were able to reconnect your site. If so, that’s good news, it means that deleting and reinstalling the plugin has successfully overwritten your old options related to the connection.

If you are still having problems with Jetpack, please let us know!

It would be extremely helpful if you do, thank you!

So it looks like you have been able to fix your problem. If so, we’re glad it’s working for you again!

If not, please let us know how we can help!

Can you please explain what you mean by “domain is registered with Jetpack”?

Jetpack usually works on domains that are owned by users themselves and are not managed by WordPress.com. To connect your Jetpack installation we just need you to have a working WordPress.com account, which you can restore access to, or just create a new one.

When you deactivate, delete, and reinstall Jetpack, you should be able to use any WordPress.com account that you have.

Hello!

Thanks for reporting this!

You’re right, spam comments should get stored in the folder for 15 days before they are deleted. But spam stats show not just comments, but other spam related activity like pingback spam and contact form entry spam.

So in this case it means that there were no comments recorded on the site. Can you reproduce the problem? Also, if you can send us more details, it would be very helpful.

Thank you!

Hello, thank you for reporting your problem!

To work around this problem you need to log into your WordPress site where you havke Jetpack installed and:

• disconnect Jetpack from the dashboard if it appears to be connected
• deactivate Jetpack
• delete Jetpack from the site entirely
• reinstall Jetpack
• activate it and try to connect again but this time using a WordPress.com account that you have control over.

Please let us know if that helps.

Hello!

Thank you for reporting your problem, but it’s impossible to say what’s wrong without looking at the site. Are we talking about https://cleancuts.biz ? It looks like this site has all the posts in order in your social media pages.

Please let us know what site we can help with.

Hello!

Do you have any other information about this error? A stack trace would have been very helpful. You can try to get it from your server’s error logs.

It looks like you have some other plugin that is trying to define a class with this name. Can you tell us the URL of the site you need help with?

We have introduced BeaverBuilderCompat in 5.8, so if you temporarily install Jetpack 5.7.1, you should have it working again to be able to make changes to your other plugins.