Set Reconfigure Services default to [no] during update when reconfigure is not necessary
I have made several customizations to configuration files that are under ISPConfig's control, and every time I upgrade ISPConfig, I hesitate when prompted with that dreaded question: Reconfigure Services?
For example, I have disabled ClamAV in my Amavis configuration, and if I allow ISPConfig to reconfigure services, there exists the potential for my customizations to be mitigated. Where Amavis and ClamAV are concerned, this reconfiguration has the potential to prevent mail from being delivered on the server, which is a "major issue".
It seems that it would be trivial for ISPConfig developers to keep track of which changes in a given release may not function correctly unless services are reconfigured.
If there are no such changes in a given release window (current revision to target revision), then the "Reconfigure Services?" option in the update script should default to [no (not necessary)] or similar.
Quite frankly, I would rather the default be [no] and that certain features of ISPConfig do not function as designed than risk problems that could arise from reconfiguration.
It seems much easier to reconfigure services later if something is not working as expected than to debug a "broken" system after ISPConfig reconfigures services and undoes a critical customization in the process.