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
Network + iPhone/Android Apps | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › Network + iPhone/Android Apps

Network + iPhone/Android Apps

Posted: September 14, 2012 at 10:10 pm

Viewing 0 reply threads


Todd

September 14, 2012 at 10:10 pm

Just looking for some feedback here from anyone else who has run into a similar situation.

Our current setup is this:

  • WordPress Network (ver 3.4.2) with one subsite.
  • We’ve used the Domain Mapping plugin to map a TLD to the subsite.
  • Event Espresso is activated on the subsite
  • Everything is working including purchasing and printing tickets

The only hitch in this whole setup is the iPhone App. Our client would like to have the ability to scan QR codes at the door.

Since the mobile apps use XML-RPC for data retrieval and entry, my assumption is that the espresso-services folder in the root directory acts as a router. Is there any known way to modify the services folder to route to the correct subsite and not just the root site?

Note: This is a custom network installation, where only the one subsite is being created. Frankly, worst-case scenario is we load up a new single WP instance and point the domain there and import what’s been created on the subsite, so I guess this is more out of curiosity to know what’s possible.
Viewing 0 reply threads

The support post ‘Network + iPhone/Android Apps’ 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.

Status: closed

Updated by Todd 12 years, 4 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server