- 🇺🇸United States nicxvan
Do we still want this? How will it work when core modules are moved to contrib?
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.
Active
11.0 🔥
extension system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Do we still want this? How will it work when core modules are moved to contrib?