|
John Ballment
|
May 7, 2015 at 5:06 am
Hi,
I have a registrant trying to update her registration details from the “edit” link in the Order Confirmation form. Whenever she tries to save an update she gets the following message:
An error has occurred:
Unable to save registration form data for the form input: “new_state_micro_form” with the submitted value: “Array”
EE_SPCO_Reg_Step_Attendee_Information – _process_registrations – 727
This can be reproduced by clicking on the “edit” button next to the Registration Details header from the following link http://sydney.anglo-indian-reunion.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=receipt&context=purchaser&token=1-c1a433326543af83e83675a1aec3612a&GRP_ID=11&id=6023. All I did to reproduce the issue was changed address line 1 from “tba” to “hello”.
Regards
John
|
|
John Ballment
|
May 7, 2015 at 5:10 am
Opps forgot to mention I’m using EE 4.6.23.p with the mailchimp, social and calendar plug-ins installed.
|
|
Lorenzo Orlando Caum
|
May 7, 2015 at 12:19 pm
Hi John, could you please update to the latest release and retest this?
https://eventespresso.com/wiki/ee4-changelog/
Some of the recent security releases for WordPress affected Event Espresso and we want to ensure that isn’t happening here.
Thanks
—
Lorenzo
|
|
John Ballment
|
May 7, 2015 at 5:22 pm
Here is the same link in our development environment http://dev.anglo-indian-reunion.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=receipt&context=purchaser&token=1-c1a433326543af83e83675a1aec3612a&GRP_ID=11&id=6023 and after updating everything including WP to 4.2.2 I’m still getting the same error.
Regards
John.
|
|
Lorenzo Orlando Caum
|
May 8, 2015 at 6:51 am
Hi John, a team member verified this issue this morning and we are working on a fix.
We’ll update this support post once we have more information.
—
Lorenzo
|
|
Josh
|
June 5, 2015 at 3:22 pm
Hi John,
A little update on this: Event Espresso 4.6.30.p includes a fix for the issue you reported here. Thanks for reporting.
|
|
John Ballment
|
June 7, 2015 at 3:33 am
I just installed 4.6.31p and it seems to have resolved this issue.
Thanks again.
|
