Hello.

First of all, thanks for the great work on this module. We are currently running some of our sites in a Drupal multisite setup (i.e. off the same Drupal installation but with different vhosts). From looking at the documentation and code, it doesn't appear like this module would work in such an environment...

; path to Drupal root directory
path = "/path/to/drupal/root"

...since this doesn't allow Drupal to know which site to run cron for beyond the default domain. Is this correct? Do you see any work-arounds?

Thanks a lot!

-Daniel Chvatik
Adulmec

Comments

cpliakas’s picture

cpliakas commented
Category: support » bug

Hi Daniel.

You are absolutely correct, and it was a lack of foresight on my part. Thanks for bringing this to my attention. There is a workaround, though. You can use Drush to execute Cron MT, and that will allow you to use the module in a multi-site environment. In terms of the future of this module, my goal is to work with the SuperCron maintainers to merge this project into theirs as to avoid duplicate efforts. I will evaluate to see how time consuming it would be to add a fix to the bundled configuration file and CLI cron script, otherwise I will assume that SuperCron will take care of this.

Thanks again,
Chris

kerberos’s picture

kerberos commented

Yes, Drush seems to be the way around this. Thanks!

-Daniel

cpliakas’s picture

cpliakas commented
Status: Active » Closed (won't fix)

Due to end of life announcement.