nwhit

Not sure what PE costs, but you might also consider simply buying the Affinity Store version of Photo for $49. I haven't had time to try the latest 1.8.2 beta, but I'm guessing EC may very well work just as it has in the last betas for both 1.7 and 1.8. I think the issue is related to the MAS version and the sandboxing from Apple. And I'm speculating that it likely works in the 1.8.1 version from the Affinity Store. The other option is to continue using 1.8 betas and wait for Photo v2 to come out, which will be a paid upgrade, then switch to the Affinity Store version. If you've not used the 1.8.2 beta, you might want to try that first to see if it works again. Runs parallel to the normal retail MAS version, so nothing lost in trying. Might help confirm if it is just an issue with the MAS retail versions. Other plugins are having similar issues with the MAS 1.8 version, so not unlikely it is the issue with EC.

@TomM1 Have you had a chance to check this in the new beta of 1.8.2? I haven't upgraded yet to either the release or the new beta for fear of breaking EC compatibility. Thanks.

Be sure to check for odd hidden characters that came come in with copy/pasting text or by opening PDFs (and sometimes IDML imports). Located under Text/Show Special Characters. I have found several times I had a similar issue that somehow odd hidden characters were within the text that did not show up without turning on Show Special Characters. Also need to be in Non-Preview Mode to see those.

Interesting! After Andy posted that "fix", I looked at my 1.7.3 install to see if maybe that might fix it as well, but saw the same thing you did. The button is greyed out. Hopefully Andy knows how to deal with that as well! Really want to upgrade but really need access to EC, so need to wait to get this resolved. Back in 1.7.3 when it failed to work in the MAS version (while it did work in the betas), I had thought I was going to have to spend another $50 to get the Affinity Store version. But when it worked in the 1.8 betas, I was encouraged that maybe this time it was fixed.

Hopefully that will solve it. I'm thinking I will have to wait to upgrade since I do need EC from time to time. I was soooo encouraged when it was working in the betas. Will wait to see if TomM1 can get it to work!

I haven’t upgraded yet. Plus a mod posted In the release Bug forum that the initial 1.8 Mac App Store version isn’t handling any plugins correctly, so they have a new version already submitted to Apple for quick release. The problem relates to MAS software requiring strict sandbox behavior. Hopefully the newer release will make it work. It does make me think that this was the issue with 1.7.3. I know it worked in the betas, but failed to even open in the final MAS release. Hoping this time that doesn’t happen. Let me know if the upcoming fix works for EC.

Interesting that it has the export issue in ADes 1.8 beta but not in ADes 1.7.3. Should I post this in the ADes Bug forum also, or are you able to cross-pollinate it?

I agree with these thoughts/ideas and think it important to clean this new section up a bit before final release of 1.8. Otherwise, I think it will generate a lot of questions, support requests and criticism. Right now the points discussed above are simply asking for complaints/questions once released to the public.

Further info. I did a new import of the IDML, then fixed a couple other issues where it had problems importing AI files correctly (so I changed them to ADes files). I then went back to this mysterious text frame and used the node tool to modify that text frame's corner radius. This time NO FUNNY magenta line remained! Why, who knows! But in looking at it some more, I can see that in previous betas I am thinking that this text frame likely came in with a 4.2mm radius just like the rounded rectangle above/behind it. And it looks correct when opening the previously saved APub file in the new RC beta. However, when I open the same IDML file in 584, while the radius of that text frame shows as being the same 4.2mm, it is much larger visually and requires resetting the radius to 0.4mm in order to match the correct/previous look and the matching rounded rectangle behind/above it. Perhaps there is some setting I'm unaware of? But that said, I never had this issue when opening this same IDML in any of the previous betas, so this is something new and repeatable. Certainly not the end of the world for an IDML import, but might cause others issues if it does it too often, and also suggest something isn't being interpreted correctly now.

Interestingly, when I use the Node tool to "fix" the radius on the text frame, it visually corrects the radius but still leaves a magenta/purple outline of the original incorrect larger radius frame when preview is off. And this incorrect import of this text frame didn't happen in previous betas.

