Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I've just checked the project page looking for information about Simplenews. In the Known bugs section, it's mentioned that using Poormanscron is not recommended. However, the issue referenced #361071: Use locking to eliminate duplicate emails from concurrent simplenews cron runs. seems to be fixed already.
Would you please clarify the current status of Poormanscron support on the project page?
Comments
Comment #1
Simon Georges CreditAttribution: Simon Georges commentedMiro, do you think we're good with Poormanscron with the 6.x-2.x version?
Comment #3
miro_dietikerI would expect that the current technical solution is now pretty fine. This means there should be no mail duplicates.
However i still cannot recommend to send newsletters using poormanscron.
Note that the interval is way too low and that sending is unreliable regarding the exact moment when the mails are created.
The time limit is currently being monitored and the amount of newsletters sent readjusted.
For the memory limit this is not yet true and missing. We should check growth of memory used towards the maximum memory limit.
We should always remain recommending real cron. We should even push usage of elysia cron and possibly add more information about this in the readme.