| | Consolidate cron scheduling and administration | drupal.org (Site not responding. Last check: 2007-10-21) |
 | | As a nice detail the page could show the time of the last cron run and perhaps provide a warning if it was a long time ago (more than a day, for example), which would serve as a clue to users that they might need to do something to set up crontabs. |
 | | The search module bases its decision on whether to run cron on the presence of new content, so search would implement hook_cron_schedule to override this default form on the admin screen (either offering an alternative form to make a schedule or indicating that no scheduling is needed because it is handled at the module level). |
 | | While, in general, I think the reliance on cron should be elimiated, in my other post I suggest that modules should as far as possible do their own maintainance, there may be cases where cron is approriate. |
| drupal.org /node/28797 (2058 words) |