(idml issue) placed .ai with "re-enabled" layers

[woefi]

I'm not sure if much Indesign-users are aware, that when placing a PSD or an AI, you can disable/hide layers (I use it mostly for white coloured logos with transparency).

So with my many documents I hope to bring over to affinity, I have the issue, that these disabled backgrounds creep back in my .afpub file. 
This requires some extra-steps to either open it in AI and deleting the background and saving it, or convert the .ai to .afdesign (basically I'd be fine with that in the long run) but an option to choose the visible layers "on import" is still missing. (like you select the page of a multipage-ai)

This is not to be reduced to a sole feature-request – I would say it is required to successfully convert an IDML to AFPub.

 

 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.