|
Tom Semmes
|
December 10, 2013 at 6:39 pm
Hello. I just updated Event Espresso. Since I did that our registration no longer works when submitting a registration. No settings have changed. The return URL is still https://asisnyc.org/?page_id=160. This still goes to the Thank You page.
Payment is set up using the Authorize.net SIM method. The error message is
“The following errors have occurred.
(14) The referrer, relay response or receipt link URL is invalid.”
Why would Authorize.net now have a problem with the return URL when it didm’t before? Anything I can do to address this?
|
|
Dean
|
December 11, 2013 at 1:18 am
Hi Tom,
Not sure why this has suddenly stopped. Do you have Force HTTPS on Return option set in the Payment Gateway options?
One possibility is to turn that off, and to use the stripped transaction page (otherwise the return page may look a little wonky) – http://eventespresso.s3.amazonaws.com/2011/09/txnpage.zip.
|
|
Tom Semmes
|
December 11, 2013 at 7:37 am
Dean, I did not have Force HTTPS option selected. And the page did not look wonky. I did try toggling that one and off to see if it made a difference. One thing I wonder is why the url starts with https. The actual final page it ends at is http. But https is how it is listed in Event Espresso and at Authorize.net and that is what has worked.
I will try using the stripped page but it seems that isn’t the issue since Authorize.net is not able to mathc the return relay URL in the first place.
|
|
Tom Semmes
|
December 11, 2013 at 7:47 am
Dean
Changing the template made no difference.Are there any other suggestions?
|
|
Tom Semmes
|
December 11, 2013 at 8:46 am
I am creating a new support ticket in a hope I can push this to a higher level.
I updated Event Espresso to Version 3.1.36.1.P. Since then we are getting relay response errors from Authorize.net. Nothing was changed in the system except the update. This is directly related to the update.
Naturally this happens when we have our largest meeting a week a way and hundreds of people registering. Or trying to.
Could someone from Event Espresso get into our system and take a look around and try to fix this.
Or can we move back to an OLDER VERSION where Event Espresso was working?
Is it possible to move this support ticket to a higher priority?
|
|
Josh
|
December 11, 2013 at 10:06 am
It looks like there is a redirect happening from https to http. Can you go into your Authorize.net account and add this URL to the relay response URL field:
http://asisnyc.org/events/thank-you/
Also, do you have the above page set to be forced as SSL (via a plugin like WP HTTPS) ?
|
|
Tom Semmes
|
December 11, 2013 at 10:10 am
Josh
I tried setting the page to be SSL enabled (I am not sure if that is the same as forced). I use BEtter WP Security plugin to control SSL. I updated that at the same time as Event Espresso. Not sure why that would make a difference. I will try adding the URL you suggest to Authorize.net and see what happens.
|
|
Josh
|
December 11, 2013 at 10:20 am
I think you’ll need to try it with the SSL turned off for that page. It appears that the Better WP security plugin’s SSL functionality isn’t working on your site.
|
|
Josh
|
December 11, 2013 at 10:20 am
I think you’ll need to try it with the SSL turned off for that page. It appears that the Better WP security plugin’s SSL functionality isn’t working on your site.
|
|
Tom Semmes
|
December 11, 2013 at 10:39 am
The SSL was turned off for that page. How do you know the Better WP Security is not working?
|
|
Josh
|
December 11, 2013 at 12:10 pm
Something (and it may be the .htaccess rules that WP Better Security writes) is redirecting all https traffic to http.
If you try visiting:
https://asisnyc.org
do you see how it automatically redirects to:
http://asisnyc.org
|
|
Tom Semmes
|
December 12, 2013 at 10:43 am
It redirects it because the WordPress Address (URL) in General settings is set to http://asisnyc.org. WP Security is set up so that only specific pages are secure, which we were advised to do to help speed up the site. When you go to a page that is supposed to the be secure but use the http, it refers it to the https page. So it looks like the Better WP plugin is active.
But I think this security issue could be the problem. One thing I never understood is why if the page people final end up in is http://asisnyc/events/thank-you but the Relay Response URL listed in the payment settings is https://asisnyc.org/?page_id=160. Which was what was listed at Authorisze.net
WAIT! I just checked and the URL changed. Now it is http://asisnyc.org/?page_id=160. Maybe that is because I just deactivated this plugin called Fix SSL/Non-SSL Links (This plugin forces all site content and links to use SSL when the page request uses SSL. Similarly, if the page request doesn’t use SSL, all content and links are forced to not use SSL.) Okay, just reactivated it and the URL switched to https://asisnyc.org/?page_id=160
Anyway, we tried http://asisnyc.org/events/thank-you/. And both http and https://asisnyc.org/?page_id=160. But nothing works.
I need to ask this client for access to Authorize.net to find out what exactly is there before I move forward. But I would like, if you can, to clarify this issue over the discrepancy btw the actual referral page and the URL that is listed in Payment Settings. Also curious why you felt the SSL plugin was not working. Maybe our system is not set up as it should be?
|
|
Josh
|
December 12, 2013 at 11:20 am
Even if your WP site setting is set to http://asisnyc.org it should allow the page to load up as https if that’s requested. It may be one of the plugins you’ve set up added some redirect rules to the .htaccess file that is breaking this.
I think the root of the problem that you’re seeing is that redirection from:
https://asisnyc.org/?page_id=160
to http://
|
|
Tom Semmes
|
December 12, 2013 at 11:37 am
In the list of Response/Receipt URLs, I have these listed
https://asisnyc.org/?page_id=160 Default Receipt URL Edit
http://asisnyc.org/?page_id=160 Default Relay Response URL Edit
http://asisnyc.org/events/thank-you/
What other options do I possibly have?
|
|
Tom Semmes
|
December 12, 2013 at 11:40 am
Okay I deactivated all plugins to do with SSL. And now it works. But of course we don’t have any pages that are protected. Which doesn’t’t seem acceptable does it?
|
|
Tom Semmes
|
December 12, 2013 at 12:18 pm
The system is now working.
I can’t say I know exactly what the final fix was but it had to do with the SSL security plugin. I deactivated it and the system worked fine. But since I knew that you want a secure site I then reactivated the plugin I made every page on the site secure. I then added every possible combination of the relay URL
https://asisnyc.org/?page_id=160 Default Receipt URL Edit
https://asisnyc.org/events/thank-you/ Default Relay Response URL Edit
http://asisnyc.org/?page_id=160 Delete
http://asisnyc.org/events/thank-you/ Delete
I then changed the settings to only specified pages are secure. And now it works. So something in there worked.
I can’t really say if it was something in updating Event Espress (which might have changed slightly how SSL works and created a conflict with my existing settings) or with WP Security or something else. Anyway it works. Thanks for your help.
|
|
Josh
|
December 12, 2013 at 1:42 pm
Which pages do you need to be encrypted? The credit card info gets entered on Authorize.net server right?
|
|
Tom Semmes
|
December 12, 2013 at 1:52 pm
The client wants any page that people enter personal information (i.e., a form) to be encrypted.
|
