When drupal finds a module with the same name as a system module outside of the system modules directory, say in sites/all/modules, it knows that this module has moved and updates its location. Presumably this is intended to permit you to supersede system modules, to recognize when you move a module to/from a site-specific module directory, et cetera. But it doesn't recognize that the replacement has gone away. I found this problem by accidentally unpacking drupal 5.1 inside my sites/all/modules directory.

It would be nice if Drupal would check back in the system modules directory for those missing modules. Possibly this functionality depends on some module that Drupal couldn't find? In which case this is actually a bug against drupal 5.1 :)

Please see this comment for the long explanation. Please forgive any inaccuracies there (or here!)

Comments

Pasqualle’s picture

Version: 6.x-dev » 8.x-dev
jhedstrom’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

If I copy the node module into /modules, clear caches, then the new location is picked up. If I remove that directory, clear caches again, then the old location is restored.