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.

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

[3.20.0] Unable to view versions after update. #10884

Closed
PP-Tom opened this issue Jan 30, 2025 · 5 comments · Fixed by #10893
Closed

[3.20.0] Unable to view versions after update. #10884

PP-Tom opened this issue Jan 30, 2025 · 5 comments · Fixed by #10893
Assignees

Comments

@PP-Tom
Copy link

PP-Tom commented Jan 30, 2025

Describe the Bug

Image

This is happening when trying to view versions after updating to 3.20.0.

Link to the code that reproduces this issue

Coming Soon

Reproduction Steps

  1. Create a new document
  2. Go to versions
  3. View the version
  4. See error

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

Payload: 3.20.0
Node.js: 22
Next.js: 15.1.6
@PP-Tom PP-Tom added status: needs-triage Possible bug which hasn't been reproduced yet validate-reproduction labels Jan 30, 2025
Copy link
Contributor

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Jan 30, 2025
@AlessioGr AlessioGr added the status: cant-reproduce If an issue cannot be reproduced label Jan 30, 2025
@AlessioGr
Copy link
Member

@PP-Tom I'm not able to reproduce this at all - could you add a reproduction?

@AlessioGr AlessioGr added db: vercel-postgres status: verified If an issue has been reproduced and removed status: cant-reproduce If an issue cannot be reproduced db: vercel-postgres labels Jan 30, 2025
@AlessioGr
Copy link
Member

Just managed to reproduce it - this only happens for localized arrays and blocks

Copy link
Contributor

github-actions bot commented Feb 1, 2025

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 Feb 1, 2025
@github-actions github-actions bot unlocked this conversation Feb 5, 2025
Copy link
Contributor

github-actions bot commented Feb 5, 2025

🚀 This is included in version v3.21.0

@github-actions github-actions bot locked and limited conversation to collaborators Feb 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants