Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving an "invalid" embargo date creates internal server error and breaks record draft #2916

Open
ghost opened this issue Nov 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented Nov 19, 2024

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

  1. Go to: Record draft
  2. Fill in all required fields (meta-data-only, need a doi, ...)
  3. Add Embargo date "0201-01-01"
  4. Save record
  5. See "Internal server error" banner
  6. Leave page
  7. Find your draft in your records overview
  8. Click on it
  9. 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 ??? ..."
      image
    • which changes with the input: "On Invalid DateTime ..."
      image
    • when entering 0200 it shows a valid date: "On January 1, 200 ..."
      image
    • and I saved one of these "valid dates"
  • for people with admin-rights on the demonstrator instance:

@ghost ghost added the bug Something isn't working label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

0 participants