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 The Request Failed to Pass Security Check | Event Espresso - Staging Server
I’m in the process of trying to update the individual “Attendee Ticket Fees” in “Edit Attendee Data” and get the error message. The Request Failed to Pass Security Check
We originally charged tax for our camps and now we aren’t. I issued refunds in PayPal and I want to go back and change the payment amount and the actual “Attendee Ticket Fee”. If it is a single attendee transaction there are no issues. However, if there are multiple kids registered for different camps, but paid for the camps with one payment, it only allows me to edit the “Primary Attendees” price. All others I get the error message. I tried logging out and back in and still won’t allow changes to the additional attendees.
How can this be done. It’s very important that the data match what the actually price and what was actually paid for the camp
We are working on a permanent fix for this, but as a temporary fix you can go into includes/admin-reports/edit_attendee_record.php and comment out line 61, so that it reads:
// wp_die( $failed_nonce_msg );
Viewing 1 reply thread
The support post ‘The Request Failed to Pass Security Check’ 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.