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

v15: Granular permissions are empty #17860

Open
PeterKvayt opened this issue Dec 23, 2024 · 2 comments
Open

v15: Granular permissions are empty #17860

PeterKvayt opened this issue Dec 23, 2024 · 2 comments
Labels
affected/v15 area/frontend state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@PeterKvayt
Copy link
Contributor

PeterKvayt commented Dec 23, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.1.1

Bug summary

when you open user group settings there is an error in the console and permissions are empty:

image

This behaviour related to impementation. this.observe can be executed later than render method.

Error in the following file: /umbraco/backoffice/src/packages/user/user-group/workspace/user-group/components/user-group-granular-permission-list.element.ts

Sometimes element.manifest is undefined.

image
This is because this.observe callback can be executed after render method have been triggered.

image

Specifics

No response

Steps to reproduce

  1. Freash umbraco install
  2. Open user section
  3. Open any user group
  4. Refresh user group settings page couple times, and on each time check "Granular permissions" and console errors.

Expected result / actual result

Expected: there are no errors in console and "Granular permissions" is not empty
Actual: there is an error in console and "Granular permissions" is empty


This item has been added to our backlog AB#47493

Copy link

Hi there @PeterKvayt!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@NguyenThuyLan
Copy link
Contributor

You're right @PeterKvayt , thank you for reporting this.
I was able to reproduce it on v15.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected/v15 area/frontend state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

3 participants