Restoring file aliases: Difference between revisions
From MoodleDocs
David Mudrak (talk | contribs) (Added the info and the flowchart) |
Helen Foster (talk | contribs) m (small rewording) |
||
| (4 intermediate revisions by one other user not shown) | |||
| 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). | |||
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. | |||
[[Image:file-aliases-restore-flowchart.png|left|thumb|File aliases restore flowchart]] | [[Image:file-aliases-restore-flowchart.png|left|thumb|File aliases restore flowchart]] | ||
<br clear="all" /> | <br clear="all" /> | ||
Note that this logic is applied whenever the restore process is executed | Note that this logic is applied whenever the restore process is executed, in other words in all the following situations: | ||
* | * [[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.
Note that this logic is applied whenever the restore process is executed, in other words in all the following situations:
- Course restore
- Activity restore
- 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
