Closed mbjones closed 6 years ago
Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-02-19T23:56:49Z
In the RevisionUpdater class, there is structure to keep the revisions. We didn't reset it after upgrading a profile. After reseting it, the issue was fixed.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:58Z
Original Bugzilla ID was 5871
Author Name: Jing Tao (Jing Tao) Original Redmine Issue: 5871, https://projects.ecoinformatics.org/ecoinfo/issues/5871 Original Date: 2013-02-19 Original Assignee: Jing Tao
A Revision Manager in Morpho 2.0 manages the data objects in a single profile. So every profile has a Revision Manager.
However, after upgrading from Morpho 1.x to Morpho 2.0, a Revision Manager may contain the objects from the other profiles.
For example, Morpho 1.x has two profiles - A and B. After the upgrading, the RevisionManager of the profile A only has the data objects in the profile A. This is correct behavior. However, the Revision Manager of the profile B has not only the objects in the profile B but also the objects in the profile A. This is not correct.