Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 iPad app 1000 attendee limit is too small | Event Espresso - Staging Server
The 1000 attendees/registrations limit in the iPad app is going to be too small for us. We are expecting between 2500-3000 attendees. Could the query limits that are under Settings -> Event Expresso include an additional option for “unlimited” (understanding that we would then have to set the actual upper limit within the EventEspresso WordPress UI)?
Our event is not until August 2014 so this is not super time-critical at the moment, but I think we need something like this to be able to make use of the app…
Related question: What is the difference between an “attendee” and a “registration” as far as the app is concerned?
Cool, thanks Dean. I was kinda surprised that the app even has a limit – since the response can be controlled at the server anyway, I’m not sure what benefit limit in the app provides. I haven’t tried scanning a ticket for someone who was not in the first N records that the app displays, maybe that would still would. But if you’re checking people in manually, looks like you’re basically stuck if the person you want to check in does not happen to appear in that list.
I have created a ticket for the iOS developer to change this. It was originally added for people that were having timeout issues when querying the data from the server.
I am marking this as closed as there is a ticket now to resolve it.
Viewing 5 reply threads
The support post ‘iPad app 1000 attendee limit is too small’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.