Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I noticed validation isn't catching when enabling an incorrect cron task via Drush. The example below is a recent mistake using "system" instead of the correct "system_cron" cron task id. I think this can be worked around for cleanliness.
$ drush cron-enable system
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: Call to a member function enable() on a non-object in
/drupal/sites/all/modules/contrib/ultimate_cron/ultimate_cron.drush.inc,
line 457
Fatal error: Call to a member function enable() on a non-object in /drupal/code/sites/all/modules/contrib/ultimate_cron/ultimate_cron.drush.inc on line 457
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | ultimate_cron-drush-enable-verify-2833601-1.patch | 550 bytes | Chris Charlton |
Comments
Comment #2
Chris CharltonPatch provided.
Comment #3
Chris CharltonComment #5
arnested commentedThank you for catching this and thank you for the patch.
I have applied the patch to the 7.x-2.x branch and the fix will be part of the next release.
Comment #6
Chris CharltonUgh, I just realized both 'disable' and 'unlock' need the same treatment. Shall I do that patch, and if so in a new issue or this one?
Comment #7
arnested commentedIt's OK to post it here :-)