With drupal 4.6 you can run multiple sites from one installations via the sites directory, and you can have different modules for each site by placing them in a modules directory in the site's directory.

Project however has hard coded links to the include files so this feature doesn't work.

the patch attached fixes this by using the drupal_get_path function to work out where the module is installed and uses this path to load the includes.

CommentFileSizeAuthor
project.module.sitedirectory.patch815 bytesmoggy

Comments

goofrider’s picture

goofrider commented
Title: project in sites/sitename/modules directory » more symptoms related to "project in sites/sitename/modules directory"

Thanks for the patch, it was what I was looking for, though it took me some time to find this patch on the support site. Here are the error messages I encountered when I installed the project module before I found this fix. Hope it'll help others to locate this patch via searching.

1. When click on "projects -> issues", I got following error:

warning: call_user_func_array(): First argumented is expected to be a valid callback, 'project_issue_page' was given in /srv/vhosts/sandbox/share/drupal-4.6.3/includes/menu.inc on line 354.

2. When click on "admin -> access control", I got following error:

Fatal error: Call to undefined function: project_issue_state() in /srv/vhosts/sandbox/share/drupal-4.6.3/sites/sandbox/modules/project.module on line 73

It took me a while to figure out that the problem was that I put the project module files in sites//modules.

goofrider’s picture

goofrider commented
Title: more symptoms related to "project in sites/sitename/modules directory" » project in sites/sitename/modules directory
ax’s picture

ax commented
Status: Needs review » Fixed

i committed a slighty different version to DRUPAL-4-6, including an additional fix for the broken stylesheet link. fixed in HEAD, too.

Anonymous’s picture

(not verified) commented
Anonymous’s picture

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