Isaac was simply referencing that your referenced post was in 2012, and a backup function had been added in later builds. We have nothing to do with the lock and write function, it was written well before we began development on any portion of the software.
When we post updates in various threads, especially when i referencing items older than a couple of years, we always reference the date they were made; this is pretty standard for a product with support discussions over 15 years old that contain outdated information.
We consider every UBB System's customer inquiry important, however this is a rather ancient product which we're trying to bring into today's standards, we have yet to recode every bit of the software as it takes quite a bit of time to get very far at all.
We go through huge undertakings to update portions of the software; for example, the PHP 7 rewrite took the better part of a year to get the database handler and all portions of coding to play nice with modern systems. This doesn't even include keeping up to date with further changes to PHP while retaining backwards comparability with outdated systems.
I understand that things can be infuriating to some, but we try to fix things when we can replicate them; We have attempted to recreate all sorts of methods of zero out the configuration file and have found several items which can cause it such as closing your browser while the files are being written to. A method towards recovery was introducing the backup when a new settings are written to file so that one can have a snapshot of their configuration before attempted changes to the system until a fix could be identified and pushed out..
I also understand that, while promises and ideas made by previous developers may seem easy to implement and adapt changes, however we are not those programmers and items take time to write and test; we are just two guys on the West coast trying to provide a service to a vendor.
