SamMN

I'm also getting this issue, I'm fairly sure it's a bug. I have a document (can't share publicly; confidential company document) where the majority of the images are not showing up in the Resource Manager. The document has over 50 images, all linked correctly, which are missing from the Resource Manager; there are no errors in Preflight regarding images. If it helps, this is a document that was originally built in Publisher v1 some years ago and has been updated over the years, and then converted to a v2 file. Resource manager was working until relatively recently, though I couldn't tell you when it stopped working correctly as I've not kept an eye on it. I even tried clicking 'Replace Image' on the picture frame and re-selecting the correct image to see if that might prompt it into appearing in Resource Manager, but no such luck.

Looks like the corruption was caused by the file sitting in a OneDrive folder. Because it's a significantly large file, seems occasionally when it saves it corrupts itself (occasionally the Save progress bar appears twice when it saves, the second time it flashes up it progresses slower, reaches halfway then disappears). Thankfully as I had that OneDrive folder on another computer that was powered off at the time, I've managed to boot that computer with WiFi disabled, so I could grab the file before it synced and downloaded the corrupted version. So I've created a new folder on my computer that sits outside any iCloud or OneDrive just to house big Affinity files. Bit difficult when across both Windows and Apple the main folders to save files in are now linked to the cloud (OneDrive/iCloud). I've worked with Affinity files sitting in cloud-synced folders for years and this is the first time I've consistently encountered irretrievable file corruption. Do Affinity v2 programs save files differently to v1 in a way that might make it more susceptible to cloud-sync corruption issues?

A file that was working fine is now impossible to open as Publisher 2 immediately quits as soon as it tries to open the file. Is there any way to recover the file? It's a crucial document. I've attached the error report, but the file is too big to attach here (it's also a sensitive business document so can't just attach it to a public forum post) Publisher 2 Crash.txt

I've just had this same error message on MacOS Monterey when saving to local storage (first a local OneDrive folder, then tried saving the file other places too (e.g. Desktop)), i.e. seems non-FAT, local partitions can be affected too.

Sod's law it now seems to be working properly. The only thing I can think is that it might have been triggered by opening the file in different locations. I.e. I work on that file on my personal Windows laptop at home, and at work on the office iMac, so although all the linked files sit in a OneDrive folder, the pathname of linked files changes when I open the file from a location that's different to when I was last working on it. Although that file was supposed to be embedded, might have glitched when it struggled to locate the other linked resources? I'll try opening the file this evening on my personal laptop and see if that retriggers the glitch.

It's set as 'Prefer Linked' (it contains a lot of images). I then switched that specific file to Embedded in Resource Manager. Unfortunately I can't upload the file to the forum publicly as it's a confidential company document. In case it's useful, running Publisher 1.10.5, on an iMac 4K, 21.5 inch, 2017, , 16GB RAM, 3ghz quad core Intel i5, Radeon Pro 555 2GB, Monteray 12.6. The file was originally created back in April 2021 and has been updated numerous times over the past year and a bit, so could've become a bit broken if Publisher has been updating versions since then (which obviously still isn't ideal)?

In a document I'm working on, I've got an SVG file that I want embedded in the document (as I want to make a change to the colours of the file in the document - as in, by double clicking on the embedded file so it opens the SVG in Designer mode in a new tab in Publisher). All works fine, but if I save and re-open the document, the file reverts back to linked, but Publisher still recognises there have been changes to the image because the Navigator box still shows the correct (edited) version, and it also flashes to the correct colour for a second when I flick Preview mode on and off. I've done this a load of times in other documents and never encountered this glitch before. So in the screenshot, the KeyReads logo is in its original colours as a linked file in the document (according to Resource Manager, even though I'd switched and saved it as embedded), and in the Navigator box at the bottom right, as the altered white embedded version I wanted (and had saved) in the document. Turning on Preview mode turns the linked file to the white version for a second, before it goes back to the original colours. Am I missing something obvious?

So if I'm trying to match a set colour using HSL adjustment, I use the Info panel to lock two colours to compare. On all the tutorials (e.g. https://youtu.be/4IoKN4_aBCA), when they're adjusting the colour to try to match the two colours, the numbers in Info change in real time, yet when I try this the numbers only update when I release the relevant slider, which makes trying to match the colours far more of a faff. Am I doing something wrong, or is there an obscure setting I need to change? Running Affinity Photo on Mac, 1.10.4

I've never tried using them before, so maybe I've made a mistake, but shouldn't "review / inspection" be all kept on the same line due to those non-breaking spaces? (Shouldn't it break the line at "digital" and start the next line with "review"?)

OP here under my work username (as I'm at work). Yes, it's a Surface Laptop 3, the Pro bit was a typo (it's one of these things). No external monitor connected. Yes, it's the colour profiles that are the default on the machine provided by Windows. I haven't altered the colour profiles at all or downloaded new ones (changing from Enhanced to sRGB is the first change I'd made to it - to be clear, the default setting on the Surface Laptop 3 is Enhanced, I had to change the default to sRGB). Let me know if I need to provide more screenshots or I've missed a question! 🙂 Thanks again for all your investigative work!

Having to go into different menus/options screens to keep learning spellings it flags is a bit of a faff. It should be a quick option in Preflight to learn the spelling; or open up the Spelling Options box like it does for Font Manager when it flags missing fonts. Ah, cheers for that. Preflight should flag that it occurs in a placed object and let you know which object it's finding the issue with rather than opening the font manager like that.

Maybe there is a way to do this, but you should be able to tell Preflight to ignore specific things it flags if they're not actually an error (or Publisher is glitching, like in the latter example). For example, it's flagging an email address as a spelling mistake; I don't want to completely turn off spell check to get rid of the message / warning, I just want it to be able to click a button that essentially tells Preflight 'that one's fine'. It also sometimes makes mistakes flagging a missing font; says a font is missing but when you open font manager that font doesn't appear there (screenshot attached).

Maybe there's some weird technical reason why it should be like this (maybe caused by the export settings?), but if you put a live filter motion blur on an image, then export the page as a PDF, the motion blur isn't applied to the image. (Trying to upload a screenshot of how the image looks in Publiser but keep getting the error message "There was a problem processing the uploaded file. -200". No idea why.) test.pdf motion blur test.afpub (Below) PDF version: (Above) How it looks in Affinity (i.e. significantly blurrier)

It's just a new document with generic A4 settings. Issue happens every new document. It's just a freshly created text box with filler text, no style applied; arial font, regular, 12pt. Doesn't seem to matter if you adjust the wrap outline before or after the text is inserted. Running Publisher 1.7.3 on Mojave. Example file attached. text wrap.afpub

Brand new document; see screenshots. Am I missing something? I've seen a few previous posts on this issue (and it seemed that there was some issue with the Ignore Text Wrappings setting) but they were for the BETA last year and from the posts it seemed like it had been fixed? Changing to 'Largest Side' and adjusting the Distance from Text doesn't seem to do anything. Any ideas? Edit: The first picture is the actual text frame, the second picture is of the wrap outline Thanks! Sam