Hi devs, seeing some strange behaviour in the recent 2.29 builds, including:
fb88d26 from 2018-06-10 06:45
53a6293 from 2018-06-11 09:07
The issue is that for a non-superuser, existing and auto-generated events for tracker programmes simply don’t appear in data entry. Enrolling works fine, but in TC data entry the auto-generated stages are simply not there in data entry, even though the are actually created and stored in the database. Similarly, opening an existing enrolment will not show the existing events. Trying to add new events manually works except if they are non-repeateable and an event already exists.
Investigating, I found that this query (done by TC when it loads an enrolment) returns no events for a non-superuser, which seems to be the problem:
However, this query for the event linked to the above TEI does return the event…:
/api/events/Xz1YweK2pYM.json
The fact that the non-superuser can add events, edit data, access the “invisible” events via the API etc lead me to be leave it’s not a sharing/permission issue OR a permission issue. In fact, it seems to only be this specific query that creates problems:
Hi devs, seeing some strange behaviour in the recent 2.29 builds, including:
fb88d26 from 2018-06-10 06:45
53a6293 from 2018-06-11 09:07
The issue is that for a non-superuser, existing and auto-generated events for tracker programmes simply don’t appear in data entry. Enrolling works fine, but in TC data entry the auto-generated stages are simply not there in data entry, even though the are actually created and stored in the database. Similarly, opening an existing enrolment will not show the existing events. Trying to add new events manually works except if they are non-repeateable and an event already exists.
Investigating, I found that this query (done by TC when it loads an enrolment) returns no events for a non-superuser, which seems to be the problem:
However, this query for the event linked to the above TEI does return the event…:
/api/events/Xz1YweK2pYM.json
The fact that the non-superuser can add events, edit data, access the “invisible” events via the API etc lead me to be leave it’s not a sharing/permission issue OR a permission issue. In fact, it seems to only be this specific query that creates problems: