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

CP navigation preference is not applied to group roles #7565

Closed
aerni opened this issue Feb 17, 2023 · 1 comment · Fixed by #8957
Closed

CP navigation preference is not applied to group roles #7565

aerni opened this issue Feb 17, 2023 · 1 comment · Fixed by #8957

Comments

@aerni
Copy link
Contributor

aerni commented Feb 17, 2023

Bug description

The CP Navigation preference is not applied if a user is part of a group that has that role assigned. The preference is only applied if you directly assign the role to a user.

How to reproduce

  1. Create a user
  2. Create a role
  3. Create a group
  4. Assign the role to the group
  5. Assign the group to a user
  6. Customize the CP Navigation for the role
  7. Login with the user
  8. You will see the uncustomized CP navigation

Logs

No response

Environment

Environment
Application Name: gomagazin
Laravel Version: 9.52.0
PHP Version: 8.1.13
Composer Version: 2.5.0
Environment: local
Debug Mode: ENABLED
URL: gomagazin.test
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single, sentry
Mail: smtp
Queue: redis
Session: file

Statamic
Addons: 8
Antlers: runtime
Stache Watcher: Enabled
Static Caching: Disabled
Version: 3.4.4 PRO

Statamic Addons
aerni/advanced-seo: 1.4.0
aerni/livewire-forms: 7.0.1
aerni/social-links: 3.0.3
aryehraber/statamic-impersonator: 2.4.1
jacksleight/statamic-bard-texstyle: 2.1.0
jonassiewertsen/statamic-livewire: 2.11.0
spatie/statamic-responsive-ima

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

runtime (new)

Additional details

No response

@lopadz
Copy link

lopadz commented May 25, 2023

Yep. On 4.3.0 and this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants