The 6.x-2.x branch does not currently update the next_run time when a schedule configuration changes. I've attached a patch to recalculate the next_run time when a schedule is saved. This way when I change the interval form monthly to weekly I don't have to wait 4 weeks for it to take effect :)

CommentFileSizeAuthor
recalculate-next-run.patch1.04 KBInterJinn
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

joachim’s picture

joachim CreditAttribution: joachim commented

Thanks for the patch!

This issue has already been filed at #1540164: handle changes to scheduler start date in admin UI, and there's a patch there too that's marked as needing work.

Any chance you could take a look and compare them?

InterJinn’s picture

InterJinn CreditAttribution: InterJinn commented

That ticket is filed under the 7.x-1.x-dev branch for which I presume the patch is intended. This ticket addresses 6.x. Although i noticed your comment on that patch... and I intentionally did not check whether the frequency or start time fields had changed. I would rather it is recalculated everytime the form is saved thus correcting any issues that may have been introduced elsewhere (such as the current release version) without needing to first change data and then change it back.

deggertsen’s picture

deggertsen CreditAttribution: deggertsen commented
Issue summary: View changes
Related issues: +#1540164: handle changes to scheduler start date in admin UI

Noting that this is related to #1540164: handle changes to scheduler start date in admin UI. Maybe should even be marked as a duplicate, though I recognize this is directed at D6 where the other is directed at D7. The decided solution should probably be applied to both branches though.