Hi There,
I’ve recently migrated to v3.1.1 in hopes of bug fixes but found out that the Date attribute is still buggy. When selecting a date in the calendar, the system overrides the user input and saves the previous day’s date instead. In terms of an example, If I choose 01/31/2020, the CMDBuild system saves it as 01/30/2020 instead.
Can you please look into this?
Hi, i’ve tried to replicate the error but I didn’t manage to, for me the inserting of dates works properly, can you be more specific? Do you get any errors in the console? Is the attribute type Date or Timestamp? Does the date change when you click on the calendar item or when you click on the save button?
Thanks in advance.
Hi,
The attribute is “Date” type and it changes when I hit Save. There isn’t any error in the console, the INSERT query is as it should be and the data stored in the DB is also correct. But in the CMDBuild UI there’s a change.
I’m adding screenshots for reference
Hope this helps,
Sid
Hi, we managed to replicate the issue and we found out that it is related to the timezone handling, I will let you know when the issue will be solved.
Thanks for the report.
The issue has been solved. The fix will be available in the next CMDBuild release (version 3.2).
Thanks
Hi,
Thanks for acknowledging the bug. When can we expect Version 3.2 to be released?
Maybe in December, but more likely in January.
Hi,
Is there any way I can have a workaround temporarily or maybe fix the code myself given that it is opensource? We’re doing a complete overhaul from v2.5.1 to v3.1.1 and the migration is planned for November 1st Week.
Please let me know.
Sid
Hi,
because the issue is related to the difference of timezone between server and client a potential workaround is to have the server running CMDBuild and the clients using it being on the same exact timezone.