User config data is lost on update.
zelon88 opened this issue · comments
I (the developer) have noticed for the last week or so that when HRCloud2 is manually updated to a newer version it will re-write it's user configuration files... even if they exist.
This can cause users to have to re-visit their Settings page to manually re-set their color scheme and HRAI settings.
No User generated Data is affected. Only HRC2 generated cache files that store user speecific cache information. Playlists, temp files, Shared files, log files, and App generated files are unaffected.
Although I do not belive this is neccesarily a bad thing (as it keeps the format of generated files up-to-date) it can be annoying to end-users.
If you are running HRC2 in a commercial or semi-formal environment with users who could get aggrivated, please have a blog, Twitter, or other means to communicate when you update HRC2 to your users to avoid unneccesary complaints.
I will keep this issue in mind as I sift through code and hopefully resolve it if I come across a solution. Thank you for bearing with me.
It turns out that the problem wasn't in HRCloud2, but rather the process used to update HRCloud2.
If your process for updating HRCloud2 involves changing the permissions of the HRCloud2 directory or any of it's subdirectories, they must be returned to www-data ownership by using the following command:
sudo chown -R www-data /var/www/html/HRProprietary/HRCloud2
ALSO REMEMBER to re-"chown" any other directories you may have changed.
Properly updating HRCloud2 and preserving the file ownership will cause HRCloud2 to LEAVE user cache files (rather than discarding them and re-generating them).
Failure to properly preserve file ownership will cause HRCloud2 to sucessfully detect cache files that it cannot open (due to permissions and/or ownership discrepency). When it cannot open the files, HRCloud2 will attempt to remove and replace the files... Which is very effective. This keeps HRC2 safer, but causes user settings to be returned to default when the update process is not performed correctly.
Maybe we need an "auto-update" feature to automate this process?