Talk:Upgrading: Difference between revisions

Revision as of 13:46, 29 October 2006

Notes --Chris collman 07:34, 29 October 2006 (CST)

Sorry for this ramble but... this page needs more work. My instincts don't like the instructions for using download archive, but I am not qualified. Suspect they are Moodle 1.0 .

For example, this section the instructions tell me to copy the old moodle to moodle-backup, then unpack moodle-latest to moodle-backup (that is what the mv command says I believe). Big issue not mentioned is that non-standard modules (Score Lock comes to mind) alters the SQL tables. While any non-standard module should not, who knows the ways a site may have been improved which will impact more than just the moodle files. We just have to be careful about being too specific and run up a huge red flag for those who like to jump off cliffs

This page starts off by refereing to installing 1.6 (good) for more specific instructions. I think the entire page needs to either be more generic with lots of links, and/or give general instructions as in a checklist. There are too many types of Moodle installations to get specific. How different are installs from updates? --Chris collman 07:46, 29 October 2006 (CST)

What does the below line mean?

You can also use the "Export" feature in Moodle's optional "Database" web interface to do the same thing on all platforms.

Is it a reference to PHPMyAdmin, maybe? If yes, then this might confuse people now that there is a Moodle module "Database" too, which is quite unrelated to the whole Moodle installation database... Samuli Karevaara 17:43, 15 April 2006 (WST)

I agree - this comes from a time space where there wasn't such a thing as a database module. I see that it is called MySQL Admin on the download pages these days - I'll update the page accordingly --Koen roggemans 18:37, 17 April 2006 (WST)

Okay, I see! Now, specially with the new descriptive text and a link, it makes a lot more sense :-) Samuli Karevaara 20:53, 18 April 2006 (WST)

@@ Line 1: / Line 1: @@
 ==Notes --[[User:chris collman|chris collman]] 07:34, 29 October 2006 (CST)==
-Sorry for this ramble but...My instincts don't like the instructions for backup, but I am not qualified.  Suspect they are Moodle 1.0 .  It almost seems to me that the instructions say to copy the old moodle to moodle-backup, then unpack moodle-latest to moodle-backup (that is what the mv command says I believe). Big issue not mentioned is that non-standard modules (Score Lock comes to mind) alters the SQL tables. While any non-standard module should not, who knows the ways a site may have been improved which will impact more than just the moodle files.  There is no mention of the moodledata (or equal directory), another generic assumption.  We just have to be careful about being too specific and run up a huge red flag for those who like to jump off cliffs ! :)  I would suggest something like:
+Sorry for this ramble but... this page needs more work. My instincts don't like the instructions for using download archive, but I am not qualified.  Suspect they are Moodle 1.0 .
-::A standard distribution is a compressed file of the Moodle file structure, which is located in a directory called "moodle".  Do not update an old installation unless you know what you are doing. Backup everything.
+For example, this section the instructions tell me to copy the old moodle to moodle-backup, then unpack moodle-latest to moodle-backup (that is what the mv command says I believe). Big issue not mentioned is that non-standard modules (Score Lock comes to mind) alters the SQL tables. While any non-standard module should not, who knows the ways a site may have been improved which will impact more than just the moodle files.   We just have to be careful about being too specific and run up a huge red flag for those who like to jump off cliffs
-::Sometimes there are old files or non-standard modules sometimes change the SQL database that can cause problems.  Since there are so many types of Moodle installations, there is no one way to do the best backup of a working Moodle site.  The less your site has been customized by non standard modules or code hacks, the less issues.  In short, upgrading a standard Moodle site with a standard distribution package should go smoothly because it has been tested by many other people.
-::In general: backup the moodle dirctory/files and moodledata files.  Unpack the standard distribution into the moodle directory.  Start the new Moodle and the automatic update process.  Check to make sure the site works.  Next copy unique themes and languages from the backup and perhaps new versions of the non-standard modules into the moodle directory. Checking to make sure everything works.  Next pull out your list of code hacks that were made to the old Moodle version, which need to be added to the new version (sometimes new versions have features that eliminate the need for hacks or non-standard modules).
-I am not sure about the control panel commands, I don't use them but then again I am not a site administrator except for a localhost.  Was going to change but will restrict myself to some links and see also additions for now :)--[[User:chris collman|chris collman]] 07:34, 29 October 2006 (CST)
+This page starts off by refereing to installing 1.6 (good) for more specific instructions.    I think the entire page needs to either be more generic with lots of links, and/or give general instructions as in a checklist.  There are too many types of Moodle installations to get specific.    How different are installs from updates?  --[[User:chris collman|chris collman]] 07:46, 29 October 2006 (CST)

Documentation

Talk:Upgrading: Difference between revisions

Revision as of 13:46, 29 October 2006

Notes --Chris collman 07:34, 29 October 2006 (CST)

What does the below line mean?