Admin: deal with JSON corruption (not just on reset, but happened mid-usage!)

[justjulie]

[justjulie]

Found and fixed one aspect which seemed to reliably trigger the corruption, which was posting a manual update without filling out the "who" field. Fix was to simply display an error if all three fields are not filled out.

However, the corruption still occurs, just less reliably (in our limited testing). It appears the issue is doing multi-threading when using TinyDB (which is an in-memory database). Long-term solution would be to convert to MySQL or some other DB. No time to implement before AO 2021, so will go back to single threading for now.

This issue can be closed once the single-threading is implemented (and appears to address the corruption). DB change will be addressed via Issue #23