F

4 Messages

 • 

100 Points

Thu, May 27, 2021 1:19 PM

Files not compatible with older versions (after update to 22.4.1)

Hello,

after updating to 22.4 / 22.4.1 and slightly modifying (just changing layer positions and saving) some of our old .psd and .pdf files created with 22.0 version, they are suddenly not compatible with any older versions of photoshop. When trying to open it with an older version (22.0) this error shows: This document contains unknown data which will be discarded to keep layers editable. To preserve the original appearance instead, choose Flatten to load composite data as flattened image. 

Is there any way to solve this without creating new files or downgrading? Could it be fixed in a new version? We have a lot of such files, they have smart objects (without filters, styles..) and a lot of data sets and all of them suddenly stop working for older versions. We tried deleting layer by layer to find our which ones are creating problems. The ones we found problematic are:

1. all smart layers/objects

2. a group of rectangular shapes with an fx of stroke + color overlay

3. Three pixel variables.

EDIT: grammar

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

5 m ago

Do the files actually change appearance if you keep the layers?

4 Messages

 • 

100 Points

No, they remain the same. But the error is really annoying as designers usually open hundreds of this pre-made files per day. 

Creating the same new file from scratch in 22.4.1 works fine.

Copying layers from an old file to the new file creates same error. 

(edited)

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

I am able to repro #2, but #1 smart object layers don't trigger it for me. I don't understand #3 completely. I created some pixel variables and a dataset but can't repro. Can you post files for case #1 and case #3 and I can check with engineering what changed. I think I know what changed with shapes (more 'smart shape' data) but not aware of other changes.

(edited)

Sr. Product Manager, Adobe Digital Imaging

4 Messages

 • 

100 Points

Ok, bellow you can download file containing all of problems together and as separate files. Funny enough I can not replicate the smart object problem unless I use the original file which I can not share publicly. The other two problems are still there via copy/paste.

Please let me know once you download

(edited)

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

I have the files. Thanks. Taking a look shortly.

Sr. Product Manager, Adobe Digital Imaging

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

5 m ago

As suspected, Smart Shape in 22.4.1 saves new feature properties in a way that keeps them from getting damaged in round trips from apps that don't recognize them (the shape not being preserved and drawn correctly). Suggestions from engineering:
(1) Have everyone use the same version of Photoshop. Or have all on PS 22.4.1 or newer.
(2) The older versions of PS should work just fine even though the warning happens. However, when brought back into a newer PS (22.4.1 and newer), the Shapes will get washed through logic that attempts to detect and repair any inconsistent Smart Shape data. If it cannot repair that data, it will strip off that extra data. The base Paths will be unaffected, and the document will render correctly, but the Smart Shape will have become just a Path.

4 Messages

 • 

100 Points

Jeffrey thank you for the fast reply. Unfortunately I can not be sure everyone will be on the same version, we use freelancers for lots of man hours.

Just to double check, if we create files from scratch in 22.4.1, will it then be compatible with older and newer versions without the error? We would still use same layers/objects as in example files. Is there any update planned that could fix this? Or are we fuc***?

1 Message

 • 

64 Points

I just discovered this same issue yesterday, and by process of elimination/testing was able to attribute it to the shape tool also. We are unable to have all folks on the exact same version also, so this is a frustrating bug.

5 Messages

 • 

110 Points

2 m ago

same issue. Really annoying.