Bad request if config is not read/writeable

[michaelmittermair]

I migrated from a docker container to an LCX container. Therefore, I moved the data to the new system. Everything was updated with the correct owner, just the config.json was not changed to the correct owner.

During changing data in the admin-area, the save throws and "400 Bad Request", but the UI shows, that the changed are there (also after a force refresh). The changed settings are active, until I update to the next version.

After chaning the owner to the correct user, saving is working.

I would recommend, that the response contain an information, that the config file is not writeable.