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
2Checkout -- This is killing me! | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › 2Checkout — This is killing me!

2Checkout — This is killing me!

Posted: September 7, 2012 at 12:35 pm

Viewing 4 reply threads


trjast

September 7, 2012 at 12:35 pm

So I’ve heard good things about 2Checkout, and I saw that it was compatible with Event Espresso, so I decided to go with it. 2co says you guys use a header redirect as the method of returning from them back to my site, and so I’ve set everything up according to this: https://www.2checkout.com/shopping-cart/event-espresso/

As a sidenote, I have a full 2checkout account, but since I am still currently testing it, it is still set to demo mode. The reason I am mentioning this is that I did read that when in demo mode, the INS is not running (not sure if this has anything to do with it), here is the source: http://developers.2checkout.com/echo/topic/ipn-doesnt-run-when-in-demo-mode

Now, everything works (feel free to test it out at http://smileconference.com/registration/?ee=2 and just enter 16 random digits for the credit card info) until it goes to send me back to my site. When I get sent back to my site, it sends me back to an https version of my site. How can I do a header redirect without getting sent back to my site with https? Is the only way to fix this to just go with it and get an ssl certificate? Please help! example


Sidney Harrell

  • Support Staff

    •

September 7, 2012 at 12:52 pm

Do you have the “force https on return” option checked in EE’s 2CO payment settings?


trjast

September 7, 2012 at 1:03 pm

No, It is not checked
example2


Sidney Harrell

  • Support Staff

    •

September 7, 2012 at 5:51 pm

I see the bug. in gateways/2checkout/2checkout_vars.php, line 44 is currently:

$my2checkout->addField('x_Receipt_Link_URL', str_replace('http:', 'https:', $home . '/?page_id=' . $org_options['return_url'] . '&id=' . $attendee_id . '&r_id=' . $registration_id . '&event_id=' . $event_id . '&attendee_action=post_payment&form_action=payment&type=2co'));

it should be

$my2checkout->addField('x_Receipt_Link_URL', $home . '/?page_id=' . $org_options['return_url'] . '&id=' . $attendee_id . '&r_id=' . $registration_id . '&event_id=' . $event_id . '&attendee_action=post_payment&form_action=payment&type=2co');

I’m not sure how that happened, but this fix will be in the next update.


trjast

September 7, 2012 at 5:58 pm

Awesome, just fixed it as you said and it works great. Thank you!
Viewing 4 reply threads

The support post ‘2Checkout — This is killing me!’ 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.

The original Forum description...

Status: closed

Updated by trjast 12 years, 4 months ago ago

Topic Tags

Tagged: , , , , , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server