Closed VasasA closed 11 months ago
Thanks for filing this issue @VasasA 👍
@jenlampton it seems that this may be caused when the search_api module is not installed/enabled (can someone please confirm this?).
The search_api module is already declared as a dependency in metatag_search_test.info
, so this could be a Backdrop core bug if this happens with search_api not present (it is my understanding that in that case, the test should not run in the first place).
I think the real question is: why is coder upgrade module doing anything with metatag module, especially trying to run its tests? Sounds like a bug in coder upgrade.
There's no core bug here unless this happened while you are using core to run tests. Not only are we not using core to perform this action, but coder shouldn't be running tests at all, I don't think.
If coder is trying to run tests, it may need to be updated to work how backdrop runs tests, instead of how Drupal runs tests.
Thanks for filing this issue @VasasA 👍
@jenlampton it seems that this may be caused when the search_api module is not installed/enabled (can someone please confirm this?).
The search_api module is already declared as a dependency in
metatag_search_test.info
, so this could be a Backdrop core bug if this happens with search_api not present (it is my understanding that in that case, the test should not run in the first place).
I can confirm that installing the search api module before installing the code upgrade module everything work as it should be working
I just ran into this. It's not that coder_upgrade is running tests, but it is trying to module_load_include()
all modules, including disabled modules (which still seems wrong).
So, I agree with @jenlampton that this is a bug in coder_upgrade. There's a bug filed over there. https://github.com/backdrop-contrib/coder_upgrade/issues/59
This was fixed over in https://github.com/backdrop-contrib/coder_upgrade/issues/59. Thanks @bugfolder!
See this: https://forum.backdropcms.org/node/551
Posted by laz: