Closed miller-design closed 1 month ago
Hey @miller-design, we know this issue and it's already fixed in 3.0. And actually, we got merged this huge PR https://github.com/payloadcms/payload/pull/8468 that ports many fixes, including this. I don't have info when we can release that, but it should be soon.
Hey @r1tsuu, I had saw some similar issues relating to V3 just couldn't find anywhere where it was flagged for V2. Thanks for the update and ill keep an eye out for when this PR is released.
This issue has been automatically locked. Please open a new issue if this issue persists with any additional detail.
Link to reproduction
No response
Describe the Bug
Environment info
payload: '^2.28.0' npm: '10.8.2', node: '20.17.0'
Describe the Bug
When trying to set up translatable fields i was getting an issue where data from the translatable fields were not being saved correctly, i was having issues with content being deleted or overwritten. The issue seemed to boil down to setting the localised option on a group field rather than each individual field in that group like so:
This field was at the start of the collection and then proceeded to have knock on effects and preventing other fields from saving correctly.
When following the payload docs to set up all the necessary steps i came across this message:
Note: Enabling localization for field types that support nested fields will automatically create localized "sets" of all fields contained within the field. For example, if you have a page layout using a blocks field type, you have the choice of either localizing the full layout, by enabling localization on the top-level blocks field, or only certain fields within the layout. - link to doc here
Screen recording of the bug https://github.com/user-attachments/assets/eb6b4a9f-0183-46cf-8c36-8cedd4f8a54c
To Reproduce
Set up your payload config with localization:
next set up a collection
Payload Version
2.28.0
Adapters and Plugins
db-postgres v0.8.5