Missing Munkireport module about munkireport-php HOT 4 CLOSED

Something is wrong with the module's folder and structure on the server.

Module Marketplace lists a module as enabled by directly comparing MODULES in .env. dump_modules/env defines an enabled module by one that has a ms_defender_model.php or install.sh, which make it a valid module.

Verify that the module has tuxudo/ms_defender/ms_defender_model.php and tuxudo/scripts/install.sh

from munkireport-php.

@tuxudo
As additional information we are running MunkiReport on an AWS EC2 instance. I got our DevOps team to enable using a ssh session to allow interactive debugging via a shell. Via this we did an export of the MODULES variable and it does contain ms_defender.

The vendor/munkireport/ directory does contain an ms_defender folder which contains amongst others ms_defender_model.php and a subdirectory called scripts which contains both an install.sh and uninstall.sh

As a reminder as per the picture in my original post Munkireport also shows the module as installed. It is just not reporting it in the list of modules and not including it in the install script.

from munkireport-php.

It is showing as installed in Module Marketplace because when the MunkiReport server compares the composer.local and the MODULES variable in .env, there is a match for ms_defender. This does not mean it is a valid module.

Verify permissions on the ms_defender module folder and files. Use composer to remove and reinstall the module. Verify that there is only one instance of the MODULES variable in the .env file. Lastly verify the module loads when going to https://yourmunkireport.com/munkireport-php/index.php?/module/ms_defender/index

from munkireport-php.

@tuxudo I have been working with our DevOps engineer and it looks like the module was in the right place, was installed properly and the modules was in the enabled list but we had not added the module directory to the MODULE_SEARCH_PATHS

Now seems to show up.

from munkireport-php.