| Attribute | Average |
|---|---|
| Features | 3 / 5 |
| Reliability | 2 / 5 |
| Ease Of Use | 2 / 5 |
| Documentation | 1 / 5 |
| Vote Count | 1 |
SuperCron is a complete replacement for Drupal's built-in Cron functionality. It allows you to: See the list of all Cron hooks found in the enabled modules Change the order in which cron hooks are called Disable certain hooks Run the tasks you choose in parallel, so that cron tasks will be executed... [More...]
| Maintainer: | 63reasons |
| Links: | |
| Categories: | Developer, Performance and Scalability, Utility |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.3 | 2009-Jun-15 | Download | Recommended |
| 6.x-2.x-dev | 2011-Feb-25 | Download | Development |
Options: Add a review
1.x branch has a common post-install problem that makes the user interface inaccessible without manual patching. The 2.x branch seems to install without that issue, but for at least some users has a code defect that has been cropping up for over a year, through multiple .dev updates. For both 2.x and 1.x branches, permissions were inaccessible for me.
1.x branch is 2 years old. 2.x.dev branch is newer (though does not seem to be stable).
User interface is opaque -- can't make heads or tails of it -- and such documentation as exists is not helpful.
Also, installing changes the application workflow (manually applying cron no longer redirects to the status page, but rather back to the page from which it was invoked -- that would be a desirable outcome, but it's persistent after the module's uninstalled, which leads me to a) doubt the uninstaller, and b) wonder if that won't have consequences for other module and core function down the line.
Documentation seems to imply that the module introduces tracing for each cron hook, but that does not seem to be the case in practice (if it is, I can't tell how to make it happen through the UI).
Verdict: it's a promising idea, but unless you've got the time to invest in manually fixing its defects, don't bother. (If you do, it may be invaluable to you -- e.g. if you have a large complex site -- but definitely also check out Elysia Cron, which carries a similar configuration load but in the form of manually-edited cron scripts, and appears to be more stable.
