You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, block_massaction is backing up and restoring the selected course modules one after another as a single activity backup and restore process. This raises an issue as soon as there are dependencies between the course modules (e. g. activities linked by mod_learningmap, access restrictions depending on completion of another activity etc.). It would be great if these dependencies could be preserved.
Most likely this could be realized by changing the way the activities are backed up and restored: Instead of backup-restore first one, then backup-restore second one etc. all activities should be backed up at once. Unfortuantely, I'm not very experienced with the backup API and I could not find low level documentation about it. So I welcome any examples/hints or - even better - pull requests :-)
The text was updated successfully, but these errors were encountered:
Currently, block_massaction is backing up and restoring the selected course modules one after another as a single activity backup and restore process. This raises an issue as soon as there are dependencies between the course modules (e. g. activities linked by mod_learningmap, access restrictions depending on completion of another activity etc.). It would be great if these dependencies could be preserved.
Most likely this could be realized by changing the way the activities are backed up and restored: Instead of backup-restore first one, then backup-restore second one etc. all activities should be backed up at once. Unfortuantely, I'm not very experienced with the backup API and I could not find low level documentation about it. So I welcome any examples/hints or - even better - pull requests :-)
The text was updated successfully, but these errors were encountered: