Above she said, "I updated from I believe 1.8.10 to 2.9.1" so unless it was a typo and she meant 2.8.10, but there was no 2.8.10 though was there, so maybe 2.8.1....mmmm
Doesn't matter I suspect she would not be getting those errors unless the original was v1.8 or v1.9. The value of consistent upgrades. I know I get slack and only do mine once a year now, but the version leaps are not that great a year apart.
Bottom line though is still that the database as is, is likely dead, the codebase is probably so badly mauled that it needs to be replaced, and hopefully the moodledata folder is still intact. I really do think that if that is so, restoring the database, via phpMyAdmin, then restoring the original code, or even upgrading to v1.9.19 and reusing the config.php file, should see the original course structure in place.
Don't forget, the database wasn't as stringent in v1.x as it became in v2.x and there was a much greater reliance upon the moodledata folder than there is now. There was also considerably more relaxed linking between the two which made it easy to manipulate courses. From memory, if I couldn't upload a course due to size restrictions or something, I created the course using the correct name. Then manually uploaded the required materials into the subfolders created by Moodle for it. Oh there was a number of things that had to be done, and I may have had to copy and paste materials into pages created, made sure the links to images and external resources were correct. It wasn't without its own dramas, but it saved me time.
A full restoration would be the ideal, but this is one way it could be done to get out of the immediate problem.
For me, it is what happens next that is important. I would seriously suggest that Ana create a brand new v2.2 Moodle, as a test site before trying to update her production site. Restore some courses into that complete with user data. See what happens.
