VijayN

Thanks for all the suggestions. There are no intended blanks, so searching for and deleting double line breaks should do the trick. Also discovered a quicker way of deleting blank cells in Excel that that doesn't mess up data in columns to the right. Cheers.

I'm producing merged letters from Affinity Publisher, with one record per page. It works fine, but I can't figure out how to strip blanks (remove blank fields) from the address block. E.g. if <addressline3> is blank for a particular record, a blank line appears on their letter between <addressline2> and <addressline4>. I'm currently deleting blanks in the data file manually, which takes time, so any advice on how to do this in Publisher would be appreciated.

A very minor issue... I can edit and save most changes to the preflight preset but I can't save changes to the bleed hazard value which is currently 6mm. I can increase it or decrease it but the value won't be saved when I save the preset. It always reverts to 6mm. Other changes are saved e.g. warnings for spelling errors etc. Am I missing something or is this a minor bug? I've disabled bleed warnings for now, but it would be useful to save other values in the future.

Thanks, that's really helpful, and I've found the rogue hyperlink. However, why does the retail version not identify the non-compliant hyperlink, even though it's set to give a warning (see screenshot)? Cheers.

A 92-page document I'm working fails to export as a PDF from the latest retail version (1.10.1.1142) but exports successfully using the recent Beta release (1.10.1.1135 Beta). Error message attached. I uninstalled the retail release and reinstalled it, but it still fails to export the PDF. I'll continue using the Beta release for now.

Excellent. Thanks for the update

I've not had any problems saving documents since downgrading to 1.9.2. (I'd been experiencing the same save failure bug with several documents in 1.10.) I uninstalled Affinity Publisher completely (via Windows control panel) and then reinstalled using the 1.9.2 installation file. This can be downloaded here: https://store.serif.com/en-gb/update/windows/publisher/1/ (There have been no problems working on the same files I edited in 1.10).

This is a major problem that many users have reported (in several other streams) after installing 1.10 in the past few days. Hopefully Affinity have got their people working on it.

This is a major problem that many users have reported in several streams after installing 1.10 in the past few days. Hopefully Affinity have got their people working on it.

@Jon P My work would have ground to a halt if I hadn't saved my copy of the Publisher 1.9.2 installation file. If the bug can't be identified yet would it be worth warning people before they install 1.10, or providing a link to 1.9.2 for people experiencing the same problem?

Experience the same issue and reported in another stream: https://forum.affinity.serif.com/index.php?/topic/147012-publisher-11001127-save-failed-due-to-internal-error/ I have since uninstalled 1.10 and reinstalled 1.9.2 and no longer have problems saving.

My PC would have been on for about an hour when the first save error appeared. The second time would have been after the computer was restarted a few hours later. I've had to uninstall 1.10 and reinstall 1.9.2 now as I can't take the risk of losing any more work.

All my files are saved to a local drive. It's quite full but still has 39GB free. Not sure if this is relevant but... when trying to save files failed I tried Save As (as suggested in some of the error messages) but all I got was the same error plus new empty files (0 bytes) created with the new names given. This problem has appeared with several completely unrelated publisher files so I don't think it's specific to the files I'm working on. However, I've uploaded one of the files using the link you posted. Like Louisk, all my files were created some time ago with earlier versions of Publisher.

I'm getting the same error when trying to save changes to different documents since updating to 1.10 yesterday. The documents have nothing in common (for different clients) and the changes made are basic (e.g. text edits or moved text objects). Looks like I'll have to uninstall and revert to 1.9. Using Windows 7. Screenshot below...