** Changed in: dhis2
Status: New => Fix Released
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1218358
Title:
category-deletion-deletes-category-options
Status in DHIS:
Fix Released
B
Dear Ant/Adolphe,
There is a known issue which stops the upgrade to work well. It results in
the systemsSettings not loading.
The fix is to directly remove SMS_CONFIG row or any similar rows from the
systemsetting table by issuing
delete from systemsetting where name='SMS_CONFIG';
NB: Do the abo
Dear Adolphe,
We have the same issue and I have reported a bug - 1593574. The problem can
be replicated in play.dhis2.org and Markus Bekken is aware of the issue and
attending to it.
Regards
Ant
On 16 June 2016 at 19:21, Kamugunga Adolphe wrote:
> Dear all,
>
> I am upgrading my local instance o
Public bug reported:
After upgrading to 2.23 build 22982 the tracker program completes the
registration, but on the programstage data entry screen the system just
hangs. This can be replicated on play.dhis2.org.
** Affects: dhis2
Importance: Undecided
Status: New
--
You received t
Chrome
Calle
On 17 Jun 2016 12:44 a.m., "Jan Henrik Øverland" wrote:
> Hi Calle,
>
> Which browser are you using? I know there has been some IE related issues
> that are being fixed these days.
>
> Jan
>
> On 16 June 2016 at 23:54, Calle Hedberg wrote:
>
>> Hi
>>
>> We have a national instance
Yeah, it should have rolled back.. so it partially deleting something? I
don't think our `deletion handlers` does everything in the same
transaction.. so it won't do a proper rollback..
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Fri, Jun 17, 2016 at
Hi
We have a national instance for ART data that works as expected when
running on my laptop (pg 9.5.3, Java 8.0.91, tomcat 8.0.32, war file from
today), and we ran it without problems on a local training server setup
last week.
The database was moved to one of our many servers earlier today, but
Dear Morten,
Thank you for your quick reply on my query. This is very helpful.
Lungo
From: Morten Olav Hansen
To: Juma Lungo
Cc: dhis2-devs
Sent: Thursday, June 16, 2016 4:58 AM
Subject: Re: [Dhis2-devs] Metadata import from 2.18 to 2.23
Hi Juma
>From 2.18 to 2.23 there have been
Hi Morten,
this test case expects a failure(500) when deleting the admin user. The
problem is that something is being deleted, once the user is not allowed to
authenticate again. Please see log attached. Basically I was expecting the
transaction to rollback and keep database state.
BR,
Paulo
O
Hi Paulo and Morten,
Please see my earlier mail from today where I did a similar case with a
user, but via the UI.
https://lists.launchpad.net/dhis2-devs/msg45471.html
which I think basically does the same thing. Not sure. Maybe you can point
us to the exact test Paulo?
Morten, this is a quite c
Paulo,
I think what you expect is that the user is deleted. That will not happen,
maybe 2.27.
Pleases make sure Jason is feeling you actual cases we can fix.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 11:44 PM, Paulo Grácio
wr
Dear all,
I am upgrading my local instance on ubuntu 14.04LTS from dhis2.22 to 2.23.
The server seems to start correctly , i can use other apps but when i
tried to access tracker capture app it stops and doesn't show anything up.
Checking from Developer tools here is what it displays this erro
I have created a test case that tries to delete the default admin user. I
get back a 500 with the web message payload, but looks like something is
being delete because after that I can't login into the application with
that user and also http://localhost:8085/api/users?query=admin returns an
empty
Ok, great. We like to turn off some of this Jackson magic as most of the
time you don't really want to expose all fields/getter (unless you have a
very strict DTO)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 7:31 PM, Anilkumar Kod
Hi Morten,
We identified the problem and found solution as below.
*Solution :*
As you implemented disabling GETTERS and SETTERS in
for deserializing, the same way we need to disable while serializing as
well.
Thank you so much for your help
Regards,
Anil
On Thu, Jun 16, 2016 at 5:24 PM, Anil
Hi
If I was you I would use RenderService, this will have a properly
pre-configured object mapper. When you just do new ObjectMapper() it uses
all the defaults, which are incompatible with DHIS 2 (specifically it
enabled auto-discovery)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of
Sorry Morten, executeAnonymousEventPush which we build for pushing
anonymous event data, When we are getting events(which does not have valid
and coordinateString field ) and when we are passing that to
to write to request, at the time this payload was building.
Any idea why are we getting thos
On Thu, Jun 16, 2016 at 6:02 PM, Anilkumar Kodi
wrote:
> executeAnonymousEventPush
What is that?
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to :
It got added when we are serializing and sending request in the
executeAnonymousEventPush.
On Thu, Jun 16, 2016 at 3:34 PM, Morten Olav Hansen
wrote:
> Right, but I don't see why you have valid in the payload to start with?
> normal event export will not include this
>
> --
> Morten Olav Hansen
Thank you Ranga,
Ours is web based and data managers need to use computers, we would like
know how we can exploit the similar functionality from normal instance
relying on internet.
Regards
*Adolphe Kamugunga*
*MIS Technical Advisor*
Mobile: +250 788 740 578
Email:kaa...@gmail.com
Skype: ka.ado
Right, but I don't see why you have valid in the payload to start with?
normal event export will not include this
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 4:52 PM, Anilkumar Kodi
wrote:
> Hi Morten
>
> This is related to the
Hi Morten
This is related to the coordinate value itself.
Please see this event payload thats getting posted to /api/events (POST).
{"program":null,"programInstance":null,"events":[{"event":"tiqYSyQER6a","status":"ACTIVE","program":"MR7cTxF25lM","programStage":"f8hc3X0zYQ7","enrollment":null,"enr
When attempting to delete a user (in this case, the user "system" from the
SL demo database) (revision 23317) through the UI, we get this rather
nasty stack trace and then a "Deleting" message through the UI.
http://pastebin.com/TvJDFEtz
It appears actually the user is deleted, but not 100%,
Here is a quick fix. There is need for an SMS gateway to be set for all the
conditions for sending messages/SMS to be true.
Just go to Mobile Configuration and add a fake generic http gateway (does not
need to be real).
See line 47 of this file:
http://bazaar.launchpad.net/~dhis2-devs-core/dhis2/
It will return same status as before (500) but now it will return a web
message payload with info (from hibernate)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 3:01 PM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> I gue
Dear Lars/ Mike,
I have found a quick fix. There is need for an SMS gateway to be set for
all the conditions for sending messages/SMS to be true.
Just go to Mobile Configuration and add a fake generic http gateway (does
not need to be real).
See line 47 of this file:
http://bazaar.launchpad.net/~d
http://localhost:8085/api/users/URq9lLcM8ID
204 NO CONTENT
The server has successfully fulfilled the request and that there is no
additional content to send in the response payload body.
On Thu, Jun 16, 2016 at 9:24 AM Morten Olav Hansen wrote:
> 204? for which endpoint? that doesn't sound righ
I guess the scenario we need to test is for users which CANNOT be deleted
for whatever reason. This is a bit more difficult to test, but should be
able to be done with the "system" user .There are a whole slew of objects
which are attached with FK references to userinfo, so it should be pretty
easy
Right, so the user was deleted? 204 is expected for that. It's only for
server errors I have changed
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 2:26 PM, Paulo Grácio wrote:
> http://localhost:8085/api/users/URq9lLcM8ID
>
> 204
204? for which endpoint? that doesn't sound right :)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Thu, Jun 16, 2016 at 2:22 PM, Paulo Grácio wrote:
> Great, getting a 204.
>
> On Thu, Jun 16, 2016 at 8:39 AM Morten Olav Hansen
> wrote:
>
>> Hibernat
Great, getting a 204.
On Thu, Jun 16, 2016 at 8:39 AM Morten Olav Hansen wrote:
> Hibernate exception should now be caught, and a web message sent back,
> please try it out. Also added a new default exception handler, which
> unwraps the message and sends back to the user (full stack trace is st
31 matches
Mail list logo
