
In Scribus Scripter, unlinkTextFrames("B") removes B from a linked story and connects its previous and next frames. For A → B → C, the documented resulting chain is A → C. It is not a command that simply cuts both links and leaves all three stories independent.
The Handling Text Frames API reference retained in Release 1.6.6 specifies this behavior. Use the function's contract rather than assuming that the graphical unlink command has the same interaction sequence.
Establish the current chain before editing it
For a hypothetical three-column story, record the actual frame names and reading order. A visual arrangement from left to right is not proof that the links follow that order.
Keep a retained document revision and inspect the source text before changing the chain. Decide whether the goal is to bypass a frame, create independent stories or move content elsewhere. Those goals require different outcomes.
Do not run an unlink operation merely because B is the selected object. The API takes a named frame, and an explicit name makes the intended target inspectable.
Remove the named frame from the flow
In a disposable document, the schematic operation is:
scribus.unlinkTextFrames("B")
The example frame name must be replaced with an actual text-frame name. The call has not been executed for this guide. The reference also warns that violated linking rules can raise ScribusException; an exception should be investigated rather than treated as successful unlinking.
After the call, inspect whether the previous frame now connects directly to the following frame. B's removal from the flow is a structural operation, not a promise about where every character will remain visually positioned.
Recalculate and inspect the surviving story
The same reference supplies layoutTextChain() for relayout. Refresh the remaining chain as appropriate, then inspect A and C and the new transition between them.
Compare the beginning, bypassed-region passage and final sentence with the retained source. Inspect B separately rather than assuming that its previous visible lines became an independent, fully preserved story.
If the intended operation was to make independent content, stop and plan that content transfer explicitly. Do not repeat unlink calls while relying on an unsupported expectation of automatic story splitting.
Accept structure and text separately
Require both the intended new connection and complete agreed text in the resulting layout. Check for overflow after bypassing a frame, since the available story space has changed.
The text-output completeness guide supplies general acceptance questions, with separate application controls. Retain the approved revision. This article describes a proposed structural check, not a performed script or guaranteed text redistribution.
Related tasks
- Why Does My Photoshop Batch Action Save Files Under the Same Name?
- Apply Data Set or Export Data Sets as Files? Preserve Your Photoshop Template
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
Sources and scope
- Handling Text Frames: unlinkTextFrames removes the named item from flow and connects its previous and next frames; unlinking B in A to B to C yields A to C.
This guide follows the official Scribus documentation retained in Release 1.6.6, consulted on October 23, 2026 (Asia/Shanghai). Historical interface illustrations and optional viewer behavior require confirmation in the actual installation. The proposed procedures and code have not been executed for this article.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.