Closed jaswrks closed 7 years ago
This feature will be helpful. I currently have 1,292 items stuck on the Mail Queue (since 2 weeks ago).
Work in this issue may also help to resolve and/or diagnose problems reported in https://github.com/websharks/comment-mail/issues/317
Next Release Changelog:
Noting that the above details (i.e., 30
seconds and 100
queued emails) as seen in the screenshot, can be changed in your Comment Mail options. If you change them, the wording in that notice will change accordingly, and so will the time allowed and the number of entries you're able to process.
See: Config Options → Queue Processor Adjustments
@jaswsinc @raamdev
Settings seem to be working fine, but how can I get Notifications to queue so that they can be manually processed? The automatic process is doing its job very well 😆
Default:
Changing settings in Queue Processor Panel
With Max allowable values:
In that same panel change Real-Time Queue Processing from 5
to 0
(disable).
Comment Mail v161213 has been released and includes changes from this GitHub Issue. See the v161213 announcement for further details.
This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#282).
It would be very helpful if there was a button in the Dashboard that would allow a site owner to force a queue runner to process any lingering emails still in the queue. This might help others troubleshoot issues related to what could actually be an underlying problem with the CRON job.
Referencing: https://github.com/websharks/comment-mail-pro/blob/edea333166cc96cb9a7b6b8d6f8e09a346263fc0/src/includes/classes/Plugin.php#L2729
↑ Need to a way to trigger this method from the Dashboard through a non-blocking HTTP connection. Or, we simply need a way to trigger the CRON job that already exists from the Dashboard using something other than WP Crontrol, because that plugin doesn't seem to work in all cases for some reason.