big smile

My Affinity Photo file (that is included in the Publisher file as a link [e.g. not embedded]) makes use of both a mask (to hide the white background in the photo) and an adjustment layer (to change the colours of the photo). If I turn off both the mask and the adjustment layer, then it will come out just fine. If I keep any one of the mask OR adjustment layer, then problems occur. However, these problems only occur if I export the document as a black and white PDF. If I export it as colour it is fine. I guess this means I will have to rasterize my Affinity Photo? I'd rather not, as I like the flexibility that comes from having a layered version. (I know I can keep a backup copy, but still....)

@Wosven are your comments referring to the beta version, because I am using Affinity 1.8.4. I also did try converting the document to grey colour space, but the distorted images still occur.

Thanks for your help! I tried that and it doesn't work. But also, I'd like to have one colour document, that I can export as colour PDF and B&W PDF. If I have to add B&W adjustments, that kind of spoils that, as it means I'd now have to have two documents.

I have a Publisher Document that is in colour (i.e. it has an RGB colorspace). This is how it looks: (This is taken from a PDF export of the Publisher document) But I need to create a black and white version. The Black and white version is created by: • Exporting as a PDF and selecting grayscale in the PDF options • Importing the Publisher file in to another publisher file that uses a grayscale colourspace. This other file is then exported as a PDF (by selecting grayscale in the PDF options) In both cases, this is how the exported PDF looks like: I've got no idea how to fix this? I am a long time Publisher user and this has never happened. The original source images are Affinity Photo and Affinity Designer files that are imported into Publisher as links (not embded) I can't share the original document publically, so would appreciate any suggestions on how to troubleshoot. I've searched around the forum but not found anything.

Odd that doesn't show for me, this is what I see: The image is an afphoto file, does that make a difference?

I've placed some linked images in my Affinity Publisher document that have been scaled using "Scale to max fit". The original images are freaking large, so when I convert the document to PDF, Publisher takes a long time to do it and the images come out corrupted in the PDF. I need to scale down the source images so they aren't so big. In InDesign this was really easy to do. You could just check by what percentage they had been scaled by in InDesign, open up the images in Photoshop and then scale down by the same percentage. That way, when you went back to Indesign, you wouldn't have to worry about "Scale to max fit" changing things due to the smaller images size. Plus, you'd know that the images are at the best DPI for printing. Is there way to see by what percentage an images has been scaled in Affinity Publisher. The resource menu shows the original size and new size, but it doesn't give the percentage (and I suck at maths )

@Gabe I've also noticed that often, the selector to select a page in the document disappears. When you select an imported Publisher page, this is what the user should see: However, it often ends up looking like this: The page selector disappears. The document must be reimported to restore it.

Fingers cross they fix the table of contents style sheet bug and the duplicate style sheet bugs!!

It would be better if it was in Publisher natively. Especially when using automation software to go through multiple pages. Having to switch to Studiolink first adds unnecessary complexity.

I don’t think it has been answered in 1.8 at all. I copy and paste text between my Publisher documents all the time, and even though the text has identical formatting, I still end up with "Title 1" "Title 2"..... "Title 15" I've just spent 40 minutes manually merging all the styles sheets into one. Most annoying!

Affinity Designer Beta has a new feature: "Select Same / Select Object functionality" Are there any plans to add this to Affinity Publisher? It would be very handy especially when using automation software (such as Keyboard Maestro) to work on large documents. Today I had a project where I needed to select all the text on a page (but not the images) on a 160 page document, so something like this would have been perfect. The Adobe apps allow for scripting, which Affinity does not, so anything that makes Affinity more accessible to automation software would be great (especially as Automation software is more user friendly than scripting). In this context, adding Keyboard shortcuts for transform options would also be a game changer, so perhaps you consider that too!

The issue occurs with rectangles too. In fact, in the examples I have posted, I used rectangles. I dunno why I was calling them picture frames, I guess I got mixed up!

@Gabe It definitely happens with imported multi page Publisher files. I will keep an eye out for any patterns.

@Gabe Thanks for looking into this! After experimenting more, it seem to happen when the content comes from another Publisher Document that has been imported in. Attached is: Video showing the problem. "test" file that has the problem. "Child" file that is the file that has been imported into test. capture.mov test.afpub child.afpub

