Nicolas

It’s been a while since I wrote the script so please do some testing, but I do not believe that your reading of the script is correct. If you had a directory called “sites/dog”, then the script should call http://dog/cron.php. It is up to you to set up your Apache configuration to understand what dog is. Am I misunderstanging your meaning here?

If you use the “default” folder, then the script will use whatever you put in the $masterDomainName variable to call the cron script. So let’s say that you had “sites/default/dog”, then the script would call http://$masterDomainName/dog/cron.php. So it can do subdomains that way.

But yes, if you want to host sub domains as sub.domainname.com, then that subdomain needs to be labled as such. The Drupal documentation had this naming convention as a “best practice”, so that’s what I followed.

This script was built to do dev work locally. It was assumed that Drupal used relative paths, and that this will all take care of itself when moving the site. I’m unaware of any need to edit the database when moving, but maybe that just because of how I’m using it.

If the “patch” you’re talking about is a module, please post back and let me know what it is. I’d love to take a look at it.

I hope this helps.
M