Drush can be used as a full cron call replacement.
However it's not only calling "#drush cron" and you're done. Since we're building mails and leaving the context of the current drupal installation, we need full context coverage and drupal should know perfectly what's happening.
It seems to be needed that drush is called with --uri=http://www.example.com parameter to make the drupal base URI work cleanly.
Lack of this option in case of a drush cron leads to broken URLs with high certainity. Same also applies to elysia_cron run via drush.
The documentation should be extended to describe the requirements.
References:
#1158144: drush status shows Site URI of 'http://default' when only one site directory exists
In addition our recent module Simplenews Linkchecker helps you to make sure there's no broken link in your mails.
http://drupal.org/project/simplenews_linkchecker
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | add_drush_and_elysia_cron_info_to_readme.patch | 1.39 KB | berdir |
Comments
Comment #1
berdirSomething like this?
Comment #2
miro_dietikerGood start.
However, when using drush, the $base_url won't help. Since version 4.x drush no more considers the base_url from settings as current hostname. You ALWAYS need to state the --uri argument.