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 Api: WP Multisite Get BlogID from EE Endpoint | Event Espresso - Staging Server
I like to retrieve blog_id from blog-path submitted via http-request via input field Espresso Event Endpoint at the Android mobile device.
How to do that? I only found an POST[authentication]-variable in events.php, which has already lost the blog-path information. Can you give me some advice please?
The mobile app’s endpoint URL needs to point to the root directory, which is where the espresso-services folder is installed.
The work around for multi-site in the ticketing add-on documentation is for using one installation of Event Espresso on a single site of a multi-site network.
If you are trying to use more than one installation of Event Espresso on a multi-site network, you might have more success with the new API that you can download from the pre-release channel. You can opt-in to the pre-release channel from your account page by checking the box that appears below the list of plugins on the right column of your account page.
Viewing 1 reply thread
The support post ‘Espresso Services Api: WP Multisite Get BlogID from EE Endpoint’ 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.