Skip to main content
jaggedpeak
Inspiring
July 24, 2009
Question

(FM8p277) Crashes when saving first doc in book after changing conditional text display

  • July 24, 2009
  • 3 replies
  • 1808 views

That was a mouthful 🙂

Okay, this happens with any of the books that I work on --- it never happened with Frame 7.

I have a book containing several documents.

The documents contain several conditional text segments.

  1. Start new Framemaker session, open book, open all documents.
  2. Change conditional text display (from Show All to Show Selected, or vice-versa).
  3. From the book, choose Save All (or from the *first* document, choose Save). The following text appears in a 'FrameMaker dialog': "File <filename of first document>.fm has changed on the disk since you last opened or saved it. Someone else has probably modified the file. Do you want to save it anyway?
  4. Click OK. All of the files save properly. (If I had clicked Cancel, the first file would be skipped and all other files would save.)
  5. Change conditional text display again (note: this could even be for a different book at this point, I believe, but will have to verify).
  6. (Repeat step 3): The same text appears again in the dialog.
  7. Click OK. FrameMaker crashes while trying to save the first file. (If I had clicked Cancel, the first file would be skipped and all other files would save. However, if I attempt to save the first file afterward, FrameMaker still crashes.)

Anybody have any insight into this? Am I the only one this happens to? Argh 🙂

Thanks.

    This topic has been closed for replies.

    3 replies

    August 11, 2009

    Did you get an answer?

    I am having the same problem. After I toggle conditional text settings, Frame crashes upon attempted save of first file in the book.

    Please let me know if you have found a fix.

    me

    jaggedpeak
    Inspiring
    August 11, 2009

    Sorry, the only answers I got were on the forum and nothing worked

    That being said, at least now I know I'm not crazy! (Sorry it had to

    happen to you, though.)

    As it stands, I've been training myself to make sure that after the

    first time I toggle the settings, I do the save, and then make sure to

    save all, quit, and restart FrameMaker before I attempt another toggle.

    On the odd occasion that I don't do that and get the warning message, I

    select Cancel (which lets the rest of the files save), quit, restart,

    and then make sure I update the first document appropriately.

    All the while cursing and swearing, of course

    As an aside... if you find a solution, please let me know about it if

    you remember.

    Thanks.

    John

    August 12, 2009

    Here is a workaround:

    DO NOT use the book to toggle the CT settings.

    1. Use one of the files (I use the cover/1st file) to toggle the CT settings.
    2. Import those settings using the book (with all of the book files selected).

    The cover/1st file can be saved before or after the import of the CT settings.

    Let me know; I haven't had crashed since I quit using the book to toggle the CT settings.

    me

    July 24, 2009

    In your File > Preferences > Workgroup do you have "Enable group work" checked or unchecked?

    In File > Preferences  do you have "Network File Locking" checked or unchecked?

    jaggedpeak
    Inspiring
    July 24, 2009

    I've never played with those settings ;-)

    Enable workgroup functionality is checked

    • Check out = Ask
    • update from server = Always
    • update non-hypertext links = never
    • update hypertext links = never
    • check in links = always

    Network File Locking is selected

    Arnis Gubins
    Inspiring
    July 24, 2009

    Are you actually using a WebDAV server and checking your files in and out?

    If not, then turn off that function.

    Arnis Gubins
    Inspiring
    July 24, 2009

    Step #3 seems to be indicating that something funny is going on with the file, unless you actually are on a network and other users are getting acces to this file.

    As this seems to be happening only to the one file, have you tried saving the file to MIF and then opening the MIF and resaving it as the .fm binary (aka a MIF-wash)? This might get rid of any unwanted baggage or gremlins.

    jaggedpeak
    Inspiring
    July 24, 2009

    Thanks Arnis, but that didn't work :-)

    Additional info:

    • This happens with *any* book I work on.
    • The system is not on a network -- I am the only person working on the files.

    What fun :-)