Example: I have three publisher documents: "Document Global" (12 pages) "Document A" "Document B" "Document Global" has content on "page 3" that is used by "Document A" & "Document B". So I place page 3 of "document global" into "Document A" & "Document B. That way, if I make a change to Page 3., A&B will automatically update (when I click update in resource manager). 90% of the time, this works fine. But 10% of the time, I find that something will happen and the imported "page 3" of "Document Global" will change to "page 1". Then I have to go through "Document A" & "Document and set it back to "page 3". And this is a simplified example. You can imagine the nuisance it is if I have imported multiple pages in from "Document Global" and not just page 3. There doesn't seem to be any pattern as to when this happens.

@CallumIs there a way to send it privately? Thanks!

I've started getting this error when opening files: The document doesn't use applesystemuifont, and I can't find a place to install it. How do I fix it? System: Mac OSX 10.14.6 Affinity Publisher: 1.8.4

Affinity Publisher has a preview mode, which shows how the document will look when it is printed out. In this mode, all non-printing visual indicators are suppressed. However, since 1.8.3. this mode is not respected for empty picture frames when zooming out. Example: Here is my masterpiece. In it, I want green and grey backgrounds and so have used empty picture frames to create this. In preview mode, it looks like how it will print out. However, if I zoom out too much, the visual indicators for empty picture frames appear, even though preview mode is still active. Converting the picture frames to curves does not help (although the issue will go away if the frames are converted to text frames).

In Publisher is there any way to automatically caption images by file name. E.g. you import and image and then a text box with the file name appears under the image. Thanks!

In the end, I was getting close to a deadline, so I just remade the problem document and that seems to have fixed the PersonaBackstore.dat. However, I still find Publisher to be slugish, which it wasn't previously. Here is the performance tab:

In the end, I was getting close to a deadline, so I re-made the document from scratch and it works now. I guess maybe something had gone wrong? I do importing another Publisher documents into other publisher documents a lot, so if I run into problems in the future, I will reach out.

I make series of Books in Publisher. Each book has its own publisher document. Because the books share certain pages, I create these in a separate document that I call "shared doc". I then import this "shared doc" publisher files into the individual Publisher documents. That way, if I need to make a change to one of the shared pages, I can just make the changes once, rather than having to update each individual publisher document separately. I have been doing this since, 1.8.3 came out and it's worked perfectly. But today it's going screwy. For example, here is a square box in my "shared doc" Because I am viewing in Preview Mode, you can see a big X in the box. However, when I go to output the finished document as a PDF, the big X appears in the finished PDF. Even if I turn off preview mode, the X still appears. This has never happened before. How can I fix this?

I did a reinstall. It was fine for an hour, but now it's back to this again. I've read about PersonaBackstore.dat. It's for storing things that there isn't room in RAM for. But all my various documents are mostly text. Also, I have 16GB of RAM and 10GB is shown as free, so I am not sure why Affinity is using PersonaBackstore.dat.

Since this afternoon, Publisher on my Mac has become super slow. Files that opened in seconds in the morning now take over 8 minutes to open. I have made no changes to the file. Even scrolling through pages or clicking on menus is super laggy, sometimes take as much as 10 seconds for things to appear. Worse still, a file called PersonaBackstore.dat has appeared in /private/var/folders/ft/vkmjt26n273b2rf21tg10_180000gn/T/Affinity Publisher/ It is currently 61.39 GB and growing. What should I do? Should I uninstall and reinstall publisher? Set up: Publisher: 1.8.3 Mac OS: 10.14.6

Unfortunately, I can't provide a sample as it has work that I am not allowed to share. However, I tried making a 'redacted sample' that has only one line of text. When I did this, the Find and Replace worked properly, so I am guessing there must be something in the file that is creating the problem. I noticed that Affinity has an option called "reapply text styles" which can be used to clear overrides. So I set a keyboard shortcut to that command and then used Keyboard Maestro to go through all the text and clear the overrides. I guess this a screwy bug! If I find a way to reproduce it, I will post it in the bugs sections. Thanks to everyone who helped.