Jump to content

Tables create pseudo-hyperlinks that override any hyperlinks inserted into text in cells


xholt25

Recommended Posts

Hi there,

I have come across this issue a lot. I will try to describe it as best as I can. I create a table, insert desired text in cells and hyperlink the text (to other pages in the document). Then I realize I need another column/row so I add it. Naturally, it's empty. I insert the text I want in the new cells and hyperlink the text. When I check the hyperlinks (right click -> Interactive -> edit hyperlink or go to hyperlink target) - they're correct. When I export the document (PDF), they lead to incorrect pages. I go back to the .afpub file, check the hyperlinks again - they're correct.

When I delete the text, type it in again and hyperlink it again, the same error occurs. When I right click the text, delete the hyperlink and insert it again, hyperlink it again, the same error occurs.

I have noticed that when I delete the text, right click in the empty cell - there's still a hyperlink. (I didn't leave any spaces or hidden characters there, the cell indeed is empty). So when I right click in the empty cell, NOW delete the hyperlink, insert the text and hyperlink it, it works when exported.

I never inserted the wrong hyperlinks in the newly added rows/columns. They are somehow generated on their own, linger in the cells and override the hyperlinks I put in with the text.

I have recreated the problem in the attached file.

I am using MacBook Air M2, 2023, Ventura 13.5

Bug_reporting.afpub

Link to comment
Share on other sites

Hi @xholt25,

Basically what appears to be happening is that when the new column is added it inherits the hyperlinks from the column to the right (since you can only insert new columns to the left), so where 8, 15, 22 and 29 link to pages 9, 16, 23 and 30 respectively, adding a column to the left of that particular column and inserting the dates 7, 14, 21 and 28, those dates inherit the hyperlinks from 8, 15, 22 and 29 and subsequently link to the wrong page.

The second issue is that when you then edit the inherited hyperlinks so they are correct because they are still 'linked' to the adjacent column it means where you've added 7, 14, 21 and 28, when you edit the inherited hyperlinks to 8, 15, 22 and 29, it's also updating the hyperlinks in the adjacent column to the same and now incorrect values, i.e., Column A and Column B are intrinsically (and incorrectly) linked so any changes made to the hyperlinks in the newly added Column A are being reflected in Column B.

This also means that deleting the inherited hyperlinks in the newly added column deletes the hyperlinks in the adjacent column resulting in you needing to re-add the hyperlinks for both columns to achieve the correct links.

This is clearly a bug... I'm unsure if this has been reported already but someone from the moderation team will be able to confirm and if not log it.

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Hi @Hangman,

I was going to add to the topic the exact same thing, because it took a lot of cleaning up last night and I noticed that too. The hyperlinks are the same as in the adjacent column and if you update those, it also updates the pseudo-link in the new column, despite the text being re-linked in the new column. To fix it it requires deleting the text in both columns, deleting the pseudo-hyperlinks in the new column (which also deletes hyperlinks in the original column) and the re-enter everything again.

I really hope this can be fixed because it causes a lot of back and forth for me as I like to use tables a lot. A LOT.

Have a great day,

Tereza

Link to comment
Share on other sites

Hi @xholt25,

One possible, though not ideal workaround until the bug is fixed is rather than inserting a new column, add a new column. This will of course add the column to the far right of the table, but it means you can then select the already hyperlinked columns, cut and paste them into the correct columns and then add your new entries in the now blank column.

Doing it that way maintains the already created hyperlinks without the pseudo-link and also means the newly added column is free from any existing hyperlinks, so it's a case of:

  • Add new column
  • Select existing columns
  • Cut and Paste into the correct columns
  • Add new text in the now blank column
  • Add hyperlinks to the newly added text

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Hi @Hangman,

I just tested this and at first I thought - great, that works! And it did.

I added (instead of inserting) one column and copied and pasted the hyperlinked content to move it to the right. Exported it, it worked fine.

Then I did it again, added one more column, copied and pasted the content to move it and dang. Cell A1 contains the inherited hyperlink which affects B1 as well. This time, it is only the one cell, though. So apparently, if I do this twice, a similar error occurs.

Funny enough, if I do the same for the third time, then the first columns is fine.

I can drop the replicated error file in here if you want me to.

My brain isn't braining anymore.

Link to comment
Share on other sites

Hi @xholt25,

This worked for me, i.e., adding a second column but by all means, drop the replicated error file and I'll take a look... 🤔

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

That's good to hear, hopefully, it at least provides a bit of a workaround for now and hopefully, we'll see a bug fix soon... :)

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Thanks for brining this to our attention, I've informed the member of the team who originally dealt with this thread and have asked them to check this and update you here asap.

 

In the future, rather than tagging myself by default, I'd recommend checking the 'Follow' option in the top right of the thread - as selecting the number next to Follow or Following will show you the names of users who are actively following the thread, allowing you to tag the relevant moderator, if one is shown:

image.png

image.png

I hope this clears things up :)

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.