I upgraded from 1.0-final to 1.1 and seemed OK at first with a totally new chat window. Then I tried logging into a chat with existing serverid and it was not at all happy. Window didn't draw. Had a bunch of small images on left side and that's it. Been debugging my messy code all evening. So thought ... hmm perhaps the existing data files in private directory (being store outside the unzipped folder structure) was not being read or understood or such confusion. Thinking perhaps my $params["data_private_path"] was not set correctly? But hey, that never changed? So thought for debug I'd just clean out the directory of all old files and see if the software create new private data files in proper folder. So I did that test and it worked correctly. The new private data files are created. So what to think? Am guessing the older (pre-upgrade) files are not being read correctly by the new version? I don't know for sure. Am getting really frustrated with this. Would someone else please report on this. I'm kinda disgusted with it right now.
I didn't test with a migration from a 1.0-final data_private_path to a 1.1 data_private_path so I cannot guarantee that it works. It should be possible to automatically test the version number when accessing the data_private_path files but it has not been yet implemented.
However why just clearing the directory content is not satisfactory ?
Thanks for the honest & quick response. I am dealing with new directory. The chat conversations would (hopefully many many of them in future) be backed up daily and remain viewable as a form of notes. So people coming to the chat later can look back at conversation. If the data files can't be read then it messes up both the archiving and the ability for users to look at older data. Please keep this in mind when you upgrade. It's a real nightmare discovering the data isn't accessible. Surprising and stressful. Totally unexpected.