Issue 51352 - Empty storage might be lost.
Summary: Empty storage might be lost.
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: mikhail.voytenko
QA Contact: issues@api
URL:
Keywords:
: 51349 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-06-29 10:37 UTC by mikhail.voytenko
Modified: 2013-02-24 21:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mikhail.voytenko 2005-06-29 10:37:44 UTC 
If a new storage is created, copied to another location and then commited, the
commit does not really take place. The fix is to set the new storage to modified
on creation.

The scenario is not used currently by the office code and seems to be very
specific, thus the target is set to "OOo Later" for now.
Comment 1 mikhail.voytenko 2005-06-30 12:45:37 UTC 
Changing the target.
Comment 2 christianjunker 2005-07-20 17:20:33 UTC 
*** Issue 51349 has been marked as a duplicate of this issue. ***
Comment 3 mikhail.voytenko 2005-08-02 10:33:57 UTC 
Fixed.
Comment 4 mikhail.voytenko 2005-08-18 10:42:59 UTC 
Verified.
Comment 5 mikhail.voytenko 2007-01-02 10:18:02 UTC 
.