Open jaimeperez opened 9 years ago
Now that we've moved the module configuration to config.php, is this still needed? Can composer take care of this? I hope so because if we add an 'enable' file here it would have to be changed later on when the enable/disable files are depracated.
That's precisely one of the advantages with files, that there was no need for further enabling of the module after installing it. If we wanted, we could even have our composer module installer to automatically enable installed modules by adding the enable
file if missing. However, that's not possible with pure PHP configuration... 😞
Now we are using composer, those modules installed with it won't be in place unless the user explicitly installs them. When a user installs this module, it will be disabled by default, and he or she will need to enable it by including an enable file in the root of the module. That file will be removed when updating the module with composer again.
Therefore, default behaviour should be to enable external modules by default.