Thanks Herman, the staging website has been taken down. So it is normal that you don’t see it. I’ll open a ticket in the portal. I’ll mark this as solved for now since we have a workaround.
Hi Herman, since we have found the problem and a work around we have taken down the staging site. You can see the site at https://sutton.ca/en/.
The problem is if we use time content with the time zone set at a region it causes a conflict with the Event Calendar that will show the wrong time or date. So here is a normal calender:
Now here the same calendar with a time content module active :
See how the time have changed in the Event Calendar list ?
Here are the settings of the Timed content:
Hope this helps you understand the problem.
To solve it we used the UTC instead of the region or we just removed the time content module from the page if this was possible.
If you are still blocked, it is because you are in a country where this website is not available.
This reply was modified 2 years, 3 months ago by twohumans.
This reply was modified 2 years, 3 months ago by twohumans.
In our case this does not apply as we do not use iTheme for backups and have enough free space.
One of the theories we have is that some ModSecurity rules might have caused this since we had errors at about the same time as the incident. We deactivated the rules and are waiting to see if this solves the problem. I do not have a list of the rules that were changed.
We also added resources to the server because we saw a peak in memory usage (but no fault) just before the incident.
It was at the default value of 100, I lowered it in one more critical site. I would be surprised that it is a time-out issue, but nothing surprises me anymore (lol) so maybe. I did see a surge in memory usage and i/o just before the incident – but no fault. I’ll keep an eye on all that, and I’ve raised the time-out with the engineers.
Thank you, this is interesting.
So I understand that something must have changed lately that makes these rewrite more prone to corruption. I don’t remember in the last years having this issue, and I just got a few in a week on one of the two files, thus breaking the sites.
Good call the combination is more complex than I first thought.
It is when iThemes Security plus The Events Calendar and Event Tickets and Event Tickets Plus that we have the problem. We deactivated everything else and as soon as Tickets Plus (that needs Event Tickets and The Events Calendar to work) is activated the problem is there and solid.
I don’t see any error in the console, just a generic warning about the “zoom” property.
Tx
