TOPIC:

Hi,
We upgraded MySQL from 7 to 8, then upgraded Xerte from 3.12.30 to 3.13.24.

New projects are created, and open, but the Xerte editing window does not load. Pre-upgrade Projects, the links to those do not load, and display a blank screen.

Do you have any suggestions, or is it possible to re-set the version number to something, and then re-run the upgrade script, to check the output?

Thank you

Was anything else changed like the site address or the path to the Xerte directory?
Did directory permissions and/or the Apache user change?
MySQL user for the Xerte database still correct?
When you login do you see the previous projects in your workspace or an empty workspace?
What steps exactly did you take during the upgrade?
When you create a new project what gets created in the USER-FILES directory?
Where there any errors when you ran the upgrade script?
Did you use the full 3.13 download and not just the 3.13 update? The latter is just for updating 3.13. to a newer version of 3.13.
What does the Apache error log indicate?
Answer those questions and we might be able to advise.

Hello, thank you for the reply.
The site address, path remained the same, no further changes were made.
Directory permissions and Apache user were the same.
The MySQL user has the same name and permissions.
I can see previous projects in the list, just unable to open them.
For the install, I copied out the old files to a backup folder, then unzipped the install file (full 3.13 download), then restored the following folders
/error_logs
/import
/USER-FILES
/tsugi
database.php
I can't remember seeing an error message in the upgrade script - however I'm not 100% on this, and I don't seem to have saved a copy as I normally do.
I'm unable to view the Apache logs.
As a test, I've copied out the existing (3.13) html folder, and put the backup copy running 3.12 back in it's place. When I did that, Xerte is running OK (but the database changes haven't been rolled back). As this works, I presume the upgrade in the database may not be the issue.

You didn't need to move any folders you can just unzip the new release over the top of the existing release. Any important files to remove are removed as part of the upgrade script.
If you've "put the backup copy running 3.12 back in it's place" assuming you mean the parent and sub directories then just extract the 3.13 zip over the top.
You can then run the upgrade script again and it should just report that everything is already done unless it failed the first time.
But if you have moved directories about then make sure hidden files like .htaccess files are put back too and that the directories you mention are owned and writeable by the Apache user. Do that before running the upgrade script and make sure the db user has full permissions on the db.
Obviously back everything up first, including the db, but if USER-FILES is large you could potentially exclude that from the backup if needed and keep in mind that unless you prevent users from log in changes could be made at any point.
After all that when trying to edit be sure to force refresh and/or clear offline files or run the dev console when opening the editor.
HTH
Ron