Hi,
The fix that Dr.Byte is not working for me. The file authorizenet_aim.php has already been comment out
// curl_setopt($ch, CURLOPT_SSLVERSION, 3);
and the orders don't go through authorize.net.
Please help me. What should I do?
Thanks
Hi,
The fix that Dr.Byte is not working for me. The file authorizenet_aim.php has already been comment out
// curl_setopt($ch, CURLOPT_SSLVERSION, 3);
and the orders don't go through authorize.net.
Please help me. What should I do?
Thanks
Hi,
Try replacing /includes/modules/payment/authorizenet_aim.php with the one in the zip I've attached here. It should be compatible with ZC v1.3.9a thru v1.5.3. (And may be fine on 138 as well).
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
DrByte your authorizet.net_aim.php file is significantly different from the one with ZC v1.3.9b.
For me, using just the modification:
// curl_setopt($ch, CURLOPT_SSLVERSION, 3);
Worked for my site.
It also includes a handful of tweaks and updates to the AIM standards.
But really, if you're still using 1.3.9, you really ought to be scheduling an upgrade really soon.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
I have tried to use your zip file, but it does not work with 1.3.9d. Do you know what i have to change in the PHP file to make it work?
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
it is still coming up with a communication error.
In v1.3.9 the debug logs were typically put into the /cache/ folder on your server. You'll need to use FTP to look at that folder, and then look for the most recent AIM_xxxxxxx.log files.
Inside the files will be the actual communications log for the attempted transactions, including the details which explain what's failing.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Bookmarks