- Issue created by @jaydub
- last update
10 months ago 227 pass - Status changed to Closed: works as designed
10 months ago 7:57pm 29 January 2024 - πΊπΈUnited States jaydub
Ok I looked into this more closely and it looks like the old permission is not dynamically set and our issue was the the Views defined in the old version of the module did not have their access settings automatically updated upon upgrading to the 2.x version. Going to close this for now.
- π§πͺBelgium fernly
Thank you for elaborating.
I had the same issue and even setting the permission right in the View, still didn't work.Solution: there appeared to be 2 Views "Scheduled content" and "Scheduled content revisions" having the same path /admin/content/scheduled. The latter was still configured with the wrong access rule.