General behavior when saving in Cockpit

After saving entries or changes, the GUI is blocked for some time (more or less long) because every single change is immediately made known to the system in the background.

For some areas, however, multiple entries or changes are not atypical, e.g. when creating DNS entries, this takes a lot of time.

In such cases it would be good if a distinction could be made between “saving the input” (followed by checking the field and transferring it to the config DB) and actually “applying the changes” by calling the actual e-smith procedure.

Regards yummiweb


In the “firewall” section it should already be so.
It would be desirable to expand this behavior to other sections/applications as well.

1 Like