Details
Task
Description
I was reviewing scheduled backup (to ask some questions in forums) when I've discovered that we need to verify that scheduled backup supports all the recent additions performed to Moodle:
- Roles
- Gradebook
- Groups
- ....
(each step in course backups should be executed from shceduled backups too)
Ciao 
Issue Links
| This issue will help resolve: | ||||
| MDL-12562 | Backup process generate big memory footprint and would stop when have huge number of users |
|
|
|
| MDL-6227 | Cron backup issues |
|
|
|
| This issue will be resolved by: | ||||
| MDL-13115 | Backup doesn't respect the users=none setting at all |
|
|
|
| This issue has a non-specific relationship to: | ||||
| MDL-13183 | Unify manual backup_execute() and scheduled_backup_course_execute() |
|
|
|
| This issue has been marked as being related by: | ||||
| MDL-13177 | Old sites can have $lesson->usegrademax while the correct is $lesson->usemaxgrade |
|
|
|
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
Just found MDL-13115 . Going to fight with that before anything else (reproducible since 18_STABLE).
Ciao
Done. Now both manual backup and scheduled backup generates an 100% equal moodle.xml. There were some missing parts and I've added some helper functions (used by both backups) to make them share the most possible code.
Note that, for Moodle 2.0, I've added MDL-13183 that will be a huge improvement about keeping both backups working with the same code and less prone to forget parts.
Ciao
moving to Yu!