Moodle

Just checked this on 1.9.3+ (build 20081216) - and the backup/restore function still does not carry over the course forced theme, the number of weeks/topics, summary, nor the setting for "topics" vs. "weekly" course format.

My recommendation to get a better backup/restore would be to have a duplicate copy of all course settings carry over in the restore process so that it is not necessary to go into the new course after restore and reset the theme, format, number of weeks/topics, summary, or any other course settings.

PS, I wonder if this is related to the "Backup" or to the "restore" function. ? Does the backup function actually capture the course settings such as theme, # of topics, format, etc? If so, I guess it's a restore issue. If not, I guess it's a backup issue.

Hi Clark,

the number of topics, theme and son on (practically all course settings) are only restored if you are restoring to a NEW course. If the restore is happening into an existing course, then existing settings in that course have precedence and nothing will be overwritten.

Hi Eloy,

Thanks for the explanation.

The problem is that there are 3 choices:
new course
existing course, adding data to it
existing course,deleting it first.

As you've noted, the first choice will bring in the settings from the backup.
If I choose the last choice, it should ALSO bring in my settings included - because I am saying: delete it first: I don't care about anything in the already existing course, I want everythin from the backup: blocks, settings, everything.

Speaking for myself, and hopefully most all others who have a Moodle system that automatically creates new course shells every term of the year, into which either an administrator such as I, or a faculty member must move the content of their courses, this current function is insufficient and inefficient.

For example, if I go into a course for Fall 2008, and then our system has automatically set up a new blank course for Spring 2009, I as course manager need to either backup and restore, or import the course content into that new, already existing course, each term. Now, to do that, currently, my options are to use "import" (which doesn't bring in any HTML blocks I have added to my Fall course, and is generally messy - another issue for another ticket) or to backup my Fall course, then do a restore to the Spring course.

Now, currently the only way to get an exact duplicate into the Spring course, is by choosing "Existing course, deleting it first" - and even that, will not bring in my course settings. So this is extra work. But, if I am choosing "existing course, deleting it first" shouldn't it assume I don't want ANYTHING in the new course to carry over, and overwrite the settings from my backup?

I believe according to what you say above, that if one chooses "existing course adding data to it" - this function is correct, the new course's settings should remain. BUT - if one chooses "existing course, deleting it first" then all settings from the older course backup should move over into the newer course.

Doesn't this sound right?

thanks,
clark

Actually, I mean all settings, except dates.

(And I really like that in 1.9 even when I choose "existing course deleting it first" it keeps the enrolled users intact)

I updated the subject/title of this ticket to be very specific about only referring to a restore action that restores to "existing course, deleting it first"

sorry for so many updates - just wanted to put in specifics of the course settings I believe should carry over into the "existing course, deleting it first" - which I added above

Just to confirm - all these settings DO exist in a backup file - so this is a matter of the RESTORE to an "existing course, deleting it first", not bringing in the course settings:

<FORMAT>weeks</FORMAT>
<SHOWGRADES>1</SHOWGRADES>
<NEWSITEMS>5</NEWSITEMS>
<TEACHER>Teacher</TEACHER>
<TEACHERS>Teachers</TEACHERS>
<STUDENT>Student</STUDENT>
<STUDENTS>Students</STUDENTS>
<GUEST>0</GUEST>
<STARTDATE>1191384000</STARTDATE>
<NUMSECTIONS>50</NUMSECTIONS>
<MAXBYTES>524288000</MAXBYTES>
<SHOWREPORTS>0</SHOWREPORTS>
<GROUPMODE>0</GROUPMODE>
<GROUPMODEFORCE>0</GROUPMODEFORCE>
<DEFAULTGROUPINGID>0</DEFAULTGROUPINGID>
<LANG></LANG>
<THEME>bright_blue</THEME>

etc...