fooey

To get this to stop I excluded /events/, /event/, events-cal/ from caching in WP Rocket.

thanks for following up

We checked with WP Rocket and there seems to be pages like this https://www.sitename.com/events-cal/month/2071-05/ being generated for some unknown reason. Also, they said they checked our sitemaps, and the /events-cal/ URLs are not present there, so it seems page requests/views are going to these URLs for some reason (hard to know for sure – could be spam requests when the calendar plugin you’re using is detected or it could be something else).

They are fairly certain that WP Rocket would not be making requests to these URLs for no reason (as it really wouldn’t even know they exist unless they’re in the sitemap or are otherwise visited/viewed and consequently cached).

This is on more than one site we manage and want to bring that to your attention. For this specific site we are on PHP 8.1.16, WP 6.1.1, Events Calendar 6.0.11, WP Rocket 3.12.6.1, and Divi 4.20.2

Thanks!

Any update here? I have excluded events in WP Rocket as suggested through the caching guide and we are still experiencing this issue.

thanks,

ok, is this new? I don’t remember ever having to do this before and we had not had any issues with it until recently. We manage a lot of sites.

Thanks!

@haseeb0001

Just to let you know we have not experienced any fails since the last beta 2.4.2-beta.2 was installed. thanks for your persistence in correcting the issue.

What is the difference between this Version 2.4.2-beta.2 and the update that is available now to Version 2.4.3? Are the changes from the beta included in 2.4.3?

thanks,

@haseeb0001 spoke too soon. Still same issue. : (

@haseeb0001 so far so good. thanks!

@stevoli I apologize, we are using Mailgun api

@stevoli no just Post SMTP

Just saw that there was an update pushed 5 hours ago, trying that.

awesome, thanks so much!

great, thanks for the info. Is this going to updated in newer versions?

Yes, that worked! What may I ask was the issue? We have some sites that it works fine on and others that the close button will not work so it would be good to know moving forward.

Thanks,

both 587 and 25 resulted in Incorrect authentication data. I have already tried those combinations.

What info can I send or will this just not work with Siteground servers?