hyrax
hyrax copied to clipboard
Create new sub-collection leads to NoMethodError in Hyrax::Dashboard::NestCollectionsController#create_collection_under
Descriptive summary
Clicking "Create new collection as subcollection" gives rise to error page of "NoMethodError in Hyrax::Dashboard::NestCollectionsController#create_collection_under".
Steps to reproduce the behavior
- Go to collection editing page.
- Clicking "Create new collection as subcollection"
- Error page appears
Related issue #5449. Perhaps duplicate but appears to be getting NoMethodError for #create_collection_under instead of #find.
This error is still occurring on nurax-pg:

Steps to reproduce the behavior
- From Dashboard -> Collections create a collection of type "nesting only"
- From Dashboard -> Collections, click the title of the collection
- Click Create new collection as subcollection (this is where the error occurs that is in the screenshot)
@jlhardes i'm confused if this is an issue with nurax-pg
/ valkyrie support, or if it's a base hyrax issue.
i don't think any of the NestCollectionsController
supports valkyrie. AFAIK, this is the only thing not passing the full test suite when using a valkyrie collection model.
this was coming up to the top of my ToDo list, but i'm concerned about taking that work on if the controller is broken against the ActiveFedora branch.
This was from testing nurax-pg so it is valkyrie-specific. I just tested again and the error is still occurring on nurax-pg. Does that help?
@jlhardes and @no-reply I'm taking a look at it again.
@cjcolvar @blancoj I'm still seeing the error (testing on nurax-pg)
The fix hasn't been merged and deployed to nurax-pg yet. I can tag you for retesting once it is deployed.
I was able to successfully create a sub collection within a User Collection type that I had previously created, using the original steps in the ticket description. I am seeing another error when trying to open the All Collections tab within the Dashboard however.

I think this sub-collection issue is fixed. It works for me testing locally on koppie the same as you reported. The All Collections tab on nurax-pg is not working when logged in as an admin user. Testing locally on koppie as an admin user, the All Collections tab is working so it might be something specific to indexing on nurax-pg?
Thanks @jlhardes I was wondering if it was a nurax-pg specific error since it seemed to reference a specific Collection Type id being missing. I'll go ahead and close this one.