coolieranx

That's the problem—nothing is missing from the linked afpubs. I've quadruple checked to make sure there are no broken links within those afpubs. I've outputted the PDF despite the preflight warning, and it looks exactly the same as when I add flattened afphoto images (I ran a comparison). The only x-factor I can think of is that I work from iCloud (all my work is synced back to an iCloud folder). Maybe Publisher gets confused when checking links back in a folder like this?

That definitely takes away the error. But one question: Can I be sure the those links will be high res when I'm outputting without it checking inside of links? Resource manager seems to indicate everything is a-ok, so should I trust that over preflight? Thanks so much!

Hi all! I've discovered a pretty strange, but not debilitating bug in the Publisher preflight. Basically, when I add afpub files to my layout, preflight says that the "Linked resource is missing" for every afpub placed, even though they are properly linked, and the source afpubs have properly linked images within them (if you look at attached, you can see that each image is on a different page, and are all OK in resource manager). What's stranger? No matter what page the afpub is on, preflight shows that the error is always on page 1 (also see attached). Anyone experience this, or know of a way to fix this? PDFs output correctly and in high resolution, so the preflight error is definitely a false-positive. Is placing an afpub in an afpub not best practice? Would it be better if I added flattened afphoto instead? Thanks so much!

Hello all! In Publisher 1.10.0, the Page Up/Page Down and Home/End keys no longer perform any functions. They worked normally on the previous public release of Publisher. The keyboard is an Apple Wireless Numeric Keyboard. The Mac is a 16" MBP running Big Sur 11.5.2 (the bug appeared on 11.5.1 as well). Anyone else experiencing this? Thanks so much! Love the new release!

LOVE this new release! I've noticed that when you add a folder in the templates section of the New dialog, if you rename the added folder in Finder, it immediately crashes Publisher once you give the program focus again. I was able to repeat this every time in 1.8.1 on both of my Macs, both running the latest Catalina. Thanks, and congrats on this amazing release!

Ahhh. Thank you for explaining that! I agree that it’s a design flaw. A linked file should just remain linked, and at most, only a small low res preview should be embedded into the native file. What’s the point of linking if it doesn’t reduce file size? It’s basically just doubling up the size of a project for no good reason.

Hi! Using 227 on Mojave, and I created a new letter size document, choosing “link preferred.” Started putting images into it (all afphoto), and when I saved, the file was 1.6 gigs! Went to document setup, and somehow it reverted to embed preferred. Switched back to linked, re-added the images, but the document still won’t honor linked, leaving my file at 1.6 gig. Am I doing something wrong, or is this a known bug? Thanks so much!

I can confirm that this happens to me as well. At first I thought it was macOS’s weird autocapitalization, but this happened even with that off in the system.

Ahh, I see where the bug is now. When you import a jpeg, you can easily stroke the box. I was importing afphoto files, and stroking isn’t possible, on both computers I checked it on.

I’m on a Mac. macOS 10.14.2 (using latest Publisher Beta, 1.7.0.206)

On my computer, that doesn't work. Applying a stroke doesn't do anything to an image placed that way. Maybe it's a bug?

Ahhh, I see what's happening. If I originally place an image in a document with the CMND + M (or File > Place...), there is no option to stroke that item once it goes into the document. If I make a box first, I'm able to have full stroking options. Why are these so fundamentally different? If I'm placing straight away with CMND + M, and it's putting in an image with a box, I feel like I should have stroking ability. Is there a reason that these behaviors function differently? I guess what I'm asking is, what's the purpose of the CMND+M version of putting in an image versus putting it in a box first? Does this have to do with an image placing methodology that Affinity wants for this program? Is CMND + M placing a pixel layer directly, and if so, why is that desirable/undesirable to other methods? Maybe I'm too new to Affinity, but I don't quite understand why I might want a pixel layer in a layout program. Sorry if this is confusing, but I'm super curious what your response will be! Thanks!

Did a search before posting this, but didn't come up with anything. Is there a reason that when selecting an image, applying a stroke from the stroke panel doesn't seem to do anything? I'm trying to put a dark outline against a picture box, but nothing happens. Is this a bug, or a missing feature? Thanks! Love how awesome this beta has been so far!

Actually, hold on. I tested what @JFisher mentioned about afphoto/afdesign files added to the master page. It made saving impossible, even on my purely local copy. Maybe disregard my theory on cloud files!

I can confirm this bug as well, with a little bit more information. In my case, it appears as if this bug happens to items that sync to the cloud (in my instance, iCloud). I tried saving to a place on my HDD that doesn't sync to anything, and it worked just fine. No previous version of the Affinity Publisher beta had any saving issues whatsoever, so I'm wondering if this is a bug that got introduce in this version?

Perfect! Thank you so much!!

Actually, figured it out! Publisher was struggling with the font I was using, which was an older PostScript Type 1 (I believe Type 1, since it came with an scr file in addition to the type file). Removing this font allows me to export now, no issue. This leads me to one thing I can't seem to find. Is there a way to outline fonts within Publisher? I haven't been able to figure that out yet, besides going back into Affinity Designer or anther vector program. Thanks!

As of this latest beta, exporting to PDF isn't possible. I still get an endless "calculating," but no ability to export without error. Anyone else dealing with this? My files are a mix of afphoto, psd, eps, etc. Are there known issues with non-Affinity files imbedded into a document?

I believe control + W does this, but it would be awesome if it was a teensy bit more obvious.

In the first and second beta, I've had difficulty exporting PDFs. If the export dialog shows "Calculating," but doesn't end up showing a file size, Publisher can't make a PDF. Instead, it creates an error: "An error occurred while exporting to..." I haven't been able to find a reason why this is happening, but it occurs on many files. Anyone else getting this?

I hugely second this. Preflight, I think, is extremely important for this program to be used by professionals (at least by me!).

The option to export PDFs with bleed is definitely there, but it needs to be more obvious, I think.

So happy to be testing this! Three things I've noticed so far in beta 1: There seems to be no shortcut for Place (CMND+D or otherwise) There's no way to type and search for a font in the paragraph/character style menu Page up/down is not working for me to go from page to page.