Closed scherztc closed 2 months ago
Here is where we first experience this render partial error on ingest : http://localhost:3000/concern/images/new?locale=en
The <%= render_edit_field_partial(term, f: f) %>
error is from an input type being called by render_edit_field_partial, as: :multi_value.
From PR#1148: We were having problems with Scholar not recognizing the input type "as: :multi_value". Any time we were attempting to take an input with the "multi_value" format, the app would crash.
"MultiValueInput" is a custom input class created by hydra-editor and present in the version of hydra-editor we are using, 5.0.5. SimpleForm should have been using that class to handle anything with the "as: :multi_value" tags, but it wasn't.
It turns out that Scholar was not loading the input classes from hydra-editor. This PR adds the input classes of hydra-editor to the load path for Scholar, and then specifically requires the "multi_value_input" file. With this addition to the initializers, all of our work types can now successfully use the multi_value format.
Descriptive summary
This test broke when we updated hyrax from version 2.9.8 to 3.6.0
<%= render_edit_field_partial(term, f: f) %>
Expected behavior
I expect that it has something to do with DOI’s. So it might be as simple as fixing a test. It might be part of the DOI refactor. DOI’s are an overwrite area or could be missing metadata
Actual behavior
'' 3) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
5) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
6) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
7) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
8) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
9) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
10) DOIs behaves like doi request creating a work with private visibility mints a DOI for the work and the work can be edited
No reason given
Steps to reproduce the behavior
Related work
Link to related issues or prior related work here.