jinchoung

as for: "The message does not come up here much" google: affinity publisher an error occurred while exporting to and see how many hits come up. it happens frequently enough for them to know that this is an issue by now.

"The software gives generic messages when we are not sure what has gone wrong" not true. it is listed the reason in the LOG FILE. again - my point is that hacking the registry to get a log file to get this information is completely jackassbackwards and there's NO REASON why it has to be. PUT IT IN THE ERROR MESSAGE!

hey patrick, that's not the point of my post. i resolved it by looking at the log file (pdf version was incompatible with some feature in the document). the point is that the error message given is stupidly unhelpful. it's like an invitation to go look it up on google and that's not a good way for an error message to behave. that is the point. that they need to change the way errors are reported so that it actually assists the user in resolving the problem rather than leaving them flopping around on google or on forums. jin

hi, so i purchased publisher in order to do some PDF publishing for work and after finishing the project and publishing to PDF, i get this error message: "an error occurred while exporting to:" and then the directory. this is simply not acceptable as an error message in 2020. are you guys getting your cues from a car's CHECK ENGINE LIGHT circa 1990? first of all, failing to export is bad as it is. this shouldn't happen. but should it happen, the error message needs to be VERBOSE and TELL US WHAT THE PROBLEM IS! WHY WOULDN'T YOU DO THAT?! telling us simply that there IS a problem is ABSURD! after googling, i found that there's a registry entry you can make to get publisher to create a log file upon errors but that just compounds the degree to which my mind is boggled... that one would have to modify the REGISTRY... TO FIND OUT WHAT THE PROBLEM IS!!! come on guys, you gotta get it together. i bought the trio of your programs to avoid the monopoly of adobe and i'm rooting for you. but having this kind of error message does not give me confidence. AT ALL. IN THE EVENT OF AN ERROR: - ideally, tell me what's wrong and walk me through how to resolve the issue and then let me proceed. - failing that, tell me exactly what the problem is. and then i will manually change whatever settings need to be changed to make it work. - if there are missing files, GIVE ME THE NAMES OF THE MISSING FILES ffs! i've read some forum posts that say that the registry hack log files don't even tell you which fonts are missing. i'm actually kinda gobsmacked that this is the state of error handling for your product. this feels like a point release open source project. again, if the user is prevented from doing something as important as actually publishing, you HAVE to give us all the relevant information as a DEFAULT without further action or hunting necessary by the user. jin