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.Hi
On a fresh install of Elysia Cron, I go to settings and set default schedule rule to 'Every 6 hours'. Then I save and the list of single jobs shows Default (Every 6 hours). Great.
Now if I try to save configuration again, I get 'Invalid rule: Every 6 hours' repeated for every rule and settings cannot be saved...?
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | elysia-cron-invalid-rule-error-1570808-8.patch | 819 bytes | andrey.troeglazov |
| #3 | predefined varable.png | 505.24 KB | sanoopuio |
Comments
Comment #1
gotheric CreditAttribution: gotheric commentedA real strange error. Try to reset settings to factory values or to unistall (completely) the module and reinstall it.
Comment #2
JimV CreditAttribution: JimV commentedI get the same error if enter anything into 'Default schedule rule'. Tried complete uninstall/reinstall. Workaround is to never touch that field. 'Every hour' seems to be the default rule even though the field is blank.
Comment #3
sanoopuio CreditAttribution: sanoopuio commentedEven i am getting the same error and not able to reset that rule.
Please see the attached image
Comment #4
sanoopuio CreditAttribution: sanoopuio commentedfixed it through database alteration
Comment #5
MyriamB CreditAttribution: MyriamB commentedSame issue. disabling and uninstall the module, then re-enabling it is the only way to change configs.
Comment #6
kala4ekNeed to recheck it.
Comment #7
andrey.troeglazov CreditAttribution: andrey.troeglazov at DrupalJedi commentedComment #8
andrey.troeglazov CreditAttribution: andrey.troeglazov at DrupalJedi commentedHello, the problem was that schedule rules accept only cron-tab format, there is regexp for checking it in elysia_cron_settings_form_validate.
But for default schedule rule there is no such validation that's why the format like "every 6 hours" can be accepted and further we get an error.
I have attached a patch to avoid such problem.
Kind regards.
Comment #9
andrey.troeglazov CreditAttribution: andrey.troeglazov at DrupalJedi commentedComment #11
kala4ekThanks, committed to latest dev.