Mailpoet Cron
-
MailPoet Version 3.6.1 and BIG cron issue.
In the new MailPoet versions the support for native crons were removed:
The new version of MailPoet no longer relies on the cron system shipped with WordPress. That system was responsible for starting the sending process and ensuring that your emails are dispatched according to the set schedule. However, it had its quirks and most often than messages were late to send.
Please don’t treat every WordPress user as a silly non-technical person. What are the quirks with native WordPress cron?
There are no issues with WordPress crons, should users choose to set them up properly. In my opinion, there are many more issues with either way MailPoet cron has to run now, which include:
* “Spam” in PHP-FPM slow log (if someone chooses to enable it).
* Using “web based” cron to run a task against local PHP scripts is plain wrong.I have WordPress crons set to run every minute using real Linux cron, and there are absolutely no issues with this approach to run crons.
MailPoet developers decided for everyone that real Linux crons brings more issues than it solves, and shoot from their big developer canon by giving us no option to use it for their plugin.
Pardon me for my language, but I am sure this can piss of many people. Why this were removed and we only have slow, improper ways to run MailPoet cron?
Why the only proper option to run cron was removed from MailPoet??????
- The topic ‘Mailpoet Cron’ is closed to new replies.