I am running FrameMaker 2015 and cleaning up conditional tags. FrameMaker keeps closing on me when I am doing this. Any thoughts? And do I have to delete each tag individually in the book or can I do it globally in the files in the book? Thank you, This is the message I get when I do get one. Sometimes it just closes
I can't address the primary part of your question—why is FrameMaker crashing as you delete condition tags—that's a question for Adobe.
But as for deleting condition tags: Fm is great at copying formatting (including condition tags) from one file to another and updating their properties the same way but it does not have a global delete formatting function. Without a third party plug-in, you are limited to deleting formatting from one file a time, whether or not it is in a book.
One such plug-in is described here:
Yes, this is a highly irritating bug. We have lived with it for years. I don't know of a workaround.
First: Do you have the latest update? The current version is 184.108.40.2066.
When you encounter this regularly, please add a bug report in the Adobe Tracker!
Of course FrameMaker should not crash, when you delete conditions! Adobe fixes especially bugs which crash FrameMaker! When you want that FrameMaker does not crash, then make Adobe aware of your problem.
Additionally you can send a mail (possibly with your bug number) to the support: email@example.com
Surely Frame 220.127.116.116 is FrameMaker 2019, and not FrameMaker 2015 which is what we are discussing here?
Yes. My version is FM 2019.
I delete conditions only very, very rarely, therefore I do not encounter your problem.
When I experiment with a new file, everything works.
This is how to reproduce the bug:
Open a book with multiple files, that all have conditions. Open the Conditional Tags pod/tab. Use the Select dropdown to choose the entire book to operate on. Select a condition in the list, and delete it. This triggers the bug. Does that work in Frame 2019?
Thank you very much! This bug is still not fixed in FM 2019.
I will write a report in Adobe tracker.
The tracker issue has been marked fixed and will be available in the upcoming Update 2.
Don't forget to go vote for the bug report Winfried entered.