Note: You are currently viewing documentation for Moodle 2.3. Up-to-date documentation for the latest stable version is available here: Restoring file aliases.

Difference between revisions of "Restoring file aliases"

From MoodleDocs
m
m (small rewording)
 
Line 1: Line 1:
 
{{Reusing activities}}
 
{{Reusing activities}}
 
+
In Moodle 2.3 onwards, course and activity backup files can contain ''aliases'' i.e. special files that behave as a reference or a shortcut to another file. The referenced file can be an external file (such as a file stored in Dropbox) or a file stored in Moodle (such as a file in another activity or course or in a user's Private files area).
Since Moodle 2.3, course and activity backup files can contain ''aliases'' - i.e. special files that behave as a reference or a link to another file. The referenced file can be an external file (such as one stored at Dropbox) or a file stored in Moodle (such as a file in other activity/course or in some user's Private files area).
 
  
 
During the restore process, Moodle does its best to try and restore the aliases correctly. However, there are many factors involved, most notably:
 
During the restore process, Moodle does its best to try and restore the aliases correctly. However, there are many factors involved, most notably:
  
* Is the restore happening at the same site the backup comes from?
+
* Is the restore happening on the same site that the backup comes from?
* What repository type was used to create the alias in the original course? In other words, what is the location of the referenced file.
+
* What repository type was used to create the alias in the original course? In other words, what is the location of the referenced file?
 
* Is the referenced file an external file?
 
* Is the referenced file an external file?
 
* Does the backup file contain the referenced file and if so, is that file selected to be restored, too?
 
* Does the backup file contain the referenced file and if so, is that file selected to be restored, too?
  
In some situations, aliases just can't be restored safely and are skipped.
+
In some situations it's just not possible to restore aliases and so they are skipped.
  
 
The following flowchart documents the implemented behaviour.
 
The following flowchart documents the implemented behaviour.
Line 17: Line 16:
 
<br clear="all" />
 
<br clear="all" />
  
Note that this logic is applied whenever the restore process is executed. Apart from the obvious case of restoring an MBZ file, the backup and restore is also involved in
+
Note that this logic is applied whenever the restore process is executed, in other words in all the following situations:
 
 
* [[Import course data|importing course data]] from another course
 
* [[Course homepage#Editing elements on your course homepage|duplicating an activity]] in a course using the x2 icon
 
* deploying a community course via the [[Community finder block]]
 
 
 
==See also==
 
  
* MDL-33430
+
* [[Course restore]]
 +
* [[Activity restore]]
 +
* [[Import course data|Importing course data]] from another course
 +
* Cloning a resource or activity using the x2 icon
 +
* Restoring a course which has been downloaded from a hub via the [[Community finder block]]

Latest revision as of 15:14, 18 July 2012

In Moodle 2.3 onwards, course and activity backup files can contain aliases i.e. special files that behave as a reference or a shortcut to another file. The referenced file can be an external file (such as a file stored in Dropbox) or a file stored in Moodle (such as a file in another activity or course or in a user's Private files area).

During the restore process, Moodle does its best to try and restore the aliases correctly. However, there are many factors involved, most notably:

  • Is the restore happening on the same site that the backup comes from?
  • What repository type was used to create the alias in the original course? In other words, what is the location of the referenced file?
  • Is the referenced file an external file?
  • Does the backup file contain the referenced file and if so, is that file selected to be restored, too?

In some situations it's just not possible to restore aliases and so they are skipped.

The following flowchart documents the implemented behaviour.

File aliases restore flowchart


Note that this logic is applied whenever the restore process is executed, in other words in all the following situations: