Elysia Cron extends Drupal standard cron, allowing a fine grain control over each task and several ways to add custom cron jobs to your site.
Set the timings and frequencies of each cron task (you can run some jobs every day at a specified hour, other only monthly and so on...). For each task you can simply choose between some frequently used options ("once a day", "once a month" ...), or use a powerful "linux crontab"-like syntax to set the accurate timings. You can even define your frequently used options to speed up site configuration.
Parallel execution of cron task: you can group jobs in channels and execute then simultaneously: so a task that takes a lot of time to execute won't block other tasks that need to be executed every 5 minutes...
You can disable all tasks, an entire channel or a single task.
Change the priority/order of task execution.
Manual force the execution of a cron tasks.
Detailed overview of cron status with time statistics for single tasks and channels.
powerful API for module developers: you can define extra cron tasks for your modules, each one with own default timings (site administrators can override them by configuration, other modules via hook_alter).
Administrators can define custom jobs (call to functions with parameters), via the "script" option.
Several optimization for frequent cron calls and error handling.
Protection from external cron calling by cron_key or allowed host list.
Elysia has no dependencies with contributed modules, and doesn't need to patch the core: it can be used in minimal Drupal installation with only core modules.
3rd party integration:
Ping feature, for external tracking services like host-tracker to tell whether cron is functioning properly on your site.
Drush support: you can call "drush elysia-cron run" to manually run extended cron.
CTools support for exports/backup of task settings.
This module provides a block allowing users to spread the word about your website. Think of it as Forward module but as simple as it could be! The goal was to a have a simplier user experience than Forward. You can also check Tell a friend.
Since 6.x-1.4 mollom integration must be re-configured at the mollom level.
What it does?
User on your website gives a number of email adresses and his own. When user submit, each adresses (if valid) that was filled receive an email (that you can configure) from his friend advicing he/she to check the web page the sender was!
Additionnaly, a watchdog entrie is added logging who sent and who received.
Version 6.x-1.0 brings CAPTCHA & Mollom integration.
Differences with Tellafriend and Forward
User doesn't need to fill a message (action for spreading is faster)
Provides a block, which mean your not limited to node pages
Sent email contains the user current url, (same as forward but only for nodes a guess?, Tellafriend doesn't)
Submission of the form is proceed through Ajax when possible. If no JavaScript is present, then it will degrade gracefully.