dhis2-devs team mailing list archive

[Jim Grace <jimgrace@xxxxxxxxx>]

Hi Victor,

Thanks for pointing this out. The "default" dataelementcategoryoption
should also have a null userid. I have now updated the trunk code to check
for this, and also updated the latest versions of 2.18 and 2.19. Hopefully
this will avoid further errors of this type (if people use the latest
code.) Setting publicaccess to "rw----" is still fine, but shouldn't be
necessary with the latest code.

Thanks for your help in solving this.

Cheers,
Jim


On Fri, Jun 12, 2015 at 10:00 AM, Victor Garcia <vgarciabnz@xxxxxxxxx>
wrote:

> Hi Jim,
>
> thanks for the explanation. To verify if it was a configuration error,
> we have created a fresh dhis instance for versions 2.18 and 2.19, and
> in both cases the initial value of publicaccess for "default"
> dataelementcategoryoption is "------". Maybe it has been disconfigured
> at some time.
>
> It is great to know that this change is safe and solves the problem. Thank
> you!
>
> Víctor
>
> On 12 June 2015 at 13:55, Jim Grace <jimgrace@xxxxxxxxx> wrote:
> > Victor, thank you for the very good analysis. Do you know how your
> "default"
> > dataelementcategoryoption came to have publicaccess of "------"? I would
> > expect this to be a configuration error. Your fix sounds right.
> >
> > The SQL code you refer to is critical when using a non-default category
> > combination for the dataset. These category combinations can be used for
> > projects, funding contracts, etc. Then it is important for users to
> approve
> > data only where they are authorized -- only where the category option is
> > visible to the user. For data sets with the default category combination,
> > the default category option should be visible to the user.
> >
> > Lionel, can you please check to see if your dataelementcategoryoption
> with
> > name "default" also has a publicaccess of "------"? If so, please change
> the
> > publicaccess value to "rw----", to see if that solves your problem.
> >
> > Cheers,
> > Jim Grace
> >
> >
> > On Thu, Jun 11, 2015 at 1:30 PM, lionel ruberintwari <ruberlio@xxxxxxxxx
> >
> > wrote:
> >>
> >> Thanks for all your help, the bug is related to java code and it's been
> >> noticed to DHIS community in order to create a bug fix and release
> >> another war file. From my side i am limited to a BAO dashboard. Thanks
> >> once again and we are awaiting for the release of this war file
> >>
> >> --
> >> You received this bug notification because you are a member of DHIS 2
> >> developers, which is subscribed to DHIS.
> >> https://bugs.launchpad.net/bugs/1464211
> >>
> >> Title:
> >>   validation not relevant
> >>
> >> Status in DHIS 2:
> >>   New
> >>
> >> Bug description:
> >>   using DHIS2 2.18 version, users with validation data accounts are
> >>   experiencing error saying "validation not relevant" but users with
> >>   "superuser account" can proceed with validation data.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/dhis2/+bug/1464211/+subscriptions
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~dhis2-devs
> >> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~dhis2-devs
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dhis2-devs
> > Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dhis2-devs
> > More help   : https://help.launchpad.net/ListHelp
> >
>