Apache OpenOffice (AOO) Bugzilla – Issue 85044
No warning to save existing file when using Windows native Save dialog
Last modified: 2008-02-27 17:43:44 UTC
Not sure for version: I use SRC680_m241 If you saved with an existing filename, OOo don't display any warning and the file is replaced.
arielch -> oooforum: Can you tell me if this is the behavior * you are NOT using OOo dialog, but Windows dialog * if you enter the file name without extension, the old file gets overwritten * if you enter the file name AND the extension, you are asked if you wnat to overwrite the document To try with OOo dialogs, go to Tools-Options-OOo-General-Open/Save dialogs I think it only happens with Windows dialog, tested in 680m242
Changed summary because it happens on Windows when using Windows' native Save dialog. In fact, on Linux there is no option to use the system's dialog (there is no Tools - Options - OOo - General - Open/Save ).
this works for me, using Src680m241, windows system dialogs. What I did is: - create a new writer file - use "File - save as..." - browse to a directory where a document "kill_this.odt" exists - select "kill_this.odt", so that this becomes the file name to save the document - click save -> warning that file already exists appears - removefile extension, so that the filename is "kill_this" (.odt would be added by OOo) - click save -> warning appears that file already exists oooforum / arielch : can you please give a step-by-step instruction how to reproduce?
Now I use SRC680_m242 @ andreschnabel: Well I did like you except 2st step 1- create a new writer file and input some text 2- menu File > Save or Ctrl + S 3- browse to a directory where a document "kill_this.odt" exists 4-1 input "kill_this" and save -> no warning 4-2 input "kill_this.odt" and save -> NOW warning appears
I still cannot reproduce using m241 or OOH680m2. oooforum: in you initial post,you told you use m241 but you're not sure about this. Can you confirm that the issue exists in m241? This is important, as m242 is *not* going into OOo 2.4 (means, we have a little more time if this does not occure in m241). can you attach a screenshot of the file dialog with the selected path and filename ? If we can reproducethisproblemin OOo 2.4 codeline, I would consider this as a stopper - but as said, I cannot reproduce.
In my previous post, I confirm to use SRC680_m242. That's happen only if: - Saving a new document with "Save" menu or Ctrl + S - Input in "Filename" field with an existing file without extension Maybe difference with you: my Windows system is in french
Created attachment 50913 [details] Save dialog screenshot
I can confirm the behavior as described with the steps 1- create a new writer file and input some text 2- menu File > Save or Ctrl + S 3- browse to a directory where a document "kill_this.odt" exists 4-1 input "kill_this" and save -> no warning 4-2 input "kill_this.odt" and save -> NOW warning appears with Windows native save dialog; German SRC680m241 on German WinXP.
ok - I can confirm. The trick is,that you need to type the filename (I clicking on an existing file will give the warning). If you don't want to overwrite an existing file, it is normal to type the filename - so there is a real risk to loose existing files.
TM->AS: as talked about,...reassigned to you.
as: We've rolled back changes regarding "removing check box for AutoExtension" ... but for the internal OOo and the native windows file picker only. So the gnome file picker (where this feature was introduced first time) will stay alive with the new feature. as->kla: Please verify these task on cws "autoextension01". Note: you have to check some special variants of the SavAs dialog too ... as e.g. "File->Export" or "Export As PDF ...".
.
Check box for AutoExtension are back (integrated) All possible variants of Save as Dialog, esp. "File->Export"and "Export As PDF ...". checked by me and TM. Overwrite warning dialog works also fine. Also the gnome file piker (checked by TM). verified
@kla: that's mean it's fixed for the native windows file picker too?
*** Issue 85623 has been marked as a duplicate of this issue. ***
fixed im OOH680_m7 -> closed