-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Join Field Forbids Default Access Control from Related Collections #9974
Comments
If I'm not mistaken here I believe this will be fixed by #9971 and the issue was not passing a |
You're right, patching it works correctly now. I should have looked closer at the previous pull requests. Thank you! |
Thanks for opening an issue. I caught this one too late yesterday to get it into the release. I also found that join field e2e tests were not running in CI which would have caught this. Now it is included and passing https://github.com/payloadcms/payload/actions/runs/12330014124/job/34415043646?pr=9971 as expected. |
Can confirm - will have to downgrade to 3.6.0 while this is fixed. |
In PR #9930 we added `overrideAccess: false` to the find operation and failed to pass the user. This caused #9974 where any access control causes the edit view to error. The fix was to pass the user through. This change also adds Join Field e2e tests to the CI pipeline which was previously missing and would have caught the error.
Closing this issue, we'll get it out soon! |
This issue has been automatically locked. |
Describe the Bug
Related to #9930. Fixed by #9971.
Fetching a document in the admin panel with a
join
field with default access will result in adoc
undefined on the client-side andForbidden
in the console logs on the client side and server side.Link to the code that reproduces this issue
https://github.com/davliang/payload/tree/issue/join-permissions
Reproduction Steps
pnpm install
to install dependenciespnpm dev _community
to start the admin panelhttp://localhost:3000/admin
All Posts
(Just click save in the form.)Which area(s) are affected? (Select all that apply)
area: docs, area: ui
Environment Info
The text was updated successfully, but these errors were encountered: