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
Filling in an (invalid?) embargo date creates an internal server error and thereafter the record draft is broken.
Steps to Reproduce
Go to: Record draft
Fill in all required fields (meta-data-only, need a doi, ...)
Add Embargo date "0201-01-01"
Save record
See "Internal server error" banner
Leave page
Find your draft in your records overview
Click on it
Get "Internal server error" page
Expected behavior
Wrong embargo date inputs shouldn't break the record (draft)
Additional context
If the record was already published, you add then an invalid embargo-date the record is fine, but the "edit"-Button isn't working anymore "The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application."
How did I get to this date:
There is a text field above the embargo-date: "On ??? ..."
which changes with the input: "On Invalid DateTime ..."
when entering 0200 it shows a valid date: "On January 1, 200 ..."
and I saved one of these "valid dates"
for people with admin-rights on the demonstrator instance:
Package version (if known): v12.0.5 demonstrator instance - https://inveniordm.web.cern.ch
Describe the bug
Filling in an (invalid?) embargo date creates an internal server error and thereafter the record draft is broken.
Steps to Reproduce
Expected behavior
Wrong embargo date inputs shouldn't break the record (draft)
Additional context
If the record was already published, you add then an invalid embargo-date the record is fine, but the "edit"-Button isn't working anymore "The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application."
How did I get to this date:
for people with admin-rights on the demonstrator instance:
The text was updated successfully, but these errors were encountered: