Hi, I'm the developer behind a Drupal 6.4 distribution / install profile called ProsePoint.

I have received the following bug report from at least two of my users:

At the screen 'Select an installation profile', they select 'ProsePoint' instead of 'Drupal'. Upon clicking 'Save and continue', and waiting a few seconds, the browser then throws up a white screen with a message of the form "Call to undefined function db_result() in ... path.inc on line 55".

They then report that if they chose to install Drupal instead of ProsePoint, Drupal installs correctly.

Unfortunately, I myself have not been able to reproduce this problem. It seems related to less commonly used X/LAMP stacks or semi-restricted shared hosting accounts.

I have tried trapping any calls to drupal_lookup_path() (the triggering function) during this installation step, but I have not been able to get any backtraces. It would seem that on my computer, at least, nothing calls drupal_lookup_path() during this step of installation.

Yet evidently something must be calling drupal_lookup_path() on the servers of my users.

Looking at Drupal's default.profile, I realise that Drupal doesn't enable path.module at install time.

Is it possible that there's some funny bug/interaction between the Drupal installer and path.module if path.module is listed in the ...profile_modules() function?

The impact of this bug is pretty minor, but some of the core maintainers might like to enable path.module in default.profile and just run through it a few times on some less commonly LAMP stacks?

My upstream bug report is here: https://bugs.launchpad.net/prosepoint/+bug/261587

You can get the relevant version of ProsePoint (0.01) at http://www.prosepoint.org/download, though I think modifying default.profile to include path.module might be enough as a test.

Thank you.

Comments

bengtan’s picture

bengtan commented
Status: Active » Fixed

Sorry, found the problem. It's not in Drupal core, it's in another contrib module. I'm closing this issue and filing a new one against the relevant contrib module. Thank you.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

sirkitree’s picture

sirkitree commented

What was the other contrib module if you don't mind me asking?

bengtan’s picture

bengtan commented

The module was Date, but it was fixed up a long time ago. See http://drupal.org/node/301385.

lelizondo’s picture

lelizondo commented
Version: 6.4 » 6.16

SPARQL is also causing this exact same problem in 6.16. I don't want to open this issue, I'm just leaving this as a reference for other users.

Anonymous’s picture

Anonymous (not verified) commented

url_alter also causes this.