init Posted December 20, 2022 Share Posted December 20, 2022 Yes, f***ed. I have to deliver a project to the client and getting this on the latest v2.0.3: Not very descriptive, isn't it? This window is never updated as well: Lastly, to register on this very forum I had to spend quite some time proving to Google that I am not a robot, just a disappointed used who had a blast running v1 since 2019. Thank you for the v1, it was great. Off to Adobe I go. Bye! Quote Link to comment Share on other sites More sharing options...
init Posted December 20, 2022 Author Share Posted December 20, 2022 P.S. To their credit, Affinity moderator has approved this thread. Bold. Patrick Connor 1 Quote Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted December 20, 2022 Staff Share Posted December 20, 2022 17 hours ago, longTimeUser said: P.S. To their credit, Affinity moderator has approved this thread. Bold. Mainly because you posted it in feedback, which seemed fair given your experience François R and init 2 Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
thadeusz Posted December 21, 2022 Share Posted December 21, 2022 As much as I share the expressed anger towards serif - and I wrote mainly cynical comments about flaws in Publisher in the last year - why would someone use version 2 for production right now? I mean - you can't go back to V1 with your files. Nevertheless, it's good to test it out and post problems - thank you! I've also bought it, installed it and looked at it. And use V1 for now. Serif will need some time to make it's homework, often too long for my taste. But that's all known. It's like updating MacOS on day of release. Good luck with that! I'm always one year behind and have not many problems in productions. Good luck with Adobe by the way, with this behavior. But I just read about problems, never have them really. So it's only 2nd hand knowledge . I'd really recommend to hold back with updates during and for productions, even we're not getting those new shiny functions immediately. loukash 1 Quote Link to comment Share on other sites More sharing options...
init Posted December 22, 2022 Author Share Posted December 22, 2022 Alright, enough of this unproductive rage. v2 clearly has some issues, but going back to Adobe isn't going to fix them. I will reply further in https://forum.affinity.serif.com/index.php?/topic/173147-publisher-v2-pdf-export-error-without-any-clue/ Quote Link to comment Share on other sites More sharing options...
Staff Pauls Posted December 23, 2022 Staff Share Posted December 23, 2022 If you enable PDF logging and share the file it might to able to narrow down what is causing the problem. The important failure code is usually towards the end of the file. init 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.