Support

Home Forums Event Espresso Premium IE error – We're sorry but there appears to be an error with the "reg_url_link"

IE error – We're sorry but there appears to be an error with the "reg_url_link"

Posted: May 26, 2015 at 4:43 pm

Viewing 15 reply threads


setaadmin

May 26, 2015 at 4:43 pm

When users try to revisit their registration using IE and the link embedded in the email (something like https://site.com/registration-checkout/?e_reg_url_link=1-f1c03e075e50d2ec6f0ac2a510f5af75&step=payment_options&revisit=1), they are seeing an error related to “reg_url_link”. This looks to be something related to the “final_verifications” function around line 829. The link works fine in all other browsers.

Any ideas?

WP version4.2.2
EE version: 4.6.28.p


setaadmin

May 26, 2015 at 9:10 pm

UPDATE – now all we get is the shortcode [ESPRESSO_CHECKOUT] ion all browsers!


Tony

  • Support Staff

May 27, 2015 at 4:17 am

Hi Stacey,

Are you running any caching plugins or does you host run server side caching?

I tried taking a look at your events but they are hidden behind a member log in, could you create a temporary login for us to use so we can view this please?

Please send log in details using this form – https://eventespresso.com/send-login-details/


setaadmin

May 28, 2015 at 7:47 am

An update – today we received an update alert for Version 4.6.29.p. When we tried to perform the update, everything looked like it was working until I went back to the plugins page and received the following error: https://cohesionsummit.org/?attachment_id=9724

The plugin page shows we have Version 4.6.29.p though….


Lorenzo Orlando Caum

  • Support Staff

May 28, 2015 at 7:54 am

Hi, it looks like it ran into an issue with side-loading a language file from GitHub.

What language are you wanting to use with Event Espresso 4?


Lorenzo


setaadmin

May 28, 2015 at 8:09 am

We only need English (US), so maybe a non-issue then?
Thanks so much for your quick response! You guys are awesome.


setaadmin

May 28, 2015 at 8:15 am

We are also now seeing the “reg_url_link” error in all browsers – not just IE. Again, this seems to only occur when users try to revisit their pending registration by using the link provided in the email notifications (something like: ?e_reg_url_link=1-d556d9f0ab2bc4c259c66913cfa468eb&step=payment_options&revisit=1)


setaadmin

May 28, 2015 at 8:19 am

So something with the following code in the “event-espresso-core-reg | modules | single-pagecheckout | EED_Single_Page_Checkout.module.php” around line 837. It seems that “$valid_registrant instanceof EE_Registration” is null:

if ( ! empty( $this->checkout->reg_url_link )) {
$valid_registrant = $this->checkout->transaction->primary_registration();
if ( ! $valid_registrant instanceof EE_Registration ) {
EE_Error::add_error( __( ‘We\’re sorry but there appears to be an error with the “reg_url_link” or the primary registrant for this transaction. Please refresh the page and try again or contact support.’, ‘event_espresso’ ), __FILE__, __FUNCTION__, __LINE__ );
return false;
}


Tony

  • Support Staff

May 29, 2015 at 4:22 am

I’ve ran a registration on the site and used IE, FireFox and Chrome to revisit the site, all of which worked without showing the error above.

Have you made any changes to EE and do you still see the same error message?

Here is my revisit link:

https://site.com/registration-checkout/?e_reg_url_link=1-dabe18e84d4f792c9fb984e4ce7e9cb2&step=payment_options&revisit=1

Do you see the error there?


setaadmin

June 3, 2015 at 11:47 am

Well – several days and no complaints. I have tried the site using another computer not attached to our campus network and it works fine. I am marking this up to something either on my machine or a machine/network policy causing the issue.

Thanks for all of your help!


Tony

  • Support Staff

June 3, 2015 at 12:03 pm

Thank you for letting us know.

If you do run into any further issues we can investigate further.


John Ballment

June 15, 2015 at 2:33 am

Hi

I’m using EE 4.6.31p and I’m getting the same issue in Google Chrome when users are clicking on the link in the payment reminders. A sample link is http://sydney.anglo-indian-reunion.com/registration-checkout/?e_reg_url_link=1-5aeee2f57bed1bb8666493654c38c5eb&step=payment_options&revisit=1.

Regards

John.


Dean

June 15, 2015 at 4:16 am

Hi John,

I checked your link in the latest Chrome and couldn’t see any error notifications – should something appear in the Registration Checkout page?


Tony

  • Support Staff

June 15, 2015 at 5:05 am

Hi John,

I also see the correct ifnromation when using that link.

We found that the

We’re sorry but there appears to be an error with the “reg_url_link”

Error is usually thrown when there is a session conflict, this can be caused by by the admin when you open up a registrants payment page (which opens a session) then you open another, which tries to retrieve the info for your current session based on the e_reg_url_link parameter and your session (which now conflicts because your session was opened using a different e_reg_url_link than your new page)

Make sense?

If you run into this issue again, go to your registration cancelled page, usually:

youdomain.com/registration-cancelled/

Then retry the link you previously used that threw the error.

I have created a ticket for some developer feedback on this.


John Ballment

June 16, 2015 at 7:31 pm

Hi Tony

You’re correct, if I open the links in another browser they work fine.

Thanks

John.


Tony

  • Support Staff

June 17, 2015 at 2:31 am

Great, thanks for letting me know.

If it pops up again you should be able to just visit the registration cancelled page in whichever browser you are using to clear the current session, then continue on as you were.

Viewing 15 reply threads

The support post ‘IE error – We're sorry but there appears to be an error with the "reg_url_link"’ 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