Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | File - Versions - Always save a version on closing is not working | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | Andrea Pescetti <pescetti> | ||||
Component: | save-export | Assignee: | Oliver-Rainer Wittmann <orw> | ||||
Status: | CLOSED FIXED | QA Contact: | |||||
Severity: | Normal | ||||||
Priority: | P3 | CC: | elish, fanyuzhen, hanya.runo, issues, jsc, oliver.brinzing, oooforum, orw, pedlino | ||||
Version: | 3.4.0 | Keywords: | regression | ||||
Target Milestone: | 4.1.1 | Flags: | jsc:
4.1.1_release_blocker+
|
||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | 4.0.1 | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Andrea Pescetti
2013-12-07 16:20:09 UTC
Confirmed with AOO410m1(Build:9750) - Rev. 1548193 2013-12-07_04:10:48 - Rev. 1548790 Debian . I was able to reproduce the described defect on Windows 7 using OOo 3.2.0 and OOo 3.3.0. It worked in OOo 2.2.0. Created attachment 82403 [details]
Patch to add FailOnWarning as valid parameter
If "Always save a version on closing" is checked on Versions dialog,
SID_SAVEDOC request is made with SID_DOCINFO_COMMENTS and
SID_FAIL_ON_WARNING in SfxObjectShell::PrepareClose method.
The SID_SAVEDOC request is processed in SfxObjectShell::ExecFile_Impl method and
GUIStoreModel method on SfxStoringHelper method is called.
SfxBaseModel::storeSelf method is called to store into the file but
I get IllegalArgumentException and store method is called to store alternatively.
So, no original arguments for saveas command lost.
The exception is raised because FailOnWarning parameter is not accepted in storeSelf method.
Storing a version from Versions dialog does not specify FailOnWarning parameter,
the same problem does not happen with it.
Thanks hanya, I applied (in my local copy) the patch to the current trunk. It works but not in all cases. Namely: - Manual "Save new version" button -> still works - Closing with unsaved changes -> The "Do you want to save your changes?" dialog appears, a new version is saved if I confirm (this is thus fixed by the patch) - Closing after making changes and saving them with CTRL+S -> The "Do you want to save your changes?" dialog does not appear (and this is normal), but I would expect a new version to be saved here too (it doesn't in 4.0.1 and it still doesn't with your patch) (In reply to Andrea Pescetti from comment #5) > - Closing after making changes and saving them with CTRL+S -> The "Do you > want to save your changes?" dialog does not appear (and this is normal), but > I would expect a new version to be saved here too (it doesn't in 4.0.1 and > it still doesn't with your patch) The option on the Versions dialog is creating new version on closing. And its help section says: > Always save version when closing > If you have made changes to your document, OpenOffice automatically saves a new > version when you close the document. > If you save the document manually, do not change the document after saving, > and then close, no new version will be created. It seems the behavior after the patch seems match with the description. But I see what you want to see. It would be an enhancement. (In reply to Andrea Pescetti from comment #5) > - Closing after making changes and saving them with CTRL+S -> The "Do you > want to save your changes?" dialog does not appear (and this is normal), but > I would expect a new version to be saved here too (it doesn't in 4.0.1 and > it still doesn't with your patch) Agree with hanya, this should be an enhancement. In the meantime, is it possible to integrate this patch for the next build? Nominating as 4.1.1 release blocker: simple patch by hanya available, works for me, fixes a regression. Should be reviewed and applied both to trunk and AOO410 for OpenOffice 4.1.1. Nominating as 4.1.1 release blocker: simple patch by hanya available, works for me, fixes a regression. Should be reviewed and applied both to trunk and AOO410 for OpenOffice 4.1.1. taking over to review the patch. Comment on attachment 82403 [details]
Patch to add FailOnWarning as valid parameter
patch looks fine.
@hanya: Do you want to commit the patch by yourself?
I have no objections to include the fix also in our planned 4.1.1 release. grant showstopper flag set target As Jürgen grants the release blocker status. As he wants to prepare new snapshots today I am taking the liberty to integrate the patch into trunk and branch AOO410 "orw" committed SVN revision 1608376 into trunk: 123812: <SfxBaseModel::storeSelf(..)> - accept arguement FailOnWarning in ord... "orw" committed SVN revision 1608384 into branches/AOO410: 123812: <SfxBaseModel::storeSelf(..)> - accept arguement FailOnWarning in ord... fixed on trunk and on branch AOO410 It's verified fixed in build AOO411m2(Build:9771) - Rev. 1608452 2014-07-07 15:29:02 (Mon, 07 Jul 2014) This bug is NOT fixed in RC1. If you reopen each Version you will notice that the manually saved Version 1 contains the same as Version 2 (i.e. Aaa bbb) when it should contain only aaa. Opening a Version does NOT open in Read Only mode. Strange, on trunk it's working fine AOO420m1(Build:9800) - Rev. 1614365 Verified fixed on AOO411m4(Build:9774) - Rev. 1614049 2014-07-28 17:55 - Linux x86_64 (In reply to Pedro from comment #20) > This bug is NOT fixed in RC1. If you reopen each Version you will notice > that the manually saved Version 1 contains the same as Version 2 (i.e. Aaa > bbb) when it should contain only aaa. I cannot reproduce this. > Opening a Version does NOT open in Read Only mode. Neither this, the version os opened read-ony. This bug is fixed also under Windows. A new Version is indeed created on close. Opening a new bug report with described problem (which makes Versions useless under Win7 x64) |