|
radiusinvestigations
|
November 19, 2018 at 10:20 am
I was working with my hosting provider on a completely unrelated matter this morning, which led to temporarily disabling the firewall. This caused a bunch of old registration notification emails to be re-sent to the admin and registrants’ email addresses. Needless to say, I had a very fun Monday putting out this fire.
I do recall last month, we had an issue where notification emails were not going through. After what was figured to be a redundancy issue, since the admin notifications were set to be sent and received by the same email. In the messaging portal, it showed several email notification that were marked in gray and not generated. I think those non-generated emails generated themselves and were sent out the moment the firewall was disabled. The hosting provider believes that the wp-cron pushed these through after the firewall was disabled.
Can there be a feature put in place to automatically delete or remove any messages after a certain period of time that failed or were not generated?
|
|
Tony
|
November 22, 2018 at 4:28 am
Hi there,
The hosting provider believes that the wp-cron pushed these through after the firewall was disabled.
This sounds likely to me, we do use crons for the messages system and if for whatever reason that didn’t work the messages could sit waiting.
I’m guessing, that at some point you switched the messages system to send the emails directly?
(Event Espresso -> Messages -> Settings ->
Generate and send all messages -> On same request)
Meaning the messages using cron sat waiting and and then when the firewall was disabled worked, it still seems a little strange though as WP Cron works on any request, not just specific requests, although the firewall may have prevented something else downstream.
Can there be a feature put in place to automatically delete or remove any messages after a certain period of time that failed or were not generated?
We actually already have a setting for this, same section as above you’ll have ‘Cleanup of old messages:’ which lets you specify how long we keep messages, by default the only status it ignores (which can be filtered) is the idle status which is ‘Queued for sending’.
However, that also works on WP_Cron so the catch is that if your messages weren’t working because of an issue with wp_cron/the firewall…. the function to delete the messages also won’t work.
|
