🐛 [BUG] - Packages/modules are not considered in project backups

[OliverKunc]

Summary

Activation (and probably also deactivation) of "Project Modules" are ignored by the backup functionality. Also, changes to un-backuped modules (aka packages) are ignored when restoring backups.

Expected Behaviour

The backup functionality should store and restore the entire project state including the state of activeness of modules and their contents.

Reproduction steps

1. Backup a project
2. Activate a module
3. Make some changes to that module, save the project
4. Restore the backup

Now the module, which was activated post-backup, is not only still active, but it even contains the post-backup changes.

GTlab environment

GTlab Version: 2.0.6

OS

Windows

[rainman110]

Thanks for Posting the issue. Lets separate the two case:

• Case 1: Backup contains a Package XXX, which the project does not have anymore:
  • When restoring the project from the backup, the package XXX is indeed missing from the project tree. BUG!
  • When restarting GTlab and loading the project, the package XXX is back.
  • So it seems, that the package information are not correctly restored in memory, but it is fixed after a restart.

[rainman110]

• Case 2: Project contains a Package YYY, which the backup does not contain:
  • Expected behavior: After backup restore, YYY removed from the project tree
  • Actual behaviour: YYY is still in the tree after restore. A GTlab restart fixes the problem

[OliverKunc]

• Additional problem with case 2:
  • Project contains a Package YYY, which the backup does not contain, and the user saves changes to YYY, e.g. creates new YYY.childObject.
  • After backup restore, GTlab restart, and activation of Package YYY, YYY.childObject is still there.
  • Expected behavior: YYY.childObject should not persist after backup restore.