Linking text frames subsequently

[gn53]

If I subsequently correct interrupted text flow by linking text frames from one page to the next, all subsequent "free-moving" pinned photos and text boxes of the following pages are distorted and placed at the outer edge of the pages. Even the Undo-command  "Link text frame" cannot restore the previous state.

This behaviour already existed in version 1 of Affinity Publisher. Unfortunately, I could not see any improvements in version 2.

With several hundreds of following pages, double-clicking to adjust and de-skew the images can be very time-consuming.

Are there any improvements planned for version 2. At the moment I see no need to upgrade to Verson 2 ?

PS: Please see attached afpub and try to link text frame from page 3 to page 4

--- MacOS 12.6.1, iMac2020, 40 GB RAM, 8 Core i7 - Affinity Publisher 2.0.0 Trial version ---

Linking text frames.afpub

[MikeTO]

I see the same thing with your document and it's a particularly bad bug because undo won't restore it to the original state, you have to close and re-open the document.

[iaing]

Yes same here, not come across that before, so just tried setting up a document in that way from scratch in v2 and does exactly the same with my content.

[gn53]

On 11/13/2022 at 6:29 PM, MikeTO said:

I see the same thing with your document and it's a particularly bad bug because undo won't restore it to the original state, you have to close and re-open the document.

The undo-bug is not my problem. My problem is the bug when I link textboxes after changes in the document. I have already reported this error in AP1. Now I am working with the trial version of AP2 and the error is still there. To make a decision if I upgrade to AP2 I want to know if this error will be fixed.

A subsequent change with insertion of chapters in an existing Publisher document destroys all subsequent pinned images and text boxes by distortion and displacement when re-linking text boxes.

[walt.farrell]

4 hours ago, gn53 said:

To make a decision if I upgrade to AP2 I want to know if this error will be fixed.

That is, unfortunately, something that Serif does not tell us.

It is at least acknowledged as a bug, as you can see from the bug tag below the topic title: afb-6866.

Beyond that, the Developers decide the priority of bugs and which bugs to fix, in what order, and even the QA and Support teams generally do not know when a bug will be fixed.

[gn53]

18 hours ago, walt.farrell said:

It is at least acknowledged as a bug, as you can see from the bug tag below the topic title: afb-6866.

Thank you very much! I did not know that. The abbreviation "afb" probably stands for affinity bug ...

 

18 hours ago, walt.farrell said:

Beyond that, the Developers decide the priority of bugs and which bugs to fix, in what order, and even the QA and Support teams generally do not know when a bug will be fixed.

I will definitely wait with an upgrade to version 2 until this error is fixed. Thanks again!