If you host with GoDaddy, you WILL have an issue if using Authorize.net. Don\'t worry though! It can be resolved! This fix may also apply to other hosts as well. If you get no response when trying to make an Authorize.net transaction... blank screen, etc... then give this a try as it is likely your problem:
Open the dtregister.php file which is found in /components/com_dtregister.
Around Lines 3609-3614, you\'ll find this:
// UNComment the following two lines if you use GoDaddy hosting
/*
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt($ch,CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
*/
CHANGE it to this:
// UNComment the following two lines if you use GoDaddy hosting
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt($ch,CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
THEN... same thing around lines 7658-7664, you\'ll find this:
/*
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch,CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
*/
CHANGE it to:
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch, CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
This uncomments these lines of code and uses different code for CURL. After making the changes, upload the modified dtregister.php file back to:
/components/com_dtregister
All done. That wasn\'t so bad now was it?
Now, IF you use ECheck with Authorize.net, you\'ll need to do the same thing to the file eCheck.html.php which is found in the same directory.
Around lines 1319-1323, you\'ll find:
/*
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch, CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
*/
CHANGE it to:
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch, CURLOPT_PROXY,\"http://proxy.shr.secureserver.net:3128\");
Just one spot in that file! Upload your modified file and now you\'re all done. If you need further assistance, let us know.