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
The URL (/dashboard/my/works/page/2) stood out to me as odd... typically, instead of seeing /page/2 used for pagination, I've seen it like ?page=2.
I think the page parameter itself may be related to the root cause of the issue. Removing that param using a debugger, it appeared as though I had access like normal.
This bug was originally reported by / investigated for PALNI/PALCI's Hyku for Consortia Hyku project (Hyrax version: v3.4.2)
The text was updated successfully, but these errors were encountered:
I could not recreate this problem in Hyrax 5.0.0 on https://dev.nurax.samvera.org/. I was able to select works from the second page of my works list and add them to the selected collection without any errors. I did this twice and it worked both times.
Descriptive summary
Version: hyrax-v3.5.0
As an admin, when I attempt to deposit a work into an existing collection, I see the following message:
This behavior ONLY happens on pages 2+ of works in the admin dashboard. Selecting a work from the first page of results will succeed.
Screenshots
Rationale
🐛🥾
Expected behavior
When I attempt to add any work(s) from pages 2+, they should deposit into the collection successfully.
Actual behavior
When I attempt to add any work(s) from pages 2+, I see a message saying I don't have access, even when I am supposed to.
Steps to reproduce the behavior
Test Collection
Test Collection
Add existing works to this collection
Next
Select
checkbox next to any workAdd to collection
button at the top of the list1 Running the script below in a rails console might be helpful
Create many works quickly
Related work
Notes from initial investigation (bkiahstroud)
The URL (
/dashboard/my/works/page/2
) stood out to me as odd... typically, instead of seeing/page/2
used for pagination, I've seen it like?page=2
.I think the
page
parameter itself may be related to the root cause of the issue. Removing that param using a debugger, it appeared as though I had access like normal.This bug was originally reported by / investigated for PALNI/PALCI's Hyku for Consortia Hyku project (Hyrax version:
v3.4.2
)The text was updated successfully, but these errors were encountered: