No, I AM afraid. I tried not to be afraid, but still was afraid. Oh well.
The only place where I am having problems is in the workshop. I have one more workshop to do this term and don't want to rock the boat if the rest of the system is all right. If it isn't, I will consider reinstalling from scratch. However, I hadn't even restored a course until this morning and it was daunting enough. To think of voluntarily deleting all of my three existing courses (about 130 students) and my 6 or so hidden courses at this point in the term is beyond my current level of courage.
When I think about my upgrades over the past 9 months or so, there was only one time during which things didn't go as planned. I use cvs and at some point in the summer, upgraded from (I think) 1.3.? to 1.4. I didn't realize that it was necessary to specify the moodle_14_stable root so I ended up upgrading to some other level (forget which now). I solved it by re-applying the upgrade to the 14_stable platform and it proceded well. My recent upgrade from 1.4.1 to 1.4.2 went fine with no errors. I also upgraded to 1.4.2+ today and it went fine too.
Do you think I caused system-wide problems for myself last summer, or are the problems specifically with the workshop module? I guess this question is also directed to Martin.
I have "repaired" my database using phpMyAdmin
several times in the hopes of getting the workshop going smoothly. Since this hasn't worked, is there some other less draconian strategy available? If not, how do I make sure I don't lose all of my course backups and user information? If I backup a course and download
the backup to my own computer it is possible to get the backup in the server
again, but the procedure is complicated because of the various security measures I have in place on the server. As noted above, it is also just too scary a move to make without being pushed into a corner with nowhere else to go.
Sorry to be a chicken after all.