I am using tracker Version: 2.24, Build revision: e2f8d0e, Build date: 2016-10-13 06:20. I have configured a three stage program with registration which is giving the problemlisted below.
After clicking complete button on the enrollment or refreshing/logging out of the system, the incident dates of all program stages changes to some strange dates as seen in the screenshot below. The calendar is set to ISO 8601 with date format set to dd-MM-yyy.
Is this a known problem with this version or are there any settings which are not properly set up?
Hi David,
what is the time zone of the server? This is a known bug when you have a time zone different than UTC.
Markus
···
20. okt. 2016 kl. 09.31 skrev David Itana <ditana@hispna.org>:
Dear DHIS community
I am using tracker Version: 2.24, Build revision: e2f8d0e, Build date: 2016-10-13 06:20. I have configured a three stage program with registration which is giving the problemlisted below.
After clicking complete button on the enrollment or refreshing/logging out of the system, the incident dates of all program stages changes to some strange dates as seen in the screenshot below. The calendar is set to ISO 8601 with date format set to dd-MM-yyy.
Is this a known problem with this version or are there any settings which are not properly set up?
I am using tracker Version: 2.24, Build revision: e2f8d0e, Build date: 2016-10-13 06:20. I have configured a three stage program with registration which is giving the problemlisted below.
After clicking complete button on the enrollment or refreshing/logging out of the system, the incident dates of all program stages changes to some strange dates as seen in the screenshot below. The calendar is set to ISO 8601 with date format set to dd-MM-yyy.
Is this a known problem with this version or are there any settings which are not properly set up?
The server time zone is GMT +2. On the second response, all data in the instance were deleted and upon testing the same is still happening.
I remember this bug as it affected one of my event capture instances. This was however resolved on version: 2.24, Build revision: 23573, Build date:2016-08-18 12:11.
The problem is, that version has a different bug which affects program rules on attributes. This was resolved a week or two ago which gave birth to Version: 2.24, Build revision: e2f8d0e, Build date: 2016-10-13 06:20 . My suspicion is that when the program rule bug was handled, the date related bug came back.
Apart from changing the server time, can the developers look at fixing this again as it is on the above mentioned version?
Kind regards,
David
···
also, make sure calendar setting is not changed once data is collected.
I am using tracker Version: 2.24, Build revision: e2f8d0e, Build date: 2016-10-13 06:20. I have configured a three stage program with registration which is giving the problemlisted below.
After clicking complete button on the enrollment or refreshing/logging out of the system, the incident dates of all program stages changes to some strange dates as seen in the screenshot below. The calendar is set to ISO 8601 with date format set to dd-MM-yyy.
Is this a known problem with this version or are there any settings which are not properly set up?