Hi all,
Using CS5.5 with patch 7_5_2 on a mac.
This doesn't happen on the first page!
Elements on layer 1 in my Indesign master page have moved to layer 2 in my exported pdf?
If I group layer 1 before I export it, it does not happen?
Is this a bug? Anyone else encountered it happening?
Cheers in advance.
OK, I've never seen this, but I don't export a lot of layered PDF becasue I work for print.
Are the objects overridden? Grouped with anything else? Can you show us a screen shot of the object selected (or at least with frame edge showing to identify the layer), and the layers panel for the page in ID, and the perhaps the same page withthe layer turned off in Acrobat?
Here are the images you asked for.
No Groups and no overides. Most of our files are converted legacy builds (CS4) but I've recreated this from scratch in CS5 and get the same result.
We are getting this problem on different build macs and different sites in Asia and Europe!
Indesign screenshot shows the master pages and 2 layers, layer 1 is highlighted.
Page 1 pdf screenshot shows the correct result when layer 1 is turned off.
Page 2 pdf screenshot shows that layer 1 has moved to layer 2.
Indesign screenshot
Page 1 pdf screenshot
Page 2 pdf screenshot
Using file share sites that require membership to download is not a friendly way to share.
I don't have your file, but you mentioned that this only happens with converted files. We get enough reports of strange behavior when converting files to CS5 thaat my standard advice is now to export the file from the original version as either .inx or .idml and open that in CS5 instead. If you can't do that, opent the .indd and immediately export to .idml, then open that and save as .indd with a new name (never overwrite the original version).
I have your file, and I can confirm the behavior in CS5 and CS5.5, and I can reproduce it with a new file of my own as well. I'm 99.999% sure this is a bug -- exported .idml from the files shows the error in CS5/5.5, but not in CS4.
Even more interesting than your observation of the object moving to the second layer is that the object that was on the second layer is now not on any layer at all -- if you hide all the layers it's still visible. I'm not really sure there's a point in trying to report the bug for CS5/5.5 as CS6 is due tomorrow and it's very unlikely to get get fixed in an earlier version, but I'll open a discussion with some other users with contacts onthe engineering team and see if there is any encouragement.
I've not heard anything more, but that's not unusual. I would say that it's not terribly likley to get fixed, though, in CS5 if CS6 works. Most bug fixes are not ported backwards because the time to test in a previous version is expensive and rarely available unless it's a bug that is stopping a large number of users from having any functionality at all (like the recent problem with the update to Lion that crashes multiple versions of ID on new Apple hardware) and because the risk of breaking something else is also high.
North America
Europe, Middle East and Africa
Asia Pacific