|
jferguson
|
August 22, 2013 at 12:44 am
When trying to update an attendee’s name I got the following error: “An Error Occurred. The request failed to pass a security check. Please press the back button on your browser to return to the previous page.” Hitting back and refresh, logging out, tried different browsers and I still get the same message. This only happens when trying to modify a record tied to a multiple registration.
We are using EE Version 3.1.31.B and Multiple Registrations Version 1.0.4
|
|
Dean
|
August 22, 2013 at 12:56 am
Hi,
You are using a Beta version of Event Espresso. I would recommend backing up your site and updating to the latest release version of Event Espresso.
If the issue persists after updating please advise.
|
|
jferguson
|
August 22, 2013 at 1:00 am
This version was installed by Chris Reynolds. The last time I performed an upgrade it broke several components in EE. Especially the custom questions we ask on the registration form for each Seminar. How do I get in touch with him or a member of your support staff to help me with this?
|
|
Dean
|
August 22, 2013 at 1:36 am
OK, well thats fair enough. Chris no longer works here, but what he has probably done is modify the template files, so after upgrading the modifications will need to be added to the new template files.
Looking into this further, the version you have, did not have nonce (security) checks which the newer versions do, so it really is advisable to update, otherwsie you will keep running into this problem.
If you don’t wish to update and port the changes across yourself we can do that for you, but would require a Priority Support token purchased.
If you wish to remain on the current version you have, you could try Sidneys “fix” at the bottom of this post https://eventespresso.com/topic/error-when-updating-ticket-info/
|
|
jferguson
|
August 28, 2013 at 1:47 pm
Cannot seem to find wp_die( $failed_nonce_msg ); in either of those scripts.
|
|
jferguson
|
August 28, 2013 at 1:49 pm
Just a little more info regarding this issue.
If I have a Multiple Registration, I can only edit the primary attendee. When trying to modify any of the secondary attendees I see this error:
An Error Occurred. The request failed to pass a security check.
Please press the back button on your browser to return to the previous page.
And it appears not to matter what field I am trying to change.
|
|
jferguson
|
August 28, 2013 at 2:07 pm
Sorry, I was looking in an older install of EE. I was able to find “wp_die( $failed_nonce_msg );” in those scripts, commented that out but the issue persists.
|
|
Josh
|
August 28, 2013 at 8:20 pm
Have you tried updating yet?
|
|
jferguson
|
August 28, 2013 at 8:26 pm
No I haven’t updated. The last time I did, it broke the registration form and all question information. Chris and several other EE employees had to get involved and fix the install. If EE staff is willing to help me upgrade and confirm nothing breaks this time, it would be greatly appreciated.
|
|
Sidney Harrell
|
August 28, 2013 at 9:51 pm
Are you updating the attendee record or the attendee payment?
There should be 3 instances in edit_attendee_record.php and 2 instances in enter_attendee_payments.php.
|
|
jferguson
|
August 28, 2013 at 10:12 pm
I found all instances of that statement and commented them out. I am trying to modify the attendee, but im sure if I tried to modify the payment I would see the same error.
I also noticed that if I click on any of the secondary attendees on the attendee list, it will always redirect me to the primary attendee. Not the secondary attendee I initially clicked on.
|
|
Josh
|
August 29, 2013 at 9:12 am
Hi there,
We are really not in a position to support an outdated beta version. I can advise backing the site up, including the database, and doing the update. There is an update guide here:
https://eventespresso.com/wiki/updating-event-espresso/
If you require support staff to perform the update we can typically do this with the purchase of a support token. If there are customizations that Chris had earlier made that need to be re-factored (there’s a potential for this, but updating from .31 will likely be fine) then it may require additional support tokens.
|
