dhis2-devs team mailing list archive

["Dave Palmer \(MSI\)" <david.palmer@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

After using the API to update the JSON of an event, which contained
updates to that events coordinates, the maps seemed to remember the old
value of the event coordinates.

However, if I updated the event layer to filter for a different
(shorter) period, the coordinates would display correctly.

This was replicated in v2.20 and v2.21, in various browsers and after
clearing browser caches.

Attached is screenshot showing the event layer filtered for 2015-11-15
to 2016-01-01 and displaying the correct coordinates. However, when
filtered for 2015-11-15 to 2016-02-15 the old details of the event
showed. Note - Everything looks fine in the 'event capture' app.

I've also attached what comes back via the API, which again looks
updated correctly for event LHuP6QuP83x

** Affects: dhis2
     Importance: Undecided
         Status: New

** Attachment added: "screenshots"
   https://bugs.launchpad.net/bugs/1545843/+attachment/4572336/+files/Archive.zip

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1545843

Title:
  Maps do not show updated event coordinates correctly

Status in DHIS:
  New

Bug description:
  After using the API to update the JSON of an event, which contained
  updates to that events coordinates, the maps seemed to remember the
  old value of the event coordinates.

  However, if I updated the event layer to filter for a different
  (shorter) period, the coordinates would display correctly.

  This was replicated in v2.20 and v2.21, in various browsers and after
  clearing browser caches.

  Attached is screenshot showing the event layer filtered for 2015-11-15
  to 2016-01-01 and displaying the correct coordinates. However, when
  filtered for 2015-11-15 to 2016-02-15 the old details of the event
  showed. Note - Everything looks fine in the 'event capture' app.

  I've also attached what comes back via the API, which again looks
  updated correctly for event LHuP6QuP83x

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1545843/+subscriptions