Nested Table Object Causes Tagged PDF Export Failure in Publisher

[Brian Matheson]

Hi All, I get a fail every time I try to export a specific afpub file to pdf, it fails. I had exported this file before, and since this file is based on a template, basically the same menu with different texts ( catering menus ), I tried with another menu, same file format, same export settings ( a preset for my website ), they work. It's only this file. I only changed text, not sure what else would cause the fail. It fails from the start actually. It gets to 100% in generating file size, but never shows the file size, nor a preview. If I hit export, it generates nothing on the progress bar. It works for a bit, then just says there was an error. I am at a loss at what to look for. All images are embedded, I have ICC profiles embedded as suggested to @Keya13. I'll try on my work laptop tomorrow, but I suspect it is linked to the update. Nothing else re.ally changed.

Any suggestions would be appreciated. I really don't want to re-write the whole menu. I uploaded the file in questions. Nothing proprietary or private. I put the menus up on my website for downloading.

Thanks, in advance

Packaged Meal Menu 2025.afpub

[Hangman]

Hi @Brian Matheson and welcome to the forums,

I'm assuming you are exporting using the PDF (digital - high quality), PDF (digital - small size) or PDF (for export) preset...

If so untick 'Tagged PDF' in the Advanced section of the PDF export Windows and the file will export without the error...

The export error is caused by your 'Mind Full of Food' PNG logo nested inside your Table. If you unnest it, the file will also export regardless of whether 'Tagged PDF' is ticked...

[Affinity Info Bot]

The issue "Object Nested Inside a Table Layer Will Error When Tagged PDF is Enabled" (REF: AF-5982) has been fixed by the developers in the latest beta build (2.6.2.3187). 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.