To reproduce try to create a Data Provider, say DataLad type, yet miss a mandatory field (such as name or DataLad url) to trigger form validation errors. Using already existing provider name would work too.
Expected: the type persist on the form
Observed: type changes (on the production to Loris provider, on my machine Carmin provider)
Note: few less important field, such as "Files can be browsed only by members of this project (browsable DPs only)" field seems to lost, but this should rather go to another issues
This form is admin/manager only, yet
an admin user would assume that when he entered data, it persist, or at he least does not get altered.
To reproduce try to create a Data Provider, say DataLad type, yet miss a mandatory field (such as name or DataLad url) to trigger form validation errors. Using already existing provider name would work too.
Expected: the type persist on the form Observed: type changes (on the production to Loris provider, on my machine Carmin provider)
Note: few less important field, such as "Files can be browsed only by members of this project (browsable DPs only)" field seems to lost, but this should rather go to another issues
This form is admin/manager only, yet an admin user would assume that when he entered data, it persist, or at he least does not get altered.