user to look for, at restore time, the best quiz
category to be used (i.e. the existing category with
the same stamp belonging to the same course or,
alternatively, belogns to other course but is published
and the user has editing rights).
It replaces the old-old stuff at restore code and
recent simplification that was producing some problems.
We'll use this number to determinate the code to be used
in quiz restore making these assumptions:
- backup_version < 2005043000, old quiz version.
- backup_version >=2005043000, new quiz version.
This will cover near every backup in the world, only
some backups generated last week will be wrong but I
think we can ignore them (we are in alpha stage).
to avoid moodlers filling their DBs (not always test servers!)
with non-consistent data.
Can be enabled by setting $CFG->enablerestorequiz = true;
(while working on it both Gustav's team and I, obviously this will be
removed once stabilished)
- If destination course is using 'simple' gradebook, restore nothing.
- If destination course has letters defined, don't restore backup letters.
- If one category exists in the course (by name) it's reused.
- Items belonging to non-restored modules are skipped.
- If users aren't restored, exceptions are skipped.
Test, test, test... :-)
- It's automatic. No setting for it. Does it sound ok?
- Any info related to non-exported modules is skipped.
- Any info related to non-exported users is skipped.
by the restore process. Such conversion is performed for
every backup file prior to 2005041100.
Wiki internal links are dinamically changed and then,
converted to Markdown.
quiz module backup and restore is now working (although some important
bugs remains in the module, creating strange versions and hidden questions).
Only some minor final things need to be finished to be 1.5 ready! B-)
some important bugs. Now everything seems to work properly with
lessons and backup/restore.
Only 1 pending change: Should the answer->grade field in old backups
go to the new score field??????
"PROG" (progress) because I haven't been able to reproduce the load
of binary data directly to DB reported by some moodlers in forums.
I've created bug 2634 to see if somebody can point me in the correct
direction to reproduce it.
