The logs folder to which I refer is included/part of a zencart install. So, if you performed a "by the book" install, the folder should be present.
The logs folder to which I refer is included/part of a zencart install. So, if you performed a "by the book" install, the folder should be present.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Another update from me, in case anyone is watching this thread :)
I'm becoming more convinced that Carlwhat is right--this may not even be engaging the Authorize.Net AIM module. Since logging hasn't revealed any insights, I've tried adding variables to the session throughout the script. I see only the one that I put at the very top (which tells me that the authorizenet_aim.php file is being loaded), but I don't see any of the other variables being set in the session when key functions are running. So, my current interpretation is that authorizenet_aim.php is loaded and installed, but for some reason, the functions that interact with the gateway and process payment aren't even being called. Hence, I'm not even seeing error messages from the gateway or the AIM script.
This is all pretty weird, because AIM is the only payment module that I have installed, and orders appear to be going through without a hitch (other than the payment processing being skipped).
Anyone have any ideas? Continuing to troubleshoot.... and pull out my hair.
Best, KKoch
Hi RixStix,
As far as I know, it was a "by the book" install. I started with one of those nifty auto-installers provided by the host. I do have a /zencartinstall/logs folder, but I'm not seeing any logs in there. There are logs from other days, but nothing recent.
Best, KKoch
A follow-up observation, in case anyone is wondering. I went into my database to ensure that all the configuration keys installed by the Authorizenet AIM module were actually there. They seem to be present and all correct. Also, under Admin -> modules -> payment, the Authorize.Net AIM option is there, and completely functional. So, if our guesses are correct and the authorizenet_aim.php functions are simply not being called during the payment process, then this is pretty baffling to me. Any guesses out there?
Best, KKoch
Ok try something super simple,
Uninstall the module from your ZC admin clear your cache( just in case )
Re-Install the Module
Zen cart PCI compliant Hosting
Hi Merlinpa1969,
Actually, that was one of the very first things I tried, but I decided to do it again, just for grins. Unfortunately, the problem remains.
Some more information for anyone who is following along.
Looking at the authorizenet_aim.php file, I can confirm that the following functions are being executed, and appear to be working normally:
* authorizenet_aim()
* confirmation()
* process_button()
I have no indication that before_process() (which adds the credit card info to the order and preps the call to the gateway) or _sendRequest() (which actually contacts the gateway) are executing. I have no idea why this would be.
Not too many people would agree that using one of those nifty auto-installers provided by the host is a "by the book" install. They have been known to be without problem and they have also been known to be the source of many problem.
Does/Did AIM work out of the box before you installed any addons or templates?
Other zenners may be able to offer more suggestions if they had a link to the site with the problem.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Hi RixStix,
I'm not sure whether it did or not, but I do know that, with all the testing I did pre-launch, I have nothing in the 'authorizenet' table. So, it may not have.
The site in question is https://www.birdwatchersdigest.com/shop/index.php
Really hope that helps. I'm compelled to give up on AIM and install something like PayPal Pro, but I wonder if I'd encounter the same problems there? I wonder if this is a larger, systematic problem with payment as a whole, and not just AIM.
Best, KKoch
Since AIM (and SIM) are included with the standard zencart install, it is probably the most tested and reliable method of accepting CC, so I would be more inclined to believe that there is something within your specific environment.
Since you did use an auto-installer, it is possible that the install did not have the POODLE fix(es) applied to the various payment modules.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
Bookmarks