Skip to content

BUG: Modules with issues in dependencies are locked, which prevents disabling them to solve the problem, and prevents enabling/disabling any modules at all #125

Description

@shemetz

Right now I have:

  1. module-c which is enabled and requires omdule-a and module-b as dependencies
  2. module-b which is enabled and functional
  3. module-a which is disabled and broken due to not being migrated to the latest foundry version
    3.1. because it is broken, I do not see it in the module management screen at all

(this is in V13, but doesn't feel like a v13-only bug)

Now this causes two bugs which are terrible when put together:

  • I cannot save module settings at all, because saving fails and gives me a ui warning notification that says module-c cannot be enabled because module-a is not enabled
  • I cannot turn off module-c because of the same problem -- the checkbox is disabled and stuck in the "active" state. therefore, I can't solve the problem, except via safe mode or via uninstalling the other modules

Image

Image

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions