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

Error: invalid date format in Event dialog #4412

Closed
MisterCodeRalf opened this issue Jun 19, 2023 · 7 comments
Closed

Error: invalid date format in Event dialog #4412

MisterCodeRalf opened this issue Jun 19, 2023 · 7 comments

Comments

@MisterCodeRalf
Copy link

Detailed description of the problem

If one changes the time of an event after clicking the event in the calendar an Error message appears: Error invalid date format received

Expected Behavior

time will change without error message

Steps to reproduce the behavior

  1. generate event
  2. click event
  3. change end time

What eLabFTW version are you using? Visible in bottom right of a page.

latest 4.7

Do you have any idea what may have caused this?

conversion problem in the interaction of the form and the database

Do you have an idea how to solve the issue?

workaraound: just drag drop event in clandar ... works fine

Additional information

No response

@NicolasCARPi
Copy link
Contributor

Hello,

This issue already has been reported to me but I don't manage to reproduce it. I think it has to do with the browser lang. Can you give more info on that please? Screenshots are welcome, too.

@MisterCodeRalf
Copy link
Author

Hi Nicolas,
the browser language is German.

I have made short videos for edge and chrome.

2023-06-19.13-44-02.mp4
2023-06-19.13-47-34.mp4

Best regards

Ralf

@NicolasCARPi
Copy link
Contributor

Great, thank you. I'll look into it.

@NicolasCARPi
Copy link
Contributor

So the issue was not related to the browser lang, but some weird bug where valueAsDate would be null on Chromium (and Chromium based browser like you observed), so I used valueAsNumber it it seems to work fine. When this issue will autoclose, it will be because the code was merged to master, which is generally done before release, so it would be great if you could have a look on the demo website and confirm that it's all good with the new version. The demo gets alpha/beta versions.

@MisterCodeRalf
Copy link
Author

Thank you for your effort. I have just tested the behaviour at demo.elabftw.net (is this the right place?). In Firefox its fine. In chromium and edge it is still present.

@NicolasCARPi
Copy link
Contributor

That's normal. Read again my message carefully. It starts with "When this issue will autoclose", which has not happened yet ;)

@MisterCodeRalf
Copy link
Author

OK, sorry for the confusion. I will test it again when autoclosed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants