The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.
As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.
···
-doh
On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:
Hello Jason,
thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?
The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?
Thanks!
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:
The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.
http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war
Regards,
Jason
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:
Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?
–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:
Thanks Jason
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
–
Papa Alioune SOKHNA
**Informaticien **
Spécialité: développement d’application web, mobile et logiciels surs
Tel: +221 77 442 16 22
On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:
Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .
I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.
Best regards,
Jason
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:
Hi Jason,
we just started receiving emails from users reporting the same problem.
Will follow the evolution.
Cheers
–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:
Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:
Hi Papa,
I am able to reproduce this. It is clearly a bug.
I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.
Jan/Lars, could you comment?
Regards,
Jason
–
Papa Alioune SOKHNA
**Informaticien **
Spécialité: développement d’application web, mobile et logiciels surs
Tel: +221 77 442 16 22
On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:
I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .
In attached the screenshots.
–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:
Hi Papa,
Could you be more specific?
December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.
Are you seeing this in the analysis modules for last 52 weeks?
Regards,
Jason
–
Papa Alioune SOKHNA
**Informaticien **
Spécialité: développement d’application web, mobile et logiciels surs
Tel: +221 77 442 16 22
On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:
Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.
Best regards.
–
Papa Alioune SOKHNA
**Informaticien **
Spécialité: développement d’application web, mobile et logiciels surs
Tel: +221 77 442 16 22
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
–