Just following up on my query below. As per Alex’s recommendation, I’ve just
had a play with Android Event Capture 0.5.5, and it looks great – is there a
timeline for fixing it (or any version, for that matter) to work with 2.25?
Can you try to use the full object name "dataElementCategoryCombo" instead
of "categoryCombo" and try again. It works on my local.
Need more investigation to understand why the short name does not work
On Mon, Oct 17, 2016 at 9:55 PM, Sam Johnson
Yes its working, export functionality is functional.
On Sat, Oct 15, 2016 at 7:22 PM, Brajesh Murari
> Dear Knut,
> I agree at your point, but i will check it once again tomorrow ie. on sUN
> day morning.
> On Sat, Oct 15, 2016 at 6:44 PM, Knut
My GIS isn't loading also in 2.25. Dhis and tomcat logs don't write any
error but the browser console gave me:
*Uncaught SyntaxError: Unexpecte end of JSON INPUT
*Uncaught SyntaxError: Unexpected end of JSON input VM808:1*
The problem I reported yesterday has actually turned out to be what I think is
a new bug in 2.25, which is stopping XML imports for data elements.
No matter what I do, any attempt at an XML import of data elements seems to
throw the error “DataElementCategoryCombo Missing required
It seems to be memory issue happening in 2.24? If I try the same import
with the same org.units in 2.22, everything works well. With 2.24, I'm
normally getting the follow log message...
* INFO 2016-10-17 14:03:07,531 Org unit cache heated after cache miss
it is working now. Thanks for your quick answer
On Fri, Oct 14, 2016 at 3:22 PM, Nicolay Ramm wrote:
> Hi Jose,
> I just published a new version of the maintenance app for 2.24 where this
> should be fixed (v24.0.31).
> Best regards,
> Nicolay Ramm
On Mon, Oct 17, 2016 at 3:42 PM, Sam Kasozi wrote:
> GIS is failing to load in a new instance of 2.25; not sure if this is a
> bug or whether some pre-configuration needs to happen.
we need some more info, can you check in the browser developer
GIS is failing to load in a new instance of 2.25; not sure if this is a bug
or whether some pre-configuration needs to happen.
Mailing list: https://launchpad.net/~dhis2-devs
Post to :
Well at the end got imported (sometimes throws a memory exception), but it
took more than 1 hour to import 7973 datavalues. It was just a few minutes
in 2.22 with same import and same server.
On Mon, Oct 17, 2016 at 4:29 PM, Jose Garcia Muñoz
> It seems to be memory
Good news! look a way to test and upgrade.
Thanks for Dev Team
2016-10-14 9:24 GMT+01:00 riddy ndoma :
> 2016-10-14 8:52 GMT+01:00 GROUT, Lise :
>> Congratulations to all the team!
>> Really looking forward to diving into this version
I have seen this now in two separate instances, where by there seem to be
multiple configurations in the "configuration" table. Which one is DHIS2
using, and how can there be multiple ones?
-[ RECORD 1 ]-+-
OK, but that's really weird. The 2.24 build from 5 days ago was 138mb
Anybody from the core team have an explanation? I don't want to use the new
version before I know if there are nails in the soup
On 17 October 2016 at 17:31, Dan Cocos wrote:
Maybe - but then why is the 2.25 war file size much small again? It makes
no sense to introduce a new set of libraries at the same time as 2.25 is
releases WITHOUT the same libs.
Let's hope somebody from the core team can throw some light on this when
they sober up ;-)
The idea that this is caused by malicious code is a bit far fetched.
An educated guess:
All of our "bundled" apps are now developed outside of the core code
repository. They are then pulled in at build time and bundled into the
final distribution war-file.
In practice this means that it's
Mail list logo