I found this when I ported drupal.sh to D5 but it also applies to D6. I didn't have and credentials set in my default folder and when I tried to run drupal.sh I got and error saying that it couldn't load sites/defaults/settings.php even though I put the URI as http://example.com and had sites/example.com/settings.php setup.

debbugging the issue I found it was because of $_SERVER['SCRIPT_NAME'] = './scripts/drupal.sh'; which meant conf_path() looked for sites/example.com./settings.php instead.

I'm surprised no one else has seen this issue before.

I'm marking this critical because it breaks normal convention and prevents cron from running for different sites using the same install.

CommentFileSizeAuthor
drupal.sh_.patch442 bytesjosh waihi

Comments

sun’s picture

sun’s picture

Can you elaborate a bit more on your (multi-site?) setup, and also, how exactly you invoked drupal.sh?

josh waihi’s picture

wow, this issue is quite old now. But normally i invoke drupal.sh to like so:

/path/to/drupal/root/scripts/drupal.sh --root /path/to/drupal/root URI

90% of the time I don't have a problem, it only occurs with multi-site when trying to load a settings.php from anywhere other than the default location.

ben_scott’s picture

Hi -

I'm running into a very similar problem on 6.15 - if $_SERVER['SCRIPT_NAME'] is not defined in drupal.sh, $base_path will be set to /path/to/drupal, which breaks some parts of the site. Two other bugs that I've run into:

1. Gmap markers disappear (See http://drupal.org/node/478294#comment-2340414)

2. The available updates notification email has the wrong path (The "See the available updates page for more information" goes to /path/to/drupal/scripts/admin/reports/updates rather than domain/admin/reports/updates).

The patch above fixes the issue for me.

Cheers,

Ben

Status: Needs review » Needs work

The last submitted patch, drupal.sh_.patch, failed testing.

dpearcefl’s picture

Priority: Critical » Major
Status: Needs work » Postponed (maintainer needs more info)

Is there any interest in this issue? Is this a Drush or Drupal issue?

sun’s picture

Priority: Major » Normal
Status: Postponed (maintainer needs more info) » Needs work
dpearcefl’s picture

Sun, please resubmit your patch against the latest 6.x-dev codebase and give is a proper filename.

http://drupal.org/node/1054616
[description]-[issue-number]-[comment-number].patch

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.