Hyperlink problem with Publisher 1 file in Publisher 2

[Sascha M]

Hi Affinity team,

 

I use Affinity on an iMac with MacOS 15.3.2. I’m working with a complex, heavily hyperlinked journal file originally built in Publisher 1. In Publisher 1, when I select an object and choose Edit Hyperlink, it correctly displays the current hyperlink target (e.g., an anchor), and I can adjust it if needed.

 

However, when I open the exact same file in Publisher 2, using the same workflow:

• The Edit Hyperlink dialog shows only a generic target placeholder (first anchor in the list) instead of the actual destination.

• The hyperlinks themselves still work correctly when clicked — they’re not broken — but I can’t view or verify their destinations anymore.

• This makes it impossible to quality-check or adjust links in Publisher 2, which is critical in a document with 10,000+ hyperlinks created via master pages.

 

This seems like a regression from Publisher 1, and it makes Publisher 2 currently unusable for my production workflow.

 

I’d be grateful if you could confirm whether this is a known issue, and whether a fix is planned. I’d love to migrate to Publisher 2 fully — but this bug is currently a blocker.

 

Best,

Sascha 

Edited April 8 by Sascha M

[walt.farrell]

@Sascha M: Please confirm which release of Publisher you are running. There was a bug logged against V2 which sounds very similar (AF-1647) but it was fixed in 2.5, so unless you're running an older release either you've found a different problem, or the bug has returned somehow. I will try to reproduce this later (as I was able to for that earlier bug) but I can't try it right now.

Out of curiosity: If you create a file with a similar setup in V2 (rather than starting with a V1 file) can you reproduce the issue in the new file? 

In any case, I discovered a workaround in one of the earlier bug discussions which may help. I found that when Edit Hyperlink in the Hyperlinks panel shows the first anchor in the anchor list I could then right-click on the Hyperlink in the text and choose "Go to Hyperlink Target" and that would put the cursor at the correct anchor in the panel. Perhaps that will work for you, too.

[Sascha M]

Hey Walt, thanks for your reply! 

I am running Publisher 2.6.2 - I've just checked again (as I have done repeatedly over the past few releases) and the problem still persists. 
About your workaround, yes I've tried that and it works, however since I have to change a few hundred hyperlinks for the new edition of this journal (it's a calendar of sorts), this is not a solution for me. I need to be able to see at a glance where the hyperlink points now, and be able to change it to the new target. 

Thank you for looking into it! I'll try setting up a similar file too so we can compare results. 

Thanks again! 
Alexandra

[Sascha M]

I just created this file in V1.10.8, and it has this problem. 

Hyperlink-Test.afpub

[Sascha M]

I just did what you suggested, and yes the problem is the same in a file created in V2. 

Hyperlink-Test_V2.afpub

[walt.farrell]

Thanks for the files and added info, @Sascha M. I'll try to look into this later, and they should help the Serif team, too.

[NathanC]

Looks like this was fixed for Text Hyperlinks in AF-1647, but other objects such as quick shapes the 'Edit' interface defaults the field to the first anchor incorrectly, I'll get this logged with the developers.

[Sascha M]

Only just saw your reply Nathan, thank you very much! 

[Sascha M]

On 4/11/2025 at 2:08 PM, NathanC said:

Looks like this was fixed for Text Hyperlinks in AF-1647, but other objects such as quick shapes the 'Edit' interface defaults the field to the first anchor incorrectly, I'll get this logged with the developers.

Just installed the update and was gutted to see the bug is still there and I still can't use V2 ... any idea when it will be fixed? 

[Affinity Info Bot]

The issue "Edit Hyperlink- All Hyperlinks default to first in list if the hyperlink has been inserted on a shape" (REF: AF-6660) has been fixed by the developers in the latest beta build (2.6.4.3439). The fix 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 @Affinity Info Bot to notify us.