Jump to content
You must now use your email address to sign in [click for more info] ×

Cross-reference broken when object pinned above its target


Recommended Posts

This is a regression from 2.2.1 but easily worked around by updating all cross-references.

If you paste an object inline anywhere above the target of a cross-reference, the xref will become outdated and its value will be assigned to the xref below it. This test doc has xrefs to TOC anchors, a manual anchor, and to a paragraph, and they're all impacted the same way.

I don't know if 2.3 documents are supposed to be able to open in 2.2.1 but opening this doc in 2.2.1 will result in blank values for the cross-references so something has changed.

test.afpub

 

 

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.0 for macOS Sonoma 14.3.1, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

  • 3 weeks later...

FYI for those struggling with this bug, there is a workaround. For example, I had a cross-reference to an anchor at the top of a page but the xref returned the paragraph body of the preceding paragraph. There weren't even any inline objects on that page but I assume the trigger for this bug is an inline object anywhere in the story before the anchor.

The workaround is to add a page break before the anchor.

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.0 for macOS Sonoma 14.3.1, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

  • Staff

The issue "Cross references need updating when objects pasted inline above target" (REF: AF-959) has been fixed by the developers in internal build "2.3.0.2139".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.