Skip to main content
Participant
September 2, 2026
Question

Copying Text Insets is Crashing in FM 2022

  • September 2, 2026
  • 8 replies
  • 32 views

Are there any known bugs? We are on the latest version of Framemaker. 2022. Actually see the problem with  17.0.8.853 and 17.0.9.866
Simplest way to reproduce the crash is to File → import → File (import by reference).
The select what has been imported in the Structure View and press Copy.
Framemaker crashes.
We make heavy use of text insets in our application using the FDK (have updated FDK to latest versions).  So this is a major problem for us.
Any information would be appreciated.
A technical note is we think the use of the clipboard in the creation of the text insets is part of the problem.

    8 replies

    Bob_Niland
    Community Expert
    Community Expert
    September 4, 2026

    I’m unable to get a crash, using unstructured FM 18.0.0.206

    Struc vs. unstruc aside, I can’t be sure I’m using the failing protocol, because the source file type (.fm vs. .txt) hasn’t been specified.

    And these options might come into play:
    ○Import By Reference or ○Copy Into Document
    Updating of Imported Text: ○Automatic ○Manual
    if from .fm
    ○Body Page Flow?
    ○Reformat?

    Insets can have peculiar and possibly undocumented data structures in them, in particular (as seen in MIF) “PgfLocked” & “TextInsetLocked”. I’ve seen PgfLocked hang around even when the inset is deleted. I’ve not tested to see what new issues might arise on copy&paste.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    September 2, 2026

    Might try testing it out in an Unstructured FM doc too. And of course, there’s a newer version of FM out now also.

    Participant
    September 2, 2026

    Yeah. New version of FM would be nice. We develop a plug-in and the target Fm is Fm2022
    It’s code that used to work in FM 2019.  
    More investigation required to see if we have broken this or Adobe have. 
    Thanks for the suggestions. I’ll try the Unstructured test but expect it to work and for our needs we really need some structure in the text inset.
    Cheers, Colin

    Jeff_Coatsworth
    Community Expert
    Community Expert
    September 2, 2026

    I suspect you’ve just crashed your clipboard - in your test, try inserting the text inset, then save the FM doc, then copy the text - did that crash it?

    Participant
    September 2, 2026

    Thanks.  I had tried that. Still crashes. Which suggests the document gets corrupted during the creation of the text inset. 
    We’re now investigating if the EDD is in play which I suspect it is.
    I’ll post a follow up message with more information when I have it.
    Appriectate the suggestions though.

    Participant
    September 2, 2026

    More information is that we have noticed that the document that the text inset is copied into is in play. Might be something in the EDD of that document. 

    Jeff_Coatsworth
    Community Expert
    Community Expert
    September 2, 2026

    So you’re using Structured FM? Why are you copying the imported text inset? Isn’t the point of using text insets is to avoid copy/pasting content all over your docs?

    Participant
    September 2, 2026

    Thanks for the answer. You are correct that copy insets won’t be a normal work flow. It was noticed preparing a test document where the tester required multiple text insets and attempted to copy them.