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
No "XML-RPC Publishing"? | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › No "XML-RPC Publishing"?

No "XML-RPC Publishing"?

Posted: January 6, 2013 at 8:44 am

Viewing 2 reply threads


Mr Scratch

January 6, 2013 at 8:44 am

Hi,

The ticketing documentation (http://staging.eventespresso.com/wiki/espresso-ticketing/#create-tickets) says:

> 1. Enable XML-RPC Publishing
> Event Espresso requires XML-RPC Publishing to be enabled in order to communicate with the iPhone and
> Android apps. To do this navigate to the main WordPress Settings and visit Settings > Writing.
>
> Scroll down to Remote Publishing and check the box beside XML-RPC that says “Enable the WordPress,
> Movable Type, MetaWeblog and Blogger XML-RPC publishing protocols.”

But when I navigate to Settings > Writing, there is no Remote Publishing option or anything like that. Is this documentation up-to-date?


Mr Scratch

January 6, 2013 at 9:00 am

Never mind.

According to the WordPress documentation, “With WordPress version 3.5 remote publishing via XML-RPC became permanently active. ”


Dean

  • Support Staff

    •

January 7, 2013 at 1:40 am

Hi,

Thanks for pointing that out I have updated the documentation accordingly.
Viewing 2 reply threads

The support post ‘No "XML-RPC Publishing"?’ 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 12 years ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server