Closed mbjones closed 6 years ago
Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2013-02-04T21:06:00Z
Since Morpho only ever "knows" how to save the current version of EML, we should not allow users to save the package unless it has been updated. Perhaps the dialogs need to be updated to reflect this policy, but it sounds like it works as we'd expect it to.
Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-02-04T22:32:12Z
Hrrm, I couldn't reproduce the bug any more. I opened an eml 2.0.1 on the network location without any modification, then saved it locally. The local copy is still eml 2.0.1. I tried the couple times, every time is the same.
Since the scenario just like copying a network one to the local, it is not necessary to upgrade the eml version. However, ben, if you want to force the update, you may create another bug. I am just closing this one.
Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2013-02-04T22:35:41Z
Oh, I misunderstood when I first read this.
Yes, you should be able to copy an old EML 2.0.1 file from the network to the local store without upgrading it to EML 2.1.1. But doing pretty much anything else with this file after that requires upgrading it to the latest version.
No new bug needed and thanks for closing this.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:51Z
Original Bugzilla ID was 5846
Author Name: Jing Tao (Jing Tao) Original Redmine Issue: 5846, https://projects.ecoinformatics.org/ecoinfo/issues/5846 Original Date: 2013-02-04 Original Assignee: Jing Tao
I found if use want to save an old version locally, actually the saving upgraded the eml version.
Open the document and you will find it is eml 2.1.1 after the saving.