[BUG] Config generator not updated and creating errors

[MrCybertux]

What happened?

The config gen was not updated and is in my experience quite buggy.
Even if set to 1.6.1 it still gives out wrong compose configs:

also importing a config is not possible if i change at least 1 setting in the config (in this case just activate default CRS):

How to reproduce?

Use the online config tool and change 1 setting before importing. (Import problem)

Set version to 1.6.1 in config editor and get the compose file. (Not Updated config)

Configuration file(s) (yaml or .env)

{"general":{"USE_MODSECURITY_GLOBAL_CRS":"yes"},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"service_1":{"SERVER_NAME":"service_1"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":""}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":"1.6.1"}{"general":{},"www.example.com":{"SERVER_NAME":"www.example.com"},"BUNKERWEB_VERSION":"1.6.1"}

Relevant log output

BunkerWeb version

1.6.1

What integration are you using?

Docker

Linux distribution (if applicable)

No response

Removed private data

• I have removed all private data from the configuration file and the logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[TheophileDiot]

Hi @MrCybertux,

Thanks for opening this issue—we appreciate you bringing it to our attention! We're already aware of this problem but haven't had the chance to update compatibility with version 1.6 yet.

We'll address this as soon as possible 🚀. Sorry for any inconvenience caused, and thanks again for your patience!