JimWelch

If you don't click "Fix" then it works. I always hit Ignore, because I know my TOC is updated.

H1s and H2s are just text. There's no anchors in the entire document. The only hyperlinks are on the Credits page (page 2). The very first H1 does link to page 4, so I think there's some variable that is default to the first use of that page number.

Yes. The bad links always went to TOC page + 1 (page 4 in my doc, page 3 is TOC). All of the headings had the exact same style and properties. There's nothing different about the good vs bad headers (other than the bad ones linking to pg 4). I've even deleted the TOC, recreated it, so everything is the exact same, and still same problems. I've also deleted my entire TOC, the containing frame, and then recreated the frame and TOC and still have the problem. I guess I just need to do my TOC hyperlinks by hand from now on...

I went through the TOC and re-hyperlinked all of the H1s by hand. Now when I export to PDF, everything is correct. However, I'm going to have to redo the TOC H1 hyperlinks every single time I add new content.

Okay. I'm looking at the PDFlib log file and I can see the problem. It's pretty clear and now that I'm looking here, I realize that not only are the page numbers wrong but the entire line is wrong. Sometimes the Section Name links to page 4 (wrong page) and the number is correct, other times the Section name is correct and the page number link is wrong, and sometimes both are wrong. Here's the pdflib.log output: [0] PDF_setfont(p_0x000002AF80CBBFD0, 0, 15.221038) PDF_fit_textline(p_0x000002AF80CBBFD0, "à¥\213à¥\217à¥\223", /*c*/9, 1883.539918, -637.890519, "xadvancelist={5.601342 6.073194 6.819025 }") PDF_restore(p_0x000002AF80CBBFD0) PDF_restore(p_0x000002AF80CBBFD0) PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [4] PDF_create_annotation(p_0x000002AF80CBBFD0, 68.868000, 681.140060, 294.102000, 720.856860, "link", "action {activate 4} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 5}") [5] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.356400, 681.140060, 294.102000, 702.020060, "link", "action {activate 5} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [6] PDF_create_annotation(p_0x000002AF80CBBFD0, 294.102000, 681.140060, 294.102000, 702.020060, "link", "action {activate 6} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 5}") [7] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.892039, 667.892549, 294.102000, 682.104463, "link", "action {activate 7} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 5}") [8] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.892039, 655.904268, 294.102000, 670.116182, "link", "action {activate 8} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [9] PDF_create_annotation(p_0x000002AF80CBBFD0, 68.868000, 638.326697, 287.780400, 659.206697, "link", "action {activate 9} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 7}") [10] PDF_create_annotation(p_0x000002AF80CBBFD0, 287.780400, 638.326697, 294.102000, 659.206697, "link", "action {activate 10} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [11] PDF_create_annotation(p_0x000002AF80CBBFD0, 68.868000, 619.489897, 294.102000, 659.206697, "link", "action {activate 11} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 7}") [12] PDF_create_annotation(p_0x000002AF80CBBFD0, 287.780400, 619.489897, 294.102000, 640.369897, "link", "action {activate 12} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [13] PDF_create_annotation(p_0x000002AF80CBBFD0, 294.102000, 619.489897, 294.102000, 640.369897, "link", "action {activate 13} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 7}") [14] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.913523, 606.242387, 294.102000, 620.454301, "link", "action {activate 14} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [15] PDF_create_annotation(p_0x000002AF80CBBFD0, 68.868000, 588.664816, 288.140400, 609.544816, "link", "action {activate 15} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 8}") [16] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.140400, 588.664816, 294.102000, 609.544816, "link", "action {activate 16} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 4}") [17] PDF_create_annotation(p_0x000002AF80CBBFD0, 294.102000, 588.664816, 294.102000, 609.544816, "link", "action {activate 17} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 8}") [18] PDF_create_annotation(p_0x000002AF80CBBFD0, 288.902781, 575.417305, 294.102000, 589.629219, "link", "action {activate 18} borderstyle=solid linewidth=0") PDF_create_action(p_0x000002AF80CBBFD0, "GoTo", "destination {retain page 8}") [19] Look at how the "GoTo", "destination {retain page 4}" repeats over and over. These are the wrong hyperlinks. It's changing every other link to page 4. The first GoTo is the text, the next one is the page number. So link [0] goes to page 4 (correct), then [4] goes to page 5 (correct), then [5] goes to page 4 again (wrong), then [6] goes to page 5 (correct), then [7] goes to page 5 (correct), then [8] goes to page 4 (wrong). Something in the code is changing almost every other H1 link to page 4. Oddly, all of the H2 links work fine. But I have some H1s without a H2 - otherwise, I could just remove page numbers on H1s. It's like a variable in their loop isn't getting incremented correctly when they are creating those PDF actions. Also, further investigation reveals that the hyperlink is correct within the document. When I select the problem text (such as "88" in the OP post), then click Text->Interactive->Hyperlink, it says "Page 88". So the hyperlink in the afpub TOC is correct, it's only getting exported to PDF incorrectly.

Update - There's actually more bad hyperlinks in TOC now after I did the Save As, delete TOC, recreate TOC, etc.

Save As didn't help. I did a Save As, exported still problem. I deleted the TOC completely, did another Save As, added a new TOC, exported, still same problem. The file size did get smaller (slightly) after the Save As, so that did clear something out. I've even deleted the entire text frame concerning one of the items and then recreated it. And it still has a problem.

Yes. I manually edited the problem links in Acrobat Pro (see screenshot in opening post for Acrobat pro hyperlink editor screenshot). I haven't tried a "Save As". What would that change? I'll try that later tonight.

