Values are not saved to the database in some situation
Preconditions are typical for situation, when the user solves some problem on the production server:
- Using 'memecached' before stopping the webserver python process.
- Database has been reseted or restored from backup or other project with other database have been started after stopping the previous.
Problem: Previous vaues stored in memcached are displayed on the page http://127.0.0.1/settings/ , what is natural and is not so bad and can be even useful. After changing some values, only those new changed are saved. Values which are different between the old and the new database are not updated to values, which are stored by the web form.
It is not significant whether original process and/or database was a normal one or an auxiliary one for the purpose to investigate some problem.
Solution It should be definitely saved the same what was on the form, when "Updatete Settings" have been pressed. \
The best would be to highlight by some color values different between database and cache, when /settings/ are displayed. To display cached values, because it is the most consistent with the behavior of normal server, but to display a link for resetting livesettings in the cache, if there is a difference. (This way also some values from one configuration can be imported to other configuration.)