Contrib.social

Module not visible in admin/modules or admin/reports/updates

Open on Drupal.org →
Created on 17 September 2023, about 2 years ago

Problem/Motivation

The contrib forum module is not visible in admin/modules or admin/reports/updates and therefore cannot be enabled or uninstalled from the admin ui.
Obviously module updates will not be visible in admin/reports/updates
The module can be enabled using drush.
It's not clear whether available module updates can be detected and implemented with composer.

Steps to reproduce

In Drupal 10.x install the module using composer.
View admin/modules and the contrib forum module is not visible. Only the core forum module appears.
View admin/reports/updates and the contrib forum module is not visible.

Enable the module with drush and the same occurs.

The module can only be disabled with drush, and then removed with composer, but only after removing all forum categories.

Proposed resolution

This may be related in part to https://www.drupal.org/project/forum/issues/3358942 📌 Add a composer.json file Needs review which requests the addition of a composer.json file

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

GrahamShepherd

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @GrahamShepherd
  • Status changed to Closed: works as designed about 2 years ago
  • Comment about 2 years ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    Drupals module discovery system favours a module in /modules over one in /core
    So if you have both, the contrib one is in use

    I would recommend removing the contrib one from your codebase for now

    We wanted to remove it from core for 10.x but didn't complete it. So for now there are no differences, we hope to remove the core one before 11

  • Comment 3 months ago →
    🇩🇰Denmark ressa Copenhagen

    I searched for keywords such as "site:drupal.org module discovery hierarchy", but didn't find a documentation page about this ... So like this Issue Summary says, it seems to be an undocumented feature:

    By design, Drupal allows multiple copies of a module in different directory spaces (eg one in /core/modules, one in /modules, one in sites/all/modules).

    However, if duplicate copies exist in the same space, this works too, though I assume this is by accident rather than by design. So for example if I have:

    - sites/all/modules/foo
    - sites/all/modules/contrib/foo

    then the first one is taken by Drupal, and the second one is simply ignored.

    However, because this behaviour is undocumented, it effectively puts the codebase in an unstable state: a developer doesn't know which module is being used by Drupal without inspecting the system table.

    From #2647388: Don't allow duplicate modules in the same directory space → .

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024