I tried deleting the TOC, deleting the section header that causes problems, then recreating the TOC (without the bad hyperlink section), adding back in the section, then updating the TOC, and it's still not working correctly. I'm not sure how or why the TOC displays the correct page number "header....##" but the hyperlink goes to a different page? That seems strange to me. It feels like if one piece of code was broken, then the other piece should also be broken.

Actually, the incorrect hyperlinks always go to page 4 (page 3 is where TOC is at) - regardless of whatever number (88, 89, 115, 125, etc.) is printed next to the TOC header. None of those were ever on page 4. I'll try deleting and recreating the TOC and deleting and recreating the headers as well. I've changed and checked the text styles on the problem headers and that didn't seem to change anything. It prints the correct page number! So why doesn't the TOC use the same page number that it prints for the hyperlinks?

Yep. I'm not sure that every h1 has one h2 after it. I agree this is the best way, but I'm not sure it will work. I'll try that out later today to at least remove that pop-up. Yep. I was waiting until QA popped in, then I can upload it to Dropbox (it's a huge file, with 350+ images, so even without images I think it exceeds file upload size for the forum). However, I still hope Affinity fixes the problem of the actual page links not working

I had the same problem. I had overflow text in a text frame in my Master page outside my doc bounds on a layer that was turned off. It took me weeks to find that.

I've been using PDFtk to script the same process. I keep my headings, indent levels, and page numbers in a text file and then use batch scripts to automate the insertion of those bookmarks into my final PDF. I just noticed this yesterday. It's one of those "assumptions" that I thought would "just work." I know I've clicked on several to make sure the TOC worked, but I never went through and clicked on every single TOC item to make sure every single one worked. After recreating the same PDF 3 or 4 times to check the TOC (it takes > 5 minute to create), it's always the same 5 (IIRC) sections and page numbers that are invalid. However, there's nothing unique about those 5 sections. There's no page breaks before/near/around (even in the same text frame) as those headers (unlike the bug with the hyperlink anchors in PDF). Thanks. I'll see if I can make the col break as a paragraph work in the TOC. The only problem is when I add (or remove) a new section, then that col break will need to be changed every time.

Happens frequently with me also.

I agree. There should be a way to "find" or locate the overflow text frames. If we get a warning telling us that we have overflowing text, it should let us locate it so it's easier to find.

I have a fairly large table of contents (2 column, 1 page) with maybe ~100 entries (20 chapters, the rest level 2) in a PDF that has 164 pages. About 95% of the hyperlinks in the TOC in the generated PDF go to the correct page. However, there's a handful that go to the next page (TOC page + 1) instead of page 86 or 87 or whatever it says in the TOC. This works for almost everything and requires me to click on each specific link to make sure it's valid or not. This is another deal breaker (besides the ability to generate PDF bookmarks from TOC or header styles or whatever) for digital publishers - when the TOC hyperlinks doesn't work! And there's no bookmarks! So users reading large documents will get a subpar PDF experience! Also, what's also annoying is that I need to insert a column break to prevent orphan chapter/section (the last entry on col 1 is a chapter title with it's subsections at top of col 2, so I insert a col break to make it look correct), then I get the pop-up saying "TOC has changed" on every.single.export. Even though nothing has change. I just added a col break inside of the TOC. Edit: Added image from Acrobat Pro that shows the hyperlink properties. This hyperlink property is for the chapter "Sembia" and page "88" link below it, but it says Page 4 (TOC is on Page 3).

New update on this. This started happening again (on brand new computer, happened on old laptop too). It happened. Then I reopened, went to a different page and then it happened again. And again. And again. And again. Then when I opened the doc, Affinity crashed before the doc even loaded. Then I waited 5 minutes, then Affinity opened it fine. All the time, I was making no changes to the doc. I was just browsing pages (very slowly, like waiting more than 30 seconds on each page before going to next page). It generated 3 crash dmp files out of the ~10+ crashes. 134bb650-c01d-47ce-b4a3-5cc535d5a056.zip

I think its a different file. This has only happened twice so far.

Perfect. Thank you. I spent a few minutes searching for that, but I couldn't find it.

Can you add text conversions to the menu? You would select text and then click a menu choice to change the text: Examples: "Convert to lower case" "Convert to UPPER case" "Convert to Proper case" "Convert to sentence case" (Other applications have a full list and I can't remember all of the various methods.) This is different from using the Small Caps, Caps, etc. text styles which are style changes versus actually changing the text.

Can a "word count" be added to the fields window? Thanks

It stays this way until I close and reopen the document.

Yes. (images range from 100k to 2.5 mb) It feels like after you click 'Update' on the Resource Manager that the application rescans the entire document checking for other changed images. However, when you simply click 'replace' and select the same image, it doesn't rescan the document. thanks, Jim

Just crashed again and created a DMP file. Attached. 36e06285-d424-4e78-8688-6ab3df7d4ab5.dmp

Brand new computer specs Inspiron 3670 9th Gen Intel Core i5 9400 (6-Core, 9MB Cache, up to 4.1GHz with Intel Turbo Boost Technology) Windows 10 Home (64bit) English Intel UHD Graphics 630 with shared graphics memory 12GB, DDR4, 2666MHz Dual Storage (3.5' 1TB HDD+ M.2 128GB SSD) So far (I've only started working this morning with the new PC), it's crashed once while slowly scrolling through the large 165 page document which has 300+ image links. I haven't experienced any of the 'long save' problems in the last few hours.