Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

Running Affinity Publisher 2.5.5 on macOS Sonoma (though I first noticed this bug in Publisher 2.5.3)

Two-way hyperlinks between reference numbers (in the text) and endnote bodies work as expected in Publisher and when an individual file is exported to PDF. However, when the file is part of a book (created with the Books Panel), endnote references and endnote bodies are missing all hyperlinks if the PDF is exported from the Books Panel. This is true whether all chapters or selected chapters or a single chapter is exported as PDF from the Books Panel.

Setup of my tests: Each chapter of book consists of two stories. The first story of each chapter contains the main text and concludes with the chapter’s endnotes; the second story, following directly after the endnotes, contains the references for that chapter. Endnotes are positioned “End of Story” and endnote numbering restarts each story. 

SimpleTestBook.zip

Posted

Originally discussed here: 

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop 1:  Windows 11 Pro 24H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 26.0, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1

Posted
1 hour ago, walt.farrell said:

Originally discussed here:

This is just the official bug report for the original post appearing in Affinity Support and Questions...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
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

Posted

Hi @Emolas,

This is already logged under AF-709, though this is possibly a regression since AF-709 was marked as fixed in v2.4.0.2175...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
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

Posted
5 hours ago, Hangman said:

Hi @Emolas,

This is already logged under AF-709, though this is possibly a regression since AF-709 was marked as fixed in v2.4.0.2175...

A couple of differences between what I’ve reported and AF-709:

1) AF-709 endnotes were set to “End of Book.” My endnotes are set to “End of Story.”

2) AF-709 reported endnote hyperlinks were present from reference number to the endnote, but no backlinks from endnote to reference number. I’m not getting any hyperlinks either direction — neither to nor from reference numbers, neither to nor from note bodies.

Unless there is something wrong with how I constructed my files, I think what I'm seeing may be a new bug — perhaps one that had been around for a while but not noticed?

Can anyone diagnose an error (by me) in the files I submitted?

emolas

Posted
3 minutes ago, Emolas said:

A couple of differences between what I’ve reported and AF-709:

I mentioned in your original post that this looks like a variation of AF-709...

So I do think this is technically a new bug from a bug-reporting perspective... You're definitely not doing anything wrong, this is simply a bug...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
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

  • 1 month later...
  • Staff
Posted

The issue "Books Panel- Exporting to PDF with Endnotes set to ‘End of Story’ fails to generate the reference hyperlinks" (REF: AF-4244) has been fixed by the developers in the latest beta build (2.6.0.2805). 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.

×
×
  • 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.