|
Stichting Festival Aangeschoten Wild
|
March 23, 2014 at 3:17 pm
Hi EventEspresso,
When preparing for our annual festival (next Friday) and setting up the apps, I noticed that you have switched to a new system. Great to have everything running on the API, although I think it’s a major flaw that the documentation page (https://eventespresso.com/wiki/espresso-ticketing/) not even warns of being outdated, let alone display wrong information.
That remark put aside, I have a few questions.
1) Although you state that the app will throw an error when scanning a ticket for an event other than the one currently selected (https://eventespresso.com/wiki/mobile-apps/, under “? Unsuccesful scans”), I do not get any error or warning.
2) In the API Settings, it is possible to specify the number of attendees downloaded to the device. Although it indeed features a warning that that setting can be overwritten by the device, I have not found an option in the (Android) app to change this limit. If it’s hardcoded (and can clearly NOT be overruled), what’s the point of having this setting? Or, stated differently: what’s the point of hardcoding this into the app software if the API has a default value set up?
3) I have read a few disturbing posts on the forums, such as freezing apps (https://eventespresso.com/topic/event-espresso-app-keeps-freezing-up/). Can you confirm this software to be fully functional (if setup the right way, of course) in all of its aspects? Over a thousand tickets will need to be scanned, so – as they say – failure is not an option.
Looking forward to your quick reply,
Kind regards,
Bram Peerlings
Stichting Festival Aangeschoten Wild
P.S.: I’m running a multi-site installation of WP 3.8.1, EventEspresso 3.1.36.1.P with Ticketing 2.1.p and API 2.1.1.P and have (so far) tested on Android (HTC One, running Android 4.3 and app version 2.0.10).
|
|
Dean
|
March 25, 2014 at 6:00 am
Hi Bram,
Thanks for the feedback regarding the documentation, we are looking to update it in due course.
1) The new app allows this currently.
2) If you are referring to “Also note: the api clients can always override these limits by specifying a “limit” query parameter.” then this is about general API clients, not dpecifically the mobile apps.
The app will base its calls on whatever the API plugin is set to.
3) The ticket is still outstanding, however we have run various test (not thousands in a row though) and not come across any issues. We certainly could not replicate the issue in the forum post you linked to.
Please note that Event Espresso does not formally support multisite installations. As such we cannot guarantee full functionality, especially if network enabled.
|
|
Stichting Festival Aangeschoten Wild
|
March 25, 2014 at 6:06 am
Thanks for your reply, Dean!
1) I’ll check again today, but as stated before I didn’t recieve any warning. Did you maybe issue an update in the last few days that I might have missed?
2) I’ll check again today, but from my earlier tests, the app was stuck at fetching 100 attendees, although the API-limit was set to 1000. Glad to hear that the mobile apps do not overrule this setting.
3) Thanks for the re-assurance. I haven’t checked myself yet, but I trust your testing to the fullest.
Concerning the multi-site installation: the plugin is not Network Enabled, and the apps point to the correct subdomain. Are there any areas in particular in which problems might arise, or problems are known?
I’ll get back to testing right this afternoon: it would be great if you could keep an eye out for updates on this topic today. Thanks in advance!
|
|
Stichting Festival Aangeschoten Wild
|
March 25, 2014 at 7:40 am
Hi Dean,
I have just checked both issues, and nothing has changed so far.
1) We’re selling entrance tickets as well as token vouchers (as two separate events), and when selecting the entrance ticket event in the scanning app, I am still able to scan token vouchers (without any warning whatsoever). Both events are scheduled at the same date and location.
2) I have experimented with both high (1000) and low (1 – 10) settings in all three fields (events/attendees/registrants), but the information displayed in the app is not changing.
This holds for aforementioned HTC-phone. I hope to be able to test on iOS later today, and will get back with my findings there. Until then, any idea what’s causing the above issues? We’re especially interested in solving the second problem.
Thanks, and kind regards,
Bram
|
|
Stichting Festival Aangeschoten Wild
|
March 25, 2014 at 8:26 am
I have just tested on iPhone, and the second issue is resolved there. On other Android phones, it’s not.
Would this indeed confirm that the problem is with the app, and not with the (multisite) installation?
|
|
Josh
|
March 25, 2014 at 9:25 am
Hi there,
It might be an issue with the Android app so I’ve sent a ticket over to the Android developer to investigate.
|
|
Stichting Festival Aangeschoten Wild
|
March 25, 2014 at 3:08 pm
Hi Josh,
Thanks a lot! I hope to hear back from you soon.
Bram
|
|
Stichting Festival Aangeschoten Wild
|
March 25, 2014 at 4:32 pm
Update: (at least) the Android app also seems to accept tickets with a payment status other than completed. I’ll try to check if this is also the case for iOS tomorrow, but (based on the above experiences) would guess it’s not.
Regards,
Bram
|
|
Stichting Festival Aangeschoten Wild
|
March 26, 2014 at 4:04 am
Confirmed that the error ‘This ticket is for another event’ does work in iOS (tested on iPod Touch). Same goes for the error of incomplete payments (as mentioned in my previous post).
Kind regards,
Bram
|
|
Dean
|
March 26, 2014 at 4:31 am
Thanks Bram, I have updated the ticket accordingly so the app developer is aware of the extra info.
|
|
Stichting Festival Aangeschoten Wild
|
April 3, 2014 at 3:45 am
This morning, I recieved a notification of an update of the Android-app. Were you able to fix the issue?
|
|
Dean
|
April 3, 2014 at 5:44 am
Hi,
I checked the ticket and it says that this is now working. The ticket has been marked as completed, so yes it should be fixed in the update.
|
