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
espresso-services or espresso-ticketing folder? | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › espresso-services or espresso-ticketing folder?

espresso-services or espresso-ticketing folder?

Posted: March 19, 2013 at 6:43 am

Viewing 1 reply thread


OREN Coordinator

March 19, 2013 at 6:43 am

Hello
In the docs it shows the folder listed as espresso-services however when I uploaded it via FTP it is espresso-ticketing – is that right? I can’t seem to work out why EE hasn’t picked up the ticketing options yet :(
Thanks
Wes


Dean

  • Support Staff

    •

March 19, 2013 at 6:50 am

Hello,

Espresso services and Espresso Ticketing are separate things. The Ticketing is the add on plugin itself and the Services is the api to enable scanning of the tickets qr codes.

As such you need to download the Ticketing add on from your account page and install it like any other plugin.

For the Services API click here (a download will begin) and download the zip file and extract it and upload the espresso-services folder to the root of your site.

The api is also available here http://staging.eventespresso.com/wiki/espresso-ticketing/#services
Viewing 1 reply thread

The support post ‘espresso-services or espresso-ticketing folder?’ 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 Dean 11 years, 10 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server