chapolote

Well, how I said: there should not be anything in this pdf what is not in the other pdf's generated from Bricscad not causing crashes....

I create documents in which mainly pdf are placed, which were generated from an AutoCad clone (Bricscad). This usually works without problems, but now I have the second pdf where Publisher crashes immediately when placing. However, similar pdf's can be placed without any problems. Attached is the file that crashes. Can anyone reproduce the crash and is there an obvious reason why Publisher crashes? I crash publisher when placed.pdf

Did you try the other workaround described here?

No. Thank you for the hint

Well, I'm working under Win 10 and the respective update should be KB5017262. I will give it a try, but isn't it a bit of an odd solution to the problem if I uninstall a security-related Windows update to make the Publisher work? Shouldn't Affinity rather provide an update?

While I can replace any kind of image/document like jpg or pdf in the document itsself without any issues, publisher crashes immediately and comprehensibly on replacing images/documents within resource manager. Bug reports are attached. 10490161-7739-4938-93a7-ae1892508892.dmp 218d49e7-08c7-4445-9a1b-b4c94c797d4c.dmp 31db8fa8-5048-4f6e-9e93-bc03ddacb31b.dmp 445b393f-88b0-45b3-97a0-2462422fdd30.dmp 7568354b-fb97-49c7-9545-2632bf49e404.dmp a5b959a2-41e2-404e-bcea-52b68422fab8.dmp b3ed1365-7734-4c17-b459-3eb4b72ac329.dmp

Who knows what Affinity does that such problems appear Strange, other apps don't. No harm meant.... 😜

Due to the fact, that all other programms show proper color it doesn't make sense, to change anything in color profiles on OS level. However: a simple reinstall of Publisher did it. Thanks nevertheless for your assistance 🙂

Hi, affinity publisher shows very strange red colors in color palette, see attached pictures. The first shows how red is displayed in color palette, the last, how a filled path with red is displayed and the second, how it looks in the exported pdf. I checked document settings, it doesn't make any difference if I chosse RGB/8, RGB/16 or RGB/32. As profile I tried Adobe RGB as well as sRGB, the red color stays ugly brown. The same happens, if there is red color in any embedded picture, Publisher shows it in brown. Other colors like blue or green seem to be ok. Any idea whats goung wrong here?

Sorry, now idea how to sort the image-attachments Looks a bit confusing. Hope you get along....

Ok, I proofed it again, with a new installed publisher 1.8.2.620 and a blank standard-template A4 for print. (Deinstalled publisher, rebooted and installed it new) OS is Win 10 Pro Build 18362 See screenshots filelink_publisher_pdf, filelink_publisher_jpg and filelink_publisher_txt to verify, what I did in publisher. Tried 3 different files, to show first an (for me) unexpected behaviour: for pdf it's generated an action to read another article. So far, so good. for txt-files or jpg-images a weblink is generated, what surprises me, because I expected that the file opens in editor(txt) or any picture viewer (jpg) If you watch my screenshots now, you see the bigger problem: none of the generated links is working: filelink_publisher_pdf_generiert shows this wrong path I described in my first post. Such link can't work. filelink_publisher_txt shows the link, how it would be passed to my standard-browser (because it's a weblink generated). Because of a not correct path, the browser can't open a link like x:%5Cfilelink_publisher.txt Same behaviour for the jpg file. The generated pdf is opened adobe acrobat pro dc in actual version.

assets.propcol is available with a size of 341b. Unfortunally it's not readable by any editor, cause it's machine-code. I have a backup of this file from one week ago, and using this file at least the assets panel works and my old assets are back. But I worked a lot the last days, especially wit new assets, and they are all gone. I ask myself, if a windows recovery point could help, but I doubt, that it would recover files in the user directory. And why I have the same issue on my laptop, which was not used the last days and switched off during data-loss on my workstation, is not understandable at all. It looks like, that one document created with publisher could cause the issue. By the way, Joachim_L: Just some issues I have with actual publisher release: quiet often on opening a file, publisher crashes right away. Trying it again and agaín helps mostly Files synchronized via my NAS to my laptop sometimes don't open anymore, publisher says, they are damaged. Happened after updating to 1.8.1. Same file size, same content, if I compare them. Opening them again, they suddenly work again. TOC is extremley faulty: the order gets broken, when you move an element with a defined style for TOC to another place. File links doesn't work correct And unexpected crashes when you work every day 2 or three times. Trying again, what you did before the crash, it's not reproducable. This Release is all, but not stable, and for production environment an imposition!!!

No, no backup available. The panel is completely blank. I'm not sure, but I think to remeber, that after blank installations there were some predefined categories like text an images. But can't reproduce it anymore....

Today suddenly all assets in different files doesn't show up anymore. Had huge problems with the newest version of publisher and followed the advice here in the forum to downgrade to a previous version (after complete deinstall of 1.8.6) and now all assets are gone. What's even more strange: even on my laptop, where I didn't change anything, no assets are showing up anymore, even in files, which I didn't open for days. Where the hell are assets stored? Is there any way to recover them? On both computers, under appdata/roaming/affinity/publisher/1.0/settings is a file assets.xml, with ListMode 'False' and Category '0'. To be honest, actually I'm quiet dissapointed about actual release of affinity publisher: bugs over bugs, crashes and now the assets gone. Hours of work. I'm working as professional and this should definitely NOT happen!!!!! Can't even downgrade, because my file won't open, because they are created in quiet actual versions.

When I add a file-hyperlink without checking "including file on export", the links are not working, because the exported path isn't correct. Presuming, my exported File is stored under drive d in the directory export and the linked file is is called test.pdf and stored under drive e in directory myfiles, the generated link looks like this: d:\export\E\myfiles\test.pdf Correct would be: e:\myfiles\test.pdf Can someone confirm this bug or know any workaround? By the way: if it would work, it's not helpful to have absolute pathes in file-hyperlinks, because by giving the exported file to someone else, the link would be broken. Using the checkbox "including file on export" creates valid links, but all files will be stored in the same directory. If you have a document with lots of including files, this is not helpful, because the main-file is somwhere hiddem between all the included files. There should be the possibilty to define an additional directory for included files, e.g. my file is stored in a certain place and automatically a directory will be createt on the same level called "attached files" or whatever