Thanks. Didn't think of that!

Uploaded the IDML and ID files.

I just uploaded both the ADesign and the exported eps files. (Greater Portmore Accel Drwg.afdesign)

No, this was "assembled" in Photo. When it was created as an RGB, it places in APub just fine. It's only the cmyk version of the APhoto file that when placed in APub that it has the large bounding box. However, the the Mac quicklook preview of the file is correct. I even tried opening the 1.7.3 file in the 1.8 RC beta and saved as cmyk, but it still places with the large box. I did find the contextual toolbar Page Box dropdown, so can make adjustment for this particular case, but it does seem odd.

Yes, but Chris in APhoto beta thinks there might be a bug he's going to log. Thanks.

Just trying the RC beta and find an import issue that has not been there in previous betas. Opening the "Aero A4 Brochure 2013 v2 test.idml" file (you likely have this), one of the text frames brought in has the wrong rounded corners (far too rounded). Previous betas did not do that (see other attached screen cap done in previous beta). Also, not finding where I can even fix this. Is there somewhere to change the radius on a text frame? I cannot see anything in the contextual toolbar nor in the Text Frame panel.

FWIW, works okay for me in 584.

I see that in the RC this is still the same. Very difficult/non-intuitive to edit presets. I also had a crash when working with a preset to check for Hidden items plus checked to look within placed docs. When I double-clicked on one of the warnings in preflight, the app crashed. Affinity Publisher Beta_2020-02-24-142546_TRAC-Main17.crash

Just checking on this in the RC and it appears that there is still no way to edit an existing My Presets? I just selected one of my presets, modified the margins, clicked the TINY Add New Preset plus-mark, and it added it but never asked for a name -- added it as "unnamed". I then right-clicked to Rename the Preset, gave it the same name as the previous one, and it saved it as a new preset with the identical name. That's not good in itself, but also seems to mean that we cannot edit our presets. Appears we are going to have to create new ones if we need/want to edit an existing preset, then delete the old ones???

Yes, so far everything is exporting fine with the Dig Small.

Yes, I have been trying it for the last hour or so and so far, so good. Still have a pdf-x4 issue, but the Digital Small seems to be fixed! Keep my fingers crossed as I keep trying a variety of exports. But also encourages by your results!

Have had this issue in the last few betas and still there. Using APhoto beta 168, have a graphic that is only roughly 7x3" and is a cmyk doc. When I place it in APub b584, the bounding box is essentially an A4 size, thereby requiring either a lot of overhang of the empty bounding box or using a frame or other method to crop. Cannot understand why it comes in with the strange bounding box. I also have an RGB version of this same APhoto graphic created at the same time and it places just fine. Don't know if the error is in APub or APhoto, other than it opens and looks fine in APhoto. I did just try Placing it in a 1.7.3 ADes new doc and it also places with an A4 bounding box, so maybe this is a problem with APhoto??? Gurney_Logo_Footer_-_Literature-1cmykv18.afphoto

Have had this issue in the last few betas and still there. Using APhoto beta 168RC, have a graphic that is only roughly 7x3" and is a cmyk doc. When I place it in APub b584, the bounding box almost makes it look like a Letter size, thereby requiring either a lot of overhang of the empty bounding box or using a frame or other method to crop. Just cannot understand why it comes in with the strange bounding box. I also have an RGB version of this same graphic created at the same time and it places just fine. Don't know if the error is in APub or APhoto, other than it opens and looks fine in APhoto. I did just try Placing it in a 1.7.3 ADes new doc and it does place with an A4 bounding box, so maybe this is a problem with APhoto???

Keep getting bad output of a linked ADes graphic in the RC. I've tried linking to the ADes version and an eps export version from ADes with the same results. The ADes file is cmyk and was created importing a client's pdf. It reproduces fine when exported as a Digital Small but not with x4. Not sure where the issue is. Exports fine in 1.7.3. Think you may already have these files but can upload any you might not be able to locate.

Not fixed in b584 RC1