I submitted below as a bug because it has now happened to both me and my colleague. I have copied below the same information from my bug report.
Basic info: FM 9.0p.255, OS 64 bit, Windows 7
We have just upgraded to the new version and this is a serious thing if you don't keep backups! You will never know when it is going to disappear.
When working with a Framemaker document it is unexpectedly deleted with no reason from the computer/network - this includes the backup.
The user did not delete it and it was an active document. There are different instances where the document would disappear. Below is one example of the steps taken.
Steps to reproduce bug:
1. Opened FM file.
2. Saved as an MIF file.
3. Closed FM file
4. Opened MIF file.
5. Edited the color definitions.
5. Clicked save button to save the mif file back to the source fm file.
Error message says that the file with extension .fm does not exist or has an unexpected extension. The .lck file exists but the .fm and backup files are gone.
Luckily I had the mif file and could rename it to a .fm file in this instance to recover the document. My colleague lost all versions (.fm and backup).
Expected results: that you would be able to replace the old version that is still on the network or computer.
Are you running any type of CMS or version control software?
When you're saying that backup copies have disappeared, are you talking about automatically generated FM *.backup files?
Do you have timed saves turned ON?
But if you don't mess with the color definitions while doing this MIF-wash, does anything bad happen? If not, then the lesson for MIF-washing is, "Don't do any 'FM' changes while the file is still a MIF; wait and save it back as a .fm, then monkey with settings"
Hi Jeff and Art
In answer to your posts.
No CMS, no version control. Unstructured frame. Yes, the automatic backup FM files would disappear. And yes, I have the auto save and timed back up options both turned on.
Answer to the following post:
I was doing a lot of clean up and sometimes I did the color def clean up in the MIF file and sometimes in the FM file. I can't say for sure when the errors occurred but it happened a lot. I did look for a pattern but couldn't find anything concrete. At first I thought I was going too fast for the software, then that was not consistent. I tried a variety of methods to see if I could find a pattern.
This is not an answer, but I just want to point out one little thing.
When you open a mif file in FrameMaker and then try to save it, Frame displays the message that it cannot save the file in that format, whether the format selected is mif or fm. The key is that the default file name includes the .mif extension. If one deletes the .mif from the end of the file name, then FrameMaker will happily save it to the fm format. I bring this up because if you are working quickly, you may have misunderstood the message, assuming of course that this is the message you got.....but maybe you really did get the message your report.
Amanda, to add a little bit to Van's posting, FM9 definitely works differently than earlier versions when it's doing the Save and/or Save As step, so it could be that you and your colleagues are experiencing a side-effect from that change.
In previous versions it used to drive me NUTS that we had to manually change the file extension when doing the save / save as (change the .mif to .fm or vice versa). In FM 9 that no longer is necessary, because changing the dropdown menu "Save as type" will automatically change the filename extension shown just above.
Could it be that when you are saving the document you type in the full name ("example.fm") but then you don't notice that the "Save as Type" is still showing the "Document 9.0 .fm" selection, or vice versa, and FM gets confused?
Or perhaps are you clicking on Save while you're editing (I'm in the camp that does Ctl-s reflexively, compulsively, and with almost pathological abandon while working, it would take considerable effort to retrain myself out of it). If so, maybe FM is actually saving your .mif as .fm and in the process "silently" changing the file type, so that when you finally do your last "save", it thinks the file is the opposite type?
In FM 9 that no longer is necessary, because changing the dropdown menu "Save as type" will automatically change the filename extension shown just above.
Not quite Sheila.
If you Save As an fm file, you can change the dropdown to mif and the file name changes accordingly.
HOWEVER, if you Save As (or Save) a mif file, the dropdown defaults to fm. If you change the dropdown to fm, the file name remains the same. If you change the dropdown to mif, or course the file name does not change. BUT if you then change the dropdown to fm, the file name changes to .fm. Go figure.
Hence, when I save mif to fm, I have got in to the habit of just deleting the .mif and then saving as fm. Very inconsistent.
Hi Van. I didn't save my file this way and get the message you describe below. I just tried your method and see what you mean. My message was different and based on a different way of saving. Thanks for the info though!
And thanks to Sheila too. This was useful information but not how I was working. Just for the record, since we all like to document these things, this is what I did today and previously.
1. Opened the .fm file.
2. File>Save as .mif 9.0
3. Closed the .fm file (and if prompted, saved it)
4. Opened the .mif file.
5. Deleted some color defs as an experiment.
6. Clicked the save button.
7. Clicked in File name field at the end. Entered .fm (previously I also selected the .fm file from the list that displays..)
8. Clicked save>OK to overwrite the file.
9. Deleted the .mif file from my folder.
And of course, I didn't have problems today!
I have FrameMaker 10 and my colleagues and I are experiencing a similar problem. It happens very randomly, but when it happens it is when we update the book or when we try to print. Right now, we are getting around that issue by creating a copy of the entire FrameMaker file folder prior to updating/ generating. It's a work-around so we would appreciate a more concrete solution.
@Akari - your issue sounds more like a network issue than a FM one. Do you have sufficient rights to the network location where the FM files are? Do you experience disconnection issues with the drives?
Europe, Middle East and Africa