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
400 Bad Request | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › 400 Bad Request

400 Bad Request

Posted: August 1, 2012 at 10:03 pm

Viewing 3 reply threads


Kim Schlossberg

August 1, 2012 at 10:03 pm

I think I got the broken group registration fixed, and I tried to fix the https paypal return problems. But now when I try to do a registration and confirm by going to paypal (either auto-redirect of clicking the button) I get this error message:

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

And I still don’t see any attendees marked as “paid” even though I paid for several and got confirmations.


Seth Shoultes

  • Support Staff

    •

August 1, 2012 at 10:23 pm

Can you get to the PayPal website at all (by typing in the address directly)? Sometimes that happens to me and I have to clear the browser cache or restart the browser.

As far as payments not getting updated. Were payments getting updated before now? If so, and nothing has changed. It could be an issue on PayPal’s end. I have heard that PayPal has been having issues over the last 2 to 3 weeks.

Here are some discussions on the matter:

http://quirm.net/2012/07/27/paypal-issues/

https://www.x.com/developers/paypal/forums/instant-payment-notifications-ipn-payment-data-transfer-pdt/ipn-failing-hasn-t-been-changed?page=0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C0%2C1


Kim Schlossberg

August 2, 2012 at 7:22 am

OK – I tried it in firefox and everything seems to be working now. Went back to Chrome, and that test worked. So – either something was fixed over night (if so, thank you!) or restarting the browser did the trick.


Josh

August 2, 2012 at 8:28 am

I’ve had similar issues when testing PayPal with Chrome, usually clearing the cookies/cache will do the trick.
Viewing 3 reply threads

The support post ‘400 Bad Request’ 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.

The original Forum description...

Status: closed

Updated by Josh 12 years, 6 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server