Jump to content
You must now use your email address to sign in [click for more info] ×

Export to PDF fails since upgrade to Publisher 1.10.0


Recommended Posts

A document I've had for the last year now fails to export since upgrading to Publisher 1.10.0. It exports fine in previous versions. There is no decent error message, just that it's failed to export. I've attached the file that is having the issues.

Edit: attachment removed now error has been fixed.

 

Link to comment
Share on other sites

I had two basic problems with the file, one is I do not have the fonts. The second had to do with ToCs. I ignored both and it exported fine. I am on Mac OS 10.14.6 

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

For info the reason for failure in my newsletter was that the email address started with a capital letter, obviously auto correct capitalising the first letter in a new sentence by what ever text compiler the contributor was using e.g. Word

 

Alan Pickup

Windows 11 Home all Affinity suite of Apps PC and Gigabyte Laptop 16gb Ram and Nvidia GTX1660 Super on each.

Link to comment
Share on other sites

Hi Lagarto

This is the bit in the report that refers to the error

image.png.ea2b8ebb509b6f19523fe1b1bd7f4d57.png

This is the text in Publisher and you will notice the Go to Hyperlink Target is greyed out but in 1.9 it opens an addressed email form

image.png.9f32563aeee09c0fb6fd256438953369.png

image.png.35682a42469694055a74d445e9546c85.png

 

 

Alan Pickup

Windows 11 Home all Affinity suite of Apps PC and Gigabyte Laptop 16gb Ram and Nvidia GTX1660 Super on each.

Link to comment
Share on other sites

I think you'll find, Alan, that the error is the space after the ":" in "mailto: Michael...". I'm not completely sure, as I have not managed to make an export fail while logging is enabled. But when it works (with logging enabled) there is no space after the ":".

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

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.5

Link to comment
Share on other sites

6 hours ago, Lagarto said:

How very odd! Email addresses are not case sensitive so while uppercase letters are normally not used, they are allowed (even if trivial). I just tested and at least the 1.10.0.1127 (Windows) release version does not have this problem.

Just found my problem thanks to this thread. Couldn't create Digital PDF , but print was fine - so had to be links. This was my CV - so just tweaked and updated for roles - a space had been inserted in front of my email address - I believe this is a bug - but I don't have time to check through other documents yet - anyhow - easy to fix document

Link to comment
Share on other sites

If you look at the clip from the actual document there is no mailto: that is being generated by the report, there was also a second instance where the line began with a M in the email address and there was nothing before it, it was the start of the line and genrated the same error

 

Alan Pickup

Windows 11 Home all Affinity suite of Apps PC and Gigabyte Laptop 16gb Ram and Nvidia GTX1660 Super on each.

Link to comment
Share on other sites

1 hour ago, Lagarto said:

Yes, exactly. 1.9.x versions allow this:

email_1.9_spaces_ok.png.987237c6d2a21246bab342fe9c1671e2.png

But 1.10.x versions cause an export error because of the preceding space (which is basically correct, because this IS an error, but it should be preferably either ignored or reported by giving an accurate error description). The actual bug, however, is that the same error is caused by having a space in data parameters like "subject" which by definition should allow spaces and non-ANSI characters.

So in versions 1.9.x, the following kinds of addresses would not be a problem (because email addresses are not validated), but in versions 1.10.x they are, even if being valid addresses:

 

email_1.9_spaces_ok_02.png.756a452a60197ec7942762e6fdb922d1.png

Can it be a coincidence that spaces are appearing in front of mailto?

Link to comment
Share on other sites

I have the same issue (won't export the entire document with all hyperlinks).

If I limited the page range it works (even when I change the range to find the "problem page").

But not when I do my whole document (286 pages many anchors/hyperlinks, links to URLs, but only 1 email hyperlink). I let it try to calculate for an hour but it didn't complete. But it still will export with fewer pages and without it calculating.

 

 

24in iMac M1, OS 11.4, 16GB RAM, Affinity Publisher 1.10

Screen Shot 2021-08-07 at 11.44.08 AM.png

Edited by Brent Pedersen
Link to comment
Share on other sites

Thank you for responding. I can export a smaller page range even when it doesn't show calculated. 

The instructions you sent me look like they are for Windows. I'm on a Mac.

Is there a way to export the file as v. 1.9, reinstall 1.9 and wait until 1.10 is fixed. I think if I just install 1.9 it won't be able to open it since it was saved in a newer version. 

Link to comment
Share on other sites

1 minute ago, Lagarto said:

The earlier versions (for macOS) can be downloaded here:

 https://store.serif.com/en-us/update/macos/publisher/1/

However, that won’t help in a case like this:

41 minutes ago, Brent Pedersen said:

I think if I just install 1.9 it won't be able to open it since it was saved in a newer version.

 

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen)

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.