Years ago, I was a prepress operator. There, only the printing press could spoil what I did. Ever since I've been in the online world, creating websites, I've often thought of giving up on this whole thing, because it depends on so many things whether something is good or not, and what's good also breaks down because one of the components (hosting provider, php, mysql, server component changes, but even the ISP) can mess something up. This is so fucking shit. And then I didn't even talk about modules and browsers.
The Drupal 7.98 update fixed the problem, no need for the Imunify360 exception setting
The hosting provider said there were no changes to their system.
The interesting coincidence is that before that there was an error phenomenon that I had never experienced before: the size of the database suddenly became 8 GB, cPanel showed this, but phpMyAdmin showed the normal size of 40 Mb. Because of this, the storage space was also marked as full, but the registration, content uploading and backup from Drupal still worked. The service provider said that they don't know the reason, because they can't look that deep into MySQL and cPanel either. They said it was caused by stuck data. What is stuck data? And 8 GB???
It really works, but we should know what caused this error and what we changed with this setting, whether it will cause problems later.
Addendum: when the mail is processed by the SMTP Authentication Support module, the mail is entered into the Mail Logger module, but before it is sent, which is incorrect, because it should only be entered when it has actually been sent.
Workaround:
Another feature of Rules, which also includes offset, counts well. This is interesting, because I think the module takes this action from the same place, but according to them, it doesn't?
So this solves the problem, avoiding the date offset error:
Action: Calculate a value
I do not understand. I'm not at home on this forum.
Why was my post copied and rewritten as version 7.x-2.x-dev? That the fix is in the dev version and should I test it?
I'm shocked that this bug has been in the Rules module since 2012!
Date offset is incorrect 🐛 Date offset is incorrect Closed: duplicate
I undertake the testing.
I can't fix the module because I can't program in PHP and I don't know how to create a Drupal module, yet.
I don't understand that it didn't bother others, since there can be many cases when it is important.
For example, if I want to hide a content 30 days after a given date, then it doesn't matter how many +/- days have passed due to the error, if that content is related to a subscription.