Hi Ron and Tom,
After restoring the database to the state before I started to 'try things out', I asked the user to login with their old login, and the problem remained in the sense that only newly created LO's were editable - LO's created as recently as yesterday afternoon were not editable.
I then took the step of renaming the user's faulty account to first.last_old, and asked the user to log back in and then back out so that Xerte could create a new login.
I then edited the login ID of the faulty Xerte account to be the highest login ID number plus 1, then renamed the login ID of the user's new Xerte account to be the number of the faulty login, thereby getting the new ID to inherit the projects of the faulty ID. A bit confusing, but it works!
The only issue is that many, if not all LO's created in version 3.1 and version 2.1 no longer work, but recently created ones and new LO's are editable and playable.
The user has confirmed that the previous ones can be dropped - there are still backups of those LO's, but they are in the archived versions of the Xerte websites, so if the user really needs those LO's, they can access the archived Xerte website(s) to export those LO's as zipped files and import them into the live website (haven't tried this yet).
The case sensitivity issue was something that was overloooked - I have now renamed all of the user's project folders to match the case sensitivity used by their Xerte login, but it doesn't seem to have restored access or functionality to the previously created LO's.
As the fixing of this user's account was done during the half-term break, there weren't any other users logged onto Xerte, so I don't think that any other users were affected (I hope).
Thanks again for your help Ron and Tom.
