Project

General

Profile

Bug #5809

Default save behavior to always include local store

Added by ben leinfelder over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Category:
morpho - general
Target version:
Start date:
01/24/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5809

Description

Currently you can opt to save your datapackage changes to either LOCAL, NETWORK, or BOTH. This means you can make changes to a package then opt to save them only to the NETWORK. This can leave your local store a version behind and I don't undersand the usecase for that.

I am proposing that we always save changes locally (if local does not already have the latest version).

I started thinking about this because of a related bug that displayed different local and network revisions simultaneously (#5805). I think we should still try to address that bug, but I'm not exactly sure how to guarantee it will not continue to be a problem especially if we maintain distinct revision histories for local and network content. (This may qualify as yet another bug for discussion).

morpho_force_save_local.png (30.4 KB) morpho_force_save_local.png ben leinfelder, 02/18/2013 12:40 PM

Related issues

Blocked by Morpho - Bug #5805: Local and Network revisions show at same time in search resultsIn Progress01/23/2013

History

#1 Updated by ben leinfelder over 7 years ago

Does this effectively communicate that Local saving is required?

#2 Updated by Redmine Admin about 7 years ago

Original Bugzilla ID was 5809

Also available in: Atom PDF