- Issue created by @pcate
- πΊπΈUnited States pcate
From my limited research this error may be because the module's
.info
file does not specify module dependencies. - last update
over 1 year ago 9 pass - @pcate opened merge request.
- Status changed to Needs review
over 1 year ago 5:06pm 21 April 2023 - πΊπΈUnited States pcate
Created MR for adding the core media module as a dependency. The MR resolved the issue for me.
- Assigned to maacl
- Status changed to Needs work
over 1 year ago 8:49am 24 April 2023 - π©πͺGermany maacl
Thanks for the report and the patch, let's see if we can add a test for this.
- πΊπΈUnited States pcate
let's see if we can add a test for this.
Honestly I'm not sure how to test this. Did you have a specific approach you were thinking of?
- Issue was unassigned.
- π©πͺGermany maacl
let's see if we can add a test for this.
Honestly I'm not sure how to test this. Did you have a specific approach you were thinking of?
I think it should be possible to install the module in a test, and then it should only pass if the media and file module are enabled also? And currently they won't be enabled because of the missing dependency.
- πΊπΈUnited States pcate
@maacl not sure how useful a test for this is. It seems like it would be testing Drupal module dependency system rather than this module itself. The module has a clear dependency on the core media module that should be declared.