Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

lexicalEditor - localized richText in a BlocksFeature does not get returned from the API #6455

Closed
HarleySalas opened this issue Apr 29, 2024 · 3 comments · Fixed by #6489
Closed

lexicalEditor - localized richText in a BlocksFeature does not get returned from the API #6455

HarleySalas opened this issue Apr 29, 2024 · 3 comments · Fixed by #6489
Assignees
@AlessioGr
Labels
v3

Comments

@HarleySalas
Copy link
Contributor

HarleySalas commented Apr 29, 2024 •
edited
Loading

When using the BlocksFeature from lexicalEditor, if you put any richText within your blocks, while localized, the data is saved fine, but the fields are not present in the api response. (both nested blocks and non-nested blocks) Please note, that you must have localization with multiple languages in your payload.config.ts in order to observe the issue.

Here is a reproduction
@HarleySalas
Copy link
Contributor Author

Is there any ETA, or information that can be provided about this issue @AlessioGr? I would be really grateful, as it'd help me arrange my schedule more easily; I have a couple of projects halted due to this, unfortunately.

@denolfe denolfe transferred this issue from payloadcms/payload-3.0-demo May 22, 2024
@denolfe denolfe added the v3 label May 22, 2024
@AlessioGr AlessioGr mentioned this issue May 24, 2024
Merged
11 tasks
@AlessioGr AlessioGr linked a pull request May 24, 2024 that will close this issue
fix(richtext-lexical): localized sub-fields were omitted from the API output #6489
Merged
11 tasks
denolfe pushed a commit that referenced this issue May 24, 2024
@AlessioGr
fix(richtext-lexical): localized sub-fields were omitted from the API…
7a76814 
… output (#6489)

Closes #6455. Proper localization support will be worked on later, this
just resolves the issue where having it enabled not only doesn't
localize those fields, it also omits them from the API response. Now,
they are not omitted, and localization is simply skipped.
@AlessioGr
Copy link
Member

Fixed in #6489. Fields no longer get omitted from the API response. Proper localization support will be worked on soon

@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 7, 2024

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AlessioGr AlessioGr

Labels
v3
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(richtext-lexical): localized sub-fields were omitted from the API output payloadcms/payload
3 participants
@denolfe @HarleySalas @AlessioGr