Designer 2.6.0: Does not export to PDF

[bengrau]

Hello,

Designer does not export to PDF after updating to 2.6.0. The file came from an Ipad 2.5.7 (it does not export on the ipad as well).

There are no text frames of any kind in the document (only some vectors and some pictures).

Anybody has any ideas?

x

[Hangman]

Hi @bengrau,

Can you upload your Designer file so we can find out what is causing the export failure?

[AndreasBER]

Same problem here. Since the last update Designer will not export anymore and gets stuck while the preview is supposed to be generated. Last message is "Generating preview..., then nothing happens. However it's possible to cancel and return to the UI. I will attach the file without external elemnts to keep it small.

mv speisekarte digital getränke ohne tagesgerichte DE EN 20250410.afpub

[Hangman]

Hi @AndreasBER,

The file you've uploaded is a Publisher file... You reference Designer in your post. Did you mean Designer, or were you referring to Publisher?

Your file exports without issue here, but we don't have the images to test it with, so it could be one of the linked images causing the export problem... The file path to the images references Nextcloud. Are the linked images stored on a cloud drive, or is the file path a location on your internal hard drive?

[AndreasBER]

Sorry, I shouldn't have written this late at night. It is a Publisher file. I have made some additional tests this morning to produce a PDF file for our printers:

1. Neither Nextcloud nor local storage make a difference. My last test was run locally.

2. All resources are properly linked.

3. I tried to render to other formats like JPG and PNG and those are working

Only Export to PDF does not produce a preview or file, but can be canceled 

Please find the complete project included in the attachment 

 

ba mv.tif karte aussen 543x310 20250410.afpub

[Hangman]

Hi @AndreasBER,

Many thanks for the update and the additional files...

The export error is a known bug in 2.6.2, logged under AF-6294 caused by the Spelling language in the Character panel being shown as Unknown.

Selecting all the Frame Text using Select → Select Object → Frame Text and changing the spelling language from Unknown (German-DE-ref) to None will rectify the issue and allow the file to be exported...

I've done this for you in the attached version of the file... You may need to relink the graphics when opening the file, but you should find it now exports without issue...

karte aussen 543x310 20250410.afpub

[AndreasBER]

Thank you so much. You are my big time saver today. I was already worried I would have to rebuild the whole document. Export achieved sucessfully... 

[Hangman]

That's great to hear, I'm glad everything is working for you now... Hopefully, we'll see a fix for this issue soon...

[cjudebeg]

Hi there,

Using Publisher, I've been having trouble exporting to PDF for a week now. 

I've generated a PDFLib.log of the error that occurs when exporting to PDF.

I've also attached a screen shot showing the error message.

------

System info:

Apple M1 Pro, 14 inch, 2021.

macOS Sonoma 14.7.2

------

Publisher version is latest:

Publisher 2.6.2.

------

I've tried exporting different ways to narrow down the error. 2 things stood out:

1. I can successfully export if I change "Embedded fonts: All Fonts" to "Embedded fonts: Text as Curves."
2. Unchecking hyperlinks and bookmarks options in PDF export settings does not solve problem.

I don't think the issue is to do with hyperlinks. Perhaps font related issue?

 

Thanks for your time on this.

PDFLib.log

[Hangman]

Hi @cjudebeg and welcome to the forums,

Can you use File → Save as Package, save to an empty folder, zip the contents of the folder and upload the zip file so we can take a look at what is causing the export error...

[cjudebeg]

Hi Hangman,

Thanks for your reply. Here's the file as a package. 

 

Please note - I may have found a solution since I posted. By un-checking 'Tagged PDF' and checking 'Subset Fonts' I've been able to export PDF's.

No idea how robust this fix is (The last fix I thought I'd found only worked briefly; by inputting a range of pages I was able to export PDF's for about a day).

 

Thanks again for looking at this.

package_export.zip

[cjudebeg]

I just found some discussions about 'Tagged PDF' in the Forums. 

For what it's worth, I can confirm that in my case unchecking 'Tagged PDF' has meant Publisher now exports PDFs again. 

 

[Hangman]

Hi @cjudebeg,

Many thanks for the files...

This appears to be a 'glitch' (the only way I can describe it). I only get the error when exporting as All Pages when Tagged PDF is enabled (as you've already discovered)... Exporting as All Spreads with Tagged PDF enabled doesn't give the export error...

Some images have an alt-text, which would be read by screen readers when exported using tagged PDF, though I'm unsure whether that is the intention...

Two options

Export as All Pages, unchecking Tagged PDF...

or

Try the following:

1. Unlock and copy the Table 8 heading text frame on Page 62
2. Add two pages after Pages 62,63 (57,58) using the Warehouse 2 Master
3. Delete Pages 62,63 (57,58)
4. Paste the Table 8 heading back onto Page 62
5. Export as All Pages using either PDF (digital - high quality) or PDF (digital - small size) with the default settings, i.e., with Tagged PDF and Embed All Fonts enabled

The file should now export without the error, but let us know if that is not the case...

[cjudebeg]

Firstly, thank you for your detailed response Hangman.

You're right, any images with alt-text is unintentional, and yes, the problem appears to be specific to exportIng with the 'All Pages' setting.

I am very relieved about the Tagged PDF workaround, but I will definitely try your alternative approach.

 

 

 

 

 

 

 

 

 

[Hangman]

27 minutes ago, cjudebeg said:

I am very relieved about the Tagged PDF workaround, but I will definitely try your alternative approach.

Let us know how you get on if you have an opportunity to try the alternative. This does very much appear to be a glitch since all you're doing with this approach is deleting an existing spread and replacing it with an identical spread using the same Master...

Several other pages use very similar Masters, i.e., Masters containing tables and these are not causing any export issues...

[A Lara]

Since a few days ago I am experiencing a similar problem. I am not able to export pdf (jpg or other formats do not seem affected). The generating preview never ends (even though it reaches 100% very shortly). I can cancel anytime, and I can even press the export button. Then it lets me choose a name and destination, but it ultimately fails telling me an error has occurred. 

The most curious thing is that I am. trying with affinity files that worked well until yesterday. 

I tried the mentioned workarounds like unchecking tag pdf, changing all pages... to no avail. 

Should I downgrade from version 2.6.2.?

Thanks

[Hangman]

Hi @A Lara and welcome to the forums,

Can you use File → Save as Package, save to an empty folder, zip the contents of the folder and upload the zip file so we can take a look at what is causing the export error...

[A Lara]

Sorry. I was going to make the zip file today, but I made a final test and now unexpectedly it works. I did nothing differently. Simply the same documents that were giving me trouble now doesn't seem broken. Yesterday I had already reset the Mac, quit every program, tried to uncheck the tag pdf and every other option I could think of, to no avail. But now, everything works. 

I hope it stays that way. But nevertheless thank you very much for your help. 

[Hangman]

Hi @A Lara,

That is good to hear, and I'm glad you can now export your file... If you see a repeat of the issue, just let us know, and we'd be happy to take a look...

[Affinity Info Bot]

The issue "Exporting to PDF When Spelling Language is Unknown Fails" (REF: AF-6294) has been fixed by the developers in the latest beta build (2.6.3.3273). 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.