Closed h0od closed 3 years ago
This fixes #391
Yeah, that's the problem. However, I'd say that the current approach needs to be refactored to prevent bugs like this from happening as you shouldn't need to remember to call setDirty at every location where settings are being changed. Similar bugs currently also exist in the Windows UI.
When a user runs the
--configure
wizard we are effectively mutating theWebServerManager::plainServerConfig
andWebServerManager::tlsServerConfig
fields. So theWebServerManager::isDirty
flag was never set, and no file was written.