Moodle
  1. Moodle
  2. MDL-17917

META: Backup & restore capabilities improvements

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.9.4
    • Fix Version/s: None
    • Component/s: Backup
    • Labels:
      None
    • Difficulty:
      Moderate
    • Affected Branches:
      MOODLE_19_STABLE
    • Rank:
      1018

      Description

      Right now backup and restore is handled by very simple capabilities. That need to be changed to offer a higher degree of detail, controlling things like logs, users, roll dates... both in backup and restore (separate caps?).

      For now these have been talked:

      • ability to control backup of users.
      • ability to control backup of logs.
      • ability to control roll dates in restore (MDL-12922)

        Issue Links

          Activity

          Hide
          Dan Marsden added a comment -

          it would be nice if this could be extended slightly to control certain parts of user information in the backups

          eg to allow users to be backed up, but to remove "email" fields from backups - probably also the "password" field?

          Show
          Dan Marsden added a comment - it would be nice if this could be extended slightly to control certain parts of user information in the backups eg to allow users to be backed up, but to remove "email" fields from backups - probably also the "password" field?
          Hide
          Eloy Lafuente (stronk7) added a comment -

          Hi Dan,

          well... main problem with those fields is that they are required fields... so IMO it isn't possible to keep them out (unless for some sort of anonymous backup ). IMO, by default, teachers shouldn't be able to backup/restore users by default. Or/and we can seed the password or... not really sure. I agree we must address that in some way, 100%. But backupping without password or email... sounds "incomplete" to be functional.

          Ciao

          Show
          Eloy Lafuente (stronk7) added a comment - Hi Dan, well... main problem with those fields is that they are required fields... so IMO it isn't possible to keep them out (unless for some sort of anonymous backup ). IMO, by default, teachers shouldn't be able to backup/restore users by default. Or/and we can seed the password or... not really sure. I agree we must address that in some way, 100%. But backupping without password or email... sounds "incomplete" to be functional. Ciao
          Hide
          Dan Marsden added a comment -

          fair enough - I wrote a custom hack to remove password/e-mail and a couple of other fields for OU's incremental backups - they want to ship out course backups to people to install locally and want to keep forum posts etc, but don't want the local installs to contain "private" information..... hence the removal of password and e-mail. - might need to keep it as a hack instead of getting something in core to handle this.

          Show
          Dan Marsden added a comment - fair enough - I wrote a custom hack to remove password/e-mail and a couple of other fields for OU's incremental backups - they want to ship out course backups to people to install locally and want to keep forum posts etc, but don't want the local installs to contain "private" information..... hence the removal of password and e-mail. - might need to keep it as a hack instead of getting something in core to handle this.
          Hide
          Eloy Lafuente (stronk7) added a comment -

          This will completed in 1.9.8, with caps to control creation of users and so on... moving...

          Show
          Eloy Lafuente (stronk7) added a comment - This will completed in 1.9.8, with caps to control creation of users and so on... moving...
          Hide
          Michael de Raadt added a comment -

          Thanks for reporting this issue.

          We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported.

          If you believe that this issue is still relevant to current versions (2.3 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

          Michael d;

          4d6f6f646c6521

          Show
          Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.3 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d; 4d6f6f646c6521
          Hide
          Michael de Raadt added a comment -

          I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported.

          If you still believe this is an issue in supported versions, please report a new issue.

          Show
          Michael de Raadt added a comment - I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported. If you still believe this is an issue in supported versions, please report a new issue.

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: