Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Sometimes when developing you end up with a duplicate copy of a module somewhere, and this causes a lot of headscratching when you make changes in one copy and Drupal is actually using the other one. There doesn't seem to be a good reason to allow this situation where Drupal just arbitrarily selects one version of the module to use, so to avoid many man hours of debugging time we should detect this situation and report an error rather than leave it for the developer to track down.
Comments
Comment #2
longwaveRelated to #2472119: Extension installers allow extensions with duplicate names to be enabled but that deals with enabling modules and themes with the same name, this can occur if an already enabled extension suddenly exists twice in the filesystem.
Comment #3
dawehnerWell that is tricky. There is this even feature that you can override one module with another version in a more specific directory.
Comment #4
Wim LeersI ran into this today.
I had
/modules/big_pipe
and/modules/big_pipe_broken_git
. I was working on/modules/big_pipe
, but my changes had no effect. It was maddening. Turns out Drupal was actually using/modules/big_pipe_broken_git
. We should at least make sure to prefer the directory name matching the module name.Then again, it's kind of PEBKAC.
Not sure.
Comment #5
dawehnerWel yeah we could do at least that, but its kinda magic.