You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Restricting default item read on a collection has issues #178
I'm not sure if the issue is a failed refresh (i.e. the group is actually created but is not shown), or if it's a weirder thing when the group is created only through restricting default bitstream access (see the video).
@amadulhaxxani can you check if this is an issue in the 9.x release?
The backend works fine – when you click Restrict, it creates the new group and returns a 201 response.
The problem is in the frontend. After the group is created, the UI doesn't refresh because it's still looking at an old cached response (Anonymous). So the card keeps showing "Anonymous + Restrict" until you manually refresh the page.
Activity
amadulhaxxani commentedon Aug 13, 2026
@kosarko
I looked into this:
The backend works fine – when you click Restrict, it creates the new group and returns a 201 response.
The problem is in the frontend. After the group is created, the UI doesn't refresh because it's still looking at an old cached response (Anonymous). So the card keeps showing "Anonymous + Restrict" until you manually refresh the page.