Home ›
E-mails being sent or nodes being saved by batch api breaking on a regular schedule just during cron runs E-mails being sent or nodes being saved by batch api breaking on a regular schedule just during cron runs
Submitted by Benjamin Melançon on June 4, 2009 - 12:45pm
Searched words:
command line cron
cron messing up email send
Batch API regularly has strange things happening exactly when cron.php called via script
open atrium "http://default" email site url
openatrium default mail
drush correct domain name URL default
If you are having weird problems in Batch API processes, such as the base URL for notification e-mails being replaced with something less-than-useful like /var/www/drupal, the culprit may be (somehow) cron.php being called by a command line script (rather than curl or something going to cron.php over the internet).
Calling Drush cron can also fail. Perhaps adding this optional flag (l or uri, they are the same) would help, though its purpose is just to pick the right site from a multisite: -l http://example.com, --uri=http://example.com
Resolution
Added the base url $base_url in settings.php, hope it will work.
More like this
- Batch API process silently fails if function in file not in default Drupal bootstrap isn't explicitly included
- Site name with site e-mail (in return address of e-mails sent from the site)
- Fix organic groups e-mails to subscribers to come from actual poster (commenter not original node author)
- Set the return path for e-mail sent by a web server
- I've run out of e-mail clients to switch to
Comments
Post new comment