Hi THenrich,
THenrich wrote:Xampp Control Panel having two sets of configs is a bad idea.
XAMPP control panel does not have two sets of configs.
Apache has it's own config files. MySQL, PHP, etc have their own config files too.
And the XAMPP control panel has its own config file too.
THenrich wrote:I changed the port numbers for Apache in the httpd.conf & hhtps-ssl.conf files (known this years ago) and Apache couldn't start
okay
THenrich wrote:and error showed it tried to use 80 and 443. What?
Which error? The messages in the XAMPP control panel?
The control panel prechecks need to know the new ports too. Otherwise it cannot check if these ports are free.
THenrich wrote:Is it not reading those config files?
No, the control panel does not contain a comprehensive config file parser. But the control panel is open source, so if you want that functionality, simply implement it and share it with the community.
THenrich wrote:Then I noticed the other Config button and the 'Service and Port Settings' and they had their own port numbers settings. Changed them. Apache still couldn't start
Shurely not, these ports are just used for the prechecks which should help you debug common issues.
THenrich wrote:Sheesh. Why doesn't XAMPP's config setting change the other setting files as well?
Writing a bullet proof config file parser is not such an easy task. There are multiple ways and files where you can configure your ports and other configs.
The control panel was made from a normal board user and he was so kind to share it with everybody. If you don't like the control panel simply don't use it or add the needed functionality yourself.
There are no plans yet to add this functionality in the next times.
THenrich wrote:Also the error message should indicate clearly the port settings mismatch. Annoying.
Again, the config files don't get parsed, so the control panel does not have any clue which ports Apache tries to allocate.
best wishes,
Altrea