-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Node Permissions appear to be broken in 6.1.3 #3073
Comments
Ha, never mind, found it! |
Yes, if you use flex (or update the recipes through flex) you might get an update on the kunstmaan_node config as we disabled it by default. It should work fine after you enable it again, if you encounter any bugs feel free to open a new issue! |
Actually we think there is still an issue with permissions.
|
It seems to be an incompatibilty in |
Thanks @acrobat
And we are using the new 5.3/4 system with the old FOSUserBundle removed. |
Can you try to downgrade |
We couldn't get Kuma 6.1 working with Symfony 5.4, every time we tried logged in it complained about not being able to find a password hasher for the user (so we may be missing some config there too). For now setting |
Hi @acrobat we have got our sites working on S5.4 now. As I suspected we were missing some config and some bundle versions were out too. |
Great to hear! I've also added a fix for symfony 5.3 and security-acl 3.3.0 so that shouldn't happen on other projects (symfony/security-acl#106) |
Hi, we have recently been updating some of our sites and have just noticed that for every site that we have upgraded to from 6.1.2 to 6.1.3 the permissions for pages appear to be broken.
On the front end all pages that previously required a user to be logged in with a specific permission become viewable by anonymous users and in the admin area the Permissions tab for each node/page has gone and all pages appear to be editable by all users regardless of permission group.
Returning the site back to 6.1.2 fixes permissions again for our sites.
Is there some configuration that has changed or have we missed something while upgrading?
Symfony 5.3
PHP 8.0
The text was updated successfully, but these errors were encountered: