[ModuleManager] when it's set to Active:no - page fails to load

[christinerogers]

Basically this module should never be configured to Active:No -- but it should still fail a bit more elegantly here on the off chance it is.

currently it loads with a blank page saying "this module could not be found" if it's set to Active:no (in the modules table i think)

found during C-BIg testing may 9. filed a bug after discussion with @ridz1208 and Dave.

[driusan]

The problem isn't that it fails when Active='N', the problem is that it fails when it's not on the file system (even if it's inactive)

[ridz1208]

@driusan maybe it can be a try catch to get the module info and if it fails it can just replace with NA or some other message

[christinerogers]

still seems like an important bug (did not test)

[sruthymathew123]

@driusan @christinerogers I agree that this module shouldn't be set No; But I am getting the below attached attached message when set to 'No'..

What is the fix we need to implement here. I am little confused.

[charliehenrib]

Could probably be fixed if the changes in https://github.com/aces/Loris/issues/7083 were implemented.