[bug] Saving confing in /admin/backend is very frustating

[gaspo53]

I've been having some trouble saving changes to an S3 bucket backend. There's no confirmation of the change, and it doesn't always work. I'm not sure how the JavaScript events are being handled, but even though I've tried everything I can think of, like losing focus, pressing tab, clicking, hitting enter, refreshing the page, and even force-refreshing the page (which clears the cache), the changes are only saved about 1 out of 10 times. It's like a lottery!

In addition to reporting the bug, I think it would be really helpful if we could replace the AJAX edit/save feature with a simple Save button. That way, it would be easier to make changes and know that they've been saved. What do you think?

[dr4tinymous]

In the docker installation at least, there is a spinning icon indicator while writes are happening; it's pretty quick and frequent. i know that isn't going to solve your situation but i'm hoping it will help a little for the time being!

[timptner]

I'm also very much pro save-button. When making changes in the admin config they will instantly update inbetween typing and if a user logs in right at that moment they could access unexpected paths. This could even become an security problem.

Is there a way to change the config directly via file on the server? Would the file change be recognized by the server process?