Skip to content

Restricting default item read on a collection has issues #178

Open

Description

@kosarko
Endangered.Craft.Traditions.-.Brave.2026-08-13.14-03-53.mp4

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?

Activity

  1. amadulhaxxani commented on Aug 13, 2026

    @amadulhaxxani

    @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.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions