|
William Perry
|
March 23, 2015 at 1:52 pm
I am trying to setup Authorize.net. I went to the setup page and entered my Login ID and Key. Debug = no, open by default= yes, Send test transactions = no, then click update authorize.net AIM settings. I get a message back (Under the Button URL) that says *That URL seems to be broken. Please enter a valid URL.* The default URL looks good. It seems to point to valid location.
|
|
Lorenzo Orlando Caum
|
March 23, 2015 at 3:04 pm
Hi William, the credentials that you should use are different than your login information for your Authorizenet account.
I did see the word “key” in your prior reply so you may be using the correct credentials but I wanted to mention that.
If you copy the button URL and paste in into your web browser, do you see the image appear?
One other thing to check is the use of HTTPS. If you do not have an SSL certificate on your site, then please be sure that the button URL uses http at the beginning of the URL.
—
Lorenzo
|
|
William Perry
|
March 24, 2015 at 5:29 pm
A. I understand the difference between user id + password and the API login + key. If I got that wrong, I assume that the error message would give me an indication that the API Login + key is incorrect.
B. The URL is http. I have a SSL cert, but I don’t have anything pointing to it. So it is not active yet.
C. Yes I did the cut & paste trick (pasting the string into the browser) to be sure that the “pay-by-credit-card.png” is accessible to the web server. It works.
D. I looked in the web server’s log files (error and access) there is nothing.
|
|
William Perry
|
March 24, 2015 at 5:48 pm
I note a message near the top which may have some meaning.
An error has occurred:
Payment method of type Authorize.net AIM was not saved because there were validation errors. They have been marked in the form
Payments_Admin_Page – _update_payment_method – 767
|
|
Tony
|
March 25, 2015 at 7:16 am
Hi William,
Are you using the default image URL or a custom one?
|
|
William Perry
|
March 27, 2015 at 9:31 am
It is the default image.
|
|
Tony
|
March 27, 2015 at 9:40 am
HI William,
We believe this is due to certain server configurations and have included a fix within 4.6.18.p which should fix it.
Can you update to the latest version of Event Espresso and retest please?
|
