Posted by djudd on October 2, 2009 at 2:44pm
Jump to:
| Project: | Simplenews Scheduler |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I am using Supercron to allow me to determine which cron items I want to run in a specific order and to allow me to multithread certain items.
This morning my newsletter was sent out with the exact same information as yesterday, and I'm wondering if it's my cron order.
Simplenews was in the list before Simplenews_Scheduler. It seems to me that may send the newsletter before the new edition is created, resulting in yesterday's data going out again.
Am I on the right track here?
Comments
#1
I think you are right, the module needs to update the scheduling information and create the new editions before Simplenews runs with cron. Did you try to put the Scheduler before Simplenews?
#2
Yes, I did, and it helped.
#3
I mentioned your observation on the project page, thanks!
I change this to fixed.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.