I tried some cascading questions, repeating group, if functions, sum functions, notes to display sums, and a geopoint question.
There are two things I would like to mention about geopoint question type, tested in laptop.
The search bar in the geopoint question doesn’t seem to work.
In the current version, when a location is clicked, it zooms in to that point,
In the test version when a location is clicked, it zooms out to fit whole world map.
tested in each url.
Don’t know if it’s a beta issue or not. Wanted to mention it.
Best,
Edit:
Tested with cascading questions. Works.
Tested with repeating groups. Works.
Hi @hakan_cetinkaya, thank you for noting the location search issue for geo questions, that has now been resolved — it was just a configuration issue on the testing instance.
Regarding your second point:
In the current version, when a location is clicked, it zooms in to that point,
In the test version when a location is clicked, it zooms out to fit whole world map.
I seem to be getting the same behaviour (zooming out on click) for both the current version in production (2.8.1) and the testing one (3.1.0). Would you mind please sharing your XLSForm so I can try replicating your observation?
Hi @Josh,
first tests ok (with Firefox), including “All Widgets” and some matrices.
Two minor findings, but not caused by your update::
Layout issue (same in ODK Online validator) for select_one with likert appearance
If you move out the cursor, the layout corners get white:
GPS geopoint widget: Ok, difference to ODK Online validator
Search place is working in Enketo (and KoBo Preview)
Search NOT working in ODK Online validator - Preview
Nothing happens here.
As far as possible, the Online validator should not behave differently to KoBo Enketo, as the Online validator is often referenced in the forum as a main test tool for form development.
Print not showing **Required symbol *** (except acknowledge type)
Same problem in ODK Online validator.
This issue might not be related to release 3.1.0, consider splitting to another topic if needed.
I tested a bit more after what you wrote. It seems I always write something in the search bar, so my assumption was the map zooms in when clicked on anywhere. But it seems there are two different behaviours in reality, here is how to achieve each one:
Behaviour 1: Zoom in when clicked
STEP 0: Refresh the page / open for the first time.
STEP 1: Write something in the search bar. (Let’s say Vancouver)
STEP 2: Click on anywhere.
STEP 3: The map zooms in.
This behaviour becomes the main behaviour even if you zoom out, write something else etc.
Behaviour 2: Zoom out when clicked
STEP 0: Refresh the page / open for the first time.
STEP 1: Don’t write anything in the search bar.
STEP 2: Zoom in.
STEP 3: Click on anywhere.
STEP 4: The map zooms out.
Hi @wroos, thank you for your testing! Regarding the point above, if you are referring to searching for geo questions, note that the the ODK validator likely does not have geocoding configured and therefore is unable to resolve the search. It will be up to the ODK team to configure this.
I can’t comment on why those PDF issues are being closed but they are at least aware of it.
Hi @hakan_cetinkaya, thank you for the replication steps and it seems the behaviour is the same for both 2.8.1 and 3.1.0 — although this is likely still worth creating a GitHub issue about.
Thanks, @Josh!
Who might answer this question, please? And we would appreciate that this bug is adressed, please. It should be possible as it is working for acknowledge type (so probably NOT a browser issue).
While the bug was indeed closed on the old kobotoolbox/enketo-express repository, that was only because it was moved (recreated) in the new repository: asterisk * not shown on printout · Issue #130 · enketo/enketo-express · GitHub. That bug remains open. If you have a GitHub account, I’d suggest commenting there to see if anyone has free time or a labor budget that they could invest into solving this problem. Thanks for testing, and I’m sorry this has been a problem for so long.
Hello everyone who’s participated in this testing effort! I first want to say thanks for helping us improve the reliability of the KoboToolbox service. Secondly, I’d like to invite you to try our new public beta instance at https://kf.beta.kbtdev.org/. Using this, you can test more features of Enketo 3.1.0, like submission editing and previews. Please let us know how it goes!
Thanks, @wroos I’ll assume that @Crstm was using the regular, production Enketo and not this beta-testing one, but please correct me if I’m wrong. Either way, we need to pinpoint the behavior (all Android devices, or vendor specific? dependent on the currently active keyboard or the browser? locale specific?) and open a bug on the Enketo repository for this.
Hello @jnm,
Thanks! I was using the last official Enketo (KoBoToolbox) and Collect (ODK! versions on Android Samsung (versions: 11 and 5.0).
As you can see in our posting, it is at least different between (current) Firefox and Chrome/Opera browsers. @Crstm, maybe you can add technical info and screenshots from your tablets, please.
Kind regards - and thanks for continous development
Hello and thanks to everyone who helped test Enketo 3.1.0. If anyone here would like to test Enketo 4.1.1, you may find instructions for doing so at Please help test Enketo 4.1.1.
I’ll assume that 