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
Editing Name, Email: An Error Occurred. The request failed to pass a security... | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Editing Name, Email: An Error Occurred. The request failed to pass a security…

Editing Name, Email: An Error Occurred. The request failed to pass a security…

Posted: August 16, 2013 at 3:40 pm

Viewing 7 reply threads


Kevin Kent

August 16, 2013 at 3:40 pm

When attempting to edit the name, email or other fields in the basic question group I am receiving this message:

“An Error Occurred. The request failed to pass a security check.”

After reading other posts, I logged in and out and still am receiving the same message. I am using 3.1.34.1.P and the latest version of WordPress.

http://www.flaffa.org/event-registration/


Josh

August 16, 2013 at 4:01 pm

Hi Kevin,

It may help to clear the browser or use a different browser.

If all else fails you can bypass the security check until we get this straightened out. If you edit includes/admin-reports/edit_attendee_record.php and comment out the three lines that say:

wp_die( $failed_nonce_msg );

I see them on lines 61, 148, and 195. They can be changed to:

//wp_die( $failed_nonce_msg );


Rob Mougey

August 31, 2013 at 12:07 pm

I am having the same problem, although it is only happening if I try to edit info for an additional attendee – editing the primary registrant seems to work fine.


Dean

  • Support Staff

September 2, 2013 at 12:41 am

Hi Rob,

Have you tried Josh’s workaround? What version of Event Espresso are you using?

Edit: Rob can we carry on this conversation on your thread http://staging.eventespresso.com/topic/error-when-modifying-registrant-fields/#post-57479

  • This reply was modified 11 years, 4 months ago by Dean.


Aaron Jones

September 17, 2013 at 2:18 pm

Have we found an answer for this problem yet? I am also having this issue when editing attendee fields primary or additional either one.


Josh

September 17, 2013 at 3:02 pm

Hi there,

Currently the work around is to disable the security check on line 195 of edit_attendee_record.php where it says:

wp_die( $failed_nonce_msg );

you can change it to:

// wp_die( $failed_nonce_msg );


Aaron Jones

September 17, 2013 at 3:51 pm

the work around did not work for me..


Aaron Jones

September 17, 2013 at 3:54 pm

Never mind I had more instances that I missed thanks Josh..

Viewing 7 reply threads

The support post ‘Editing Name, Email: An Error Occurred. The request failed to pass a security…’ 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.

Event Espresso - Staging Server