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 Can't login to Ticketing App with Wordpress logins | Event Espresso - Staging Server
When trying to login to the mobile ticketing app on an iphone with my WordPress logins, I am getting the error “Sorry, can’t login HTTP?1.1 406 Not Acceptable”
Anybody have any idea why this may be?
Got an event tonight, probably should have tested this earlier!
Yeah it’s all installed and the API is set to public.. It worked fine for us before didn’t have an issue however since we updated and tried again we are having this 406 error..
I’m having the same problem (406 error on login attempt) with the standard app, the HD app works however. I’m running version 2.0.2.p of the API plugin, and the API is set to public.
Would an upgrade to API version 2.0.3 solve this issue?
Not likely. A 406 error indicates a server level issue. You can try contacting your host to see if there has been any changes to the Apache installation. A possible fix is posted in this article:
The support post ‘Can't login to Ticketing App with WordPress logins’ 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.