To backup, I used cuteFTP to copy my moodle directory - which in my case appears to be the root public_http. I then used mySQL and phpMyAdmin through cPanel to export a copy of the database (in my case, mqtclass_mdl1), to my hard drive.
Now I will try installing 1.7.2 as per the instructions...any advice from people who are more familiar with the process would be appreciated.
First question - does it complicate things at all that my moodle directory is the public_http? I think that means I will not be able to simply rename the folder as a backup before beginning.
Thanks,
Alex
Okay...so if I do what the instructions say and "Overwrite the files in the current Moodle directory with the new version's ones," won't this delete my modified theme and the certificate module that I added?
Also, I do not appear to have a moodledata folder anywhere in my site. Is this a problem?
I should also correct my previous post - where I said "public_http," it should read "public_html." Sorry!
Thanks.
I did manage to find the folder that contains all the course data - called uploaddata, in my main moodle directory (public_html). Still posting my efforts in hopes that someone will chime in and say I'm on the right track, or in over my head...
Apologies for generating so many emails for those subscribed to this forum.
Thanks,
Alex
AG,
- If you're going to be overwriting files, I hope you have everything backed up first (including your moodle data folder)! You're probably right about not being able to back up public_html by renaming it, so copy it (including all sub-folders recursively) to another folder, which is not that much harder.
- Since your data folder is in public_html, which I presume is your root web files folder, I hope it has a .htaccess (or equivalent, depending on your web server s/w) file in it to prevent web browsers from being able to access it.
- Your certificate module is not in the moodle folder but in sub-folders of it, so overwriting the files in the moodle folder should not affect them. True, sub-folders of moodle are involved in the Moodle installation process, but only files with the same pathnames as new files being installed will be overwritten. See http://docs.moodle.org/en/Certificate_module. If I'm wrong about that, won't you be glad you backed everything up!

- Likewise, starting with version 1.7, your theme(s) are in a separate folder; see http://docs.moodle.org/en/Theme_directory.
- I think I've answered all your questions in all three posts. HTH.
RLE
Thank you very much for the reply. It gave me the confidence to go ahead with the upgrade, and all appears to have gone smoothly!
Also - I do have a .htaccess in my public_html folder. Good to check that, too. The site configuration was not really my choice - it is a hosted moodle account through siteground.
Anyway - I appreciate the reply and am happy to report success. It wasn't anywhere near as complicated as I expected.
AG,
Your welcome. I'm glad things are going well. However, I apparently was not clear in my statement about the .htaccess file. I meant the moodle data folder should have an .htaccess file in it, so that its contents would not be accessible via a web browser. This is necessary since your data folder is inside your web folder, if I understood you correctly. If you have an .htaccess file in your web folder, I'm sure it does not contain the commands to make that folder web inaccessible; if it did, you wouldn't be able to use your Moodle installation at all, which you apparently have.
The command that needs to be in the .htaccess file in the data folder to make it web inaccessible is:
deny from all
See http://docs.moodle.org/en/Installing_Moodle#Creating_the_data_directory_.28moodledata.29
RLE
The moodle data directory also has an .htaccess file in it, with the following:
"deny from all
AllowOverride None"
So I assume all is well.
I bet this also explains the notification in my administration panel:
"Your site configuration might not be secure. Please make sure that your dataroot directory is not directly accessible via web."
Thanks for explaining that - it was kind of disconcerting not to know if the site was secure.
Thanks,
AG