Modules are now intended to be installed into sites/all/modules while modules is reserved for core. Modules are supposed to WORK in modules, but users are admonished to install to sites/all/modules.

Comments

jpulles’s picture

jpulles commented
Category: bug » support

See my post http://drupal.org/node/112992. It seemed that modules in sites/all/modules are not yet fully supported by drupal. I don't know if this is already patched in release 5.1.
The mapbuilder module can be installed where drupal allows it.

hyperlogos’s picture

hyperlogos commented

If the module is intended to be installed in a nonstandard location, then the documentation should reflect this, regardless of the reason.

jpulles’s picture

jpulles commented

I'm sorry that I don't understand this issue.
As stated before: "The mapbuilder module can be installed where drupal allows it.". This can be under sites/all/modules or modules. On my own system, I have it installed under sites/all/modules, as is the default for drupal 5.

hyperlogos’s picture

hyperlogos commented

Ah, I misparsed. I apologize.

Perhaps the defaults could be changed to reflect being installed in the sites/all/modules directory? Again, my reasoning is that this is where people are "supposed" to install modules in Drupal 5.

I will now stop hassling you for this :)

jpulles’s picture

jpulles commented
Status: Active » Fixed

Default setting for mapbuilder location now depends on value of drupal VERSION constant. 'modules/..' for drupal version < 5, else 'sites/all/modules/..'.

Anonymous’s picture

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