Closed ro-la closed 2 years ago
This was originally by design, see the module description: "This module cannot be disabled." I decided to do it like this because
I may have to rethink this. I am aware that this contradicts the advice to disable all custom modules when investigating bugs. In the meantime, the workaround is to remove or rename the respective directory instead.
Fixed in latest release: Module may now be disabled.
Trying to deactivate all Vesta modules there will be displayed a message "Modul Common deactivated" but the check box is still checked.