Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

phi148

Members
  • Content count

    273
  • Joined

  • Last visited

  • Days Won

    3

phi148 last won the day on August 9 2021

phi148 had the most liked content!

About phi148

  • Birthday 01/01/2006

Profile Information

Recent Profile Visitors

14,277 profile views
  1. phi148

    osCommerce site and Forums update notice

    Do we have information on the link of the FTP address for the old addons ?
  2. phi148

    Google reCAPTCHA v3

    @Hotclutch nice information there. I think it would be good to modify this addon to tie the captcha to the form submission (rather than on pageload). That will get rid of the 2 minute problem entirely. It probably isn't a good thing to display that informational alert... most customers probably have no idea what a captcha even is
  3. phi148

    Google reCAPTCHA v3

    The 2 minute window is the only reason I haven't implemented this. I think there is a way to do it only when the user clicks "submit" for example, but I haven't looked into how that would change this add on. Is anyone using this currently? How are you getting around the 2 minute issue? I think a lot of people take longer than 2 minutes for the contact us or for the create account forms.
  4. Anybody know how to modify this add-on to return categories as well (instead of just products?)
  5. phi148

    AIM and SIM have reached End of Life

    I also use this and I am willing to help as well.
  6. phi148

    Google reCAPTCHA v3

    Don't you have to edit contact_us.php and create_account.php as well to make the call to initReCaptcha ? For example, in "contact_us.php" don't you have to have this command somewhere? echo $OSCOM_Hooks->call('contact_us', 'initReCaptcha');
  7. I think I fixed it. Downloaded this new file http://curl.haxx.se/ca/cacert.pem And replaced it here: /home/xxxx/public_html/ext/modules/payment/authorizenet/authorize.net.crt I *think* this is the answer. Will keep you all posted if it fails again.
  8. I was able to capture some output: * Trying 198.241.207.102:443... * TCP_NODELAY set * Connected to secure.authorize.net (198.241.207.102) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /home/xxxx/public_html/ext/modules/payment/authorizenet/authorize.net.crt CApath: none * SSL certificate problem: self signed certificate in certificate chain * Closing connection 0 Notice the error --> * SSL certificate problem: self signed certificate in certificate chain
  9. All, today an update was rolled out with authorize.net They call it Phase 4b. You can see it here: https://support.authorize.net/s/article/Authorize-Net-Network-Change-FAQ Ever since this happened, I noticed something very odd. Intermittently I couldn't connect to authorize.net. I narrowed it down to the IP address 198.241.207.102 Interestingly enough, the other IP that they use (198.241.206.93) works fine. These 2 IP addresses seem to change at random times. You can see these are the IPs that are allocated to: secure.authorize.net/gateway/transact.dll as shown here: https://support.authorize.net/s/article/Authorize-Net-Domains-and-IP-Addresses So essentially, depending on which IP that the endpoint resolves to, either a payment goes through or it doesn't. I think this must be a problem that has to do with me having an outdated certificate (This is my guess) Does anyone else have this problem AND does anybody have an updated certificate that goes here /public_html/ext/modules/payment/authorizenet/authorize.net.crt I was able to temporarily get around this problem by setting Verify SSL Certificate to False in my authorize.net settings in oscommerce. Thank you,
  10. phi148

    AIM and SIM have reached End of Life

    I fixed it by adding this code to create a customer profile which now lets me save the customers information so I can rebill them easily. I just added this as a last minute feature after a successful credit card transaction. Seems to work just fine for me. I also have it send me an email if it fails for some reason. That part has not been tested yet since it seems to be working and not executing that code. if ($error == false) { $g_loginname = substr(MODULE_PAYMENT_AUTHORIZENET_CC_AIM_LOGIN_ID, 0, 20); $g_transactionkey = substr(MODULE_PAYMENT_AUTHORIZENET_CC_AIM_TRANSACTION_KEY, 0, 16); $posturl = "https://api.authorize.net/xml/v1/request.api"; $content = "<?xml version=\"1.0\" encoding=\"utf-8\"?>" . "<createCustomerProfileFromTransactionRequest xmlns=\"AnetApi/xml/v1/schema/AnetApiSchema.xsd\">" . "<merchantAuthentication>" . "<name>" . $g_loginname . "</name>". "<transactionKey>" . $g_transactionkey . "</transactionKey>" . "</merchantAuthentication>" . "<transId>" . $response['x_trans_id'] . "</transId>" . "</createCustomerProfileFromTransactionRequest>"; $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $posturl); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, Array("Content-Type: text/xml")); curl_setopt($ch, CURLOPT_HEADER, false); curl_setopt($ch, CURLOPT_POSTFIELDS, $content); curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); $response_cim = curl_exec($ch); curl_close($ch); $parsedresponse = @simplexml_load_string($response_cim, "SimpleXMLElement", LIBXML_NOWARNING); if ($parsedresponse->messages->resultCode == "Error") { $to_name = STORE_OWNER; $to_email_address = STORE_OWNER_EMAIL_ADDRESS; $email_subject = '!!! Customer Information Manager Alert !!!'; $email_text = '<span style="color:red;">Customers information was not stored in authorize.net</span>'; $from_email_name = 'Authorize.net ALERT Notification'; $from_email_address = STORE_OWNER_EMAIL_ADDRESS; tep_mail($to_name, $to_email_address, $email_subject, $email_text, $from_email_name, $from_email_address); } }
  11. phi148

    AIM and SIM have reached End of Life

    I need to find out for sure. You may be right. Assuming you are correct, then it looks like I need to implement Authorize.net "CIM". Which doesn't exist either right now
  12. phi148

    AIM and SIM have reached End of Life

    Hey all. I’m currently using AIM. However the “rebill” function is going away and AIM is also end of life. Having to call customers to get their payment info over and over will really become a pain and I was hoping to avoid that.
  13. I'm in need of this too. Looks like I may have to switch payment processors if the community no longer wants to support authorize.net
  14. phi148

    AIM and SIM have reached End of Life

    Really need this to be updated! Anybody working this by chance?
  15. phi148

    Multi_Vendor_Shipping new thread

    I don't believe this has been done yet, but I also would be interested in this... if and when I upgrade to Phoenix.
×