Hi, I had several occasions now, where a problem only had the reason, that the vhosts file would not be accepted. If I hadn't checked the log, I would never have known why my vhosts config wasn't updated anymore. It would be helpful, if any error that results in a old vhosts being used, would be escalated/written/popuped somewhere visibly. Those Errors usually result from the httpd -t ISPConfig makes, and I guess it could be possible to pipe that output to some file that is displayed then.
Maybe a more quick solution could be to just display the ispconfig.log in the webinterface, but then you would still have to check this log after changing settings. But for my understanding the update process is an asynchronous one, so that there won't be a possibility to directly feedback to the webinterface after submitting the new data. Another thing is how to find a more general solution, e.g. an enduser won't be really interested in seeing these errors...
yeah, I always forget that there are endusers working with this But of course it would be important for them to know, that no changes are applied. And to inform the admin, they should have a way to copy&paste the relevant error from httpd -t. Currently even I can't see the error in the log, I have to copy the "broken" config there, run httpd -t manually and check the error. Thinking about bigger sites, where users can (can they?) enter Apache directives, they could break the system for everyone else... Just a thought, I'm the only user of ISPconfig here, and *I* know now about the importance of checking that log
