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
Apostrophe in customer name causes 404 | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Apostrophe in customer name causes 404

Apostrophe in customer name causes 404

Posted: August 6, 2013 at 9:06 pm

Viewing 8 reply threads


Cam Jakson

August 6, 2013 at 9:06 pm

Hey guys, we are using the latest event espresso over at http://thumpmusic.com.au/

I have found that customers who register that have an apostrophe in their name causes a 404 error when going to the payment section. I have no idea who to fix this or where to start. Any help would be greatly appreciated!

PS, I found this was happening with previous version also, i was hoping that updating would fix it but it hasnt.

Thank you

Cam


Josh

August 6, 2013 at 9:39 pm

It appears the 404 is happening on the redirect to the payment gateway (via the bypass the payment overview page option) . Can you let us know which gateway you’re using?


Cam Jakson

August 6, 2013 at 9:44 pm

eway only


Dean

  • Support Staff

August 7, 2013 at 1:19 am

Thanks for that, I will raise a developer ticket to look into this more closely.

Can you please confirm that you have set the Eway settings to use $AUD?


Cam Jakson

August 7, 2013 at 5:22 am

correct, its set to AUD. Thanks Dean


Dean

  • Support Staff

August 7, 2013 at 5:27 am

OK, thanks for the confirmation, will need to wait for a dev to look at this, but ive given it a really high priority.


Josh

August 8, 2013 at 11:44 am

Hi Cam,

We’re getting ready to release a hotfix for this. You can change one line of code in /gateways/eway/Eway.php if you’d like to use the fix now:

line 47 is getting changed from:

$ewayurl .= $name . '=' . $value . '&';

to

$ewayurl .= $name . '=' . htmlspecialchars_decode  ($value,ENT_QUOTES ) . '&';


Cam Jakson

August 10, 2013 at 9:27 pm

Thank you sir’s.


Dean

  • Support Staff

August 12, 2013 at 4:02 am

Marking resolved as workaround displayed above and fix is due to be released shortly

Viewing 8 reply threads

The support post ‘Apostrophe in customer name causes 404’ 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