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 So – we can't use both an iPad & an iPhone for ticketing? | Event Espresso - Staging Server
Our site is almost to a point for launch (barring some minor buggy issues I am waiting to hear back about here in the Support forums) and we have an event in two days. So today I am supposed to meet w/ the client to get the iPad & iPhone apps installed on their devices – and as I’m following the documentation, I run across something that I desperately hope is NOT true: roughly translated, I read that if we use the iPad app (and thus have to install the JSON API) then we will not be able to also use the iPhone app b/c it is incompatible w/ the JSON API. Is this true?!?
MY DETAILS:WordPress 3.5.1 / Authorize.net AIM pymt gatewayEvent Espresso 3.1.31.3.P (new installation, we’ve been working to get it all set up)EE Add-Ons In Use: Calendar, Multi-Event Registration, Permissions, Social Media, Ticketing… in addition, these EE-recommended plugins were also installed: WordPress HTTPS, WP Mail From II… and we are using these plugins: Scripts n Styles, Ultimate Coming Soon Page
The information you read doesn’t say that you cannot use the new API with the iPhone.
It’s the other way around, you can’t use the older API with the iPad app. The Event Espresso HD app has been updated to be a universal app, so it will work on an iPhone, iPad, and iPod touch. The HD app uses the new API. The older app uses the older api.
Thank you Josh! You’ve made my day & just saved me a world of headaches!!!
Viewing 2 reply threads
The support post ‘So – we can't use both an iPad & an iPhone for ticketing?’ 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.