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 Mobile ticketing 404 error | Event Espresso - Staging Server
trying to get the mobile app api to work. on newbeginningschurch.com.au but I keep getting the following error
“HTTP/1.1 404 Not Found”
Any help on this matter would be greatly appreciated.
I have uploaded the espresso service folder to the server, and the folder permissions is 755
XMLrpc is enabled and is on the root location of wordpress (the file is xmlrpc.php, I also tried changing the name to xml-rpc.php)
Info from help support page:
WordPress Version:
3.4.2
PHP Version:
5.2.17
MySQL Version:
5.5.27
Event Espresso Version:
3.1.28.3.P
WordPress Address (URL): http://newbeginningschurch.com.au
Hi Simon, Can you try with the default theme and with no other active plug-ins than Event Espresso?
Testing with the default theme and plugins disabled will help pin down where the problem is. If everything works then you go back and enable your theme and then try it again. If everything still works then you go back and activate each plugin one at a time until you find the one that is causing the breakage. If this doesn’t work, I can next suggest to contact the web hosting provider and check that the server’s configuration doesn’t block the XML-RPC protocol.
Is this a multi-site or a single single installation of WordPress?
Viewing 3 reply threads
The support post ‘Mobile ticketing 404 error’ 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.