Jump to content

Kohn

Members
  • Content count

    40
  • Joined

  • Last visited

  1. Kohn

    show only subcategories

    Anybody got this to work? I really need to just show the subcategories.
  2. Kohn

    Google Analytics module

    I have installed the tracking code in our site but the ecommerce sale info isn't showing up correctly. It is not possible for us to add onLoad="java script:__utmSetTrans() In the Body tag because the body tag is in the header.php, universal to all content files. Can we add the above code to a <div> tag in checkout_success.php? How will itaffect the include(DIR_WS_MODULES . 'analytics/analytics.php'); which we then included just above the </div> tag? The transaction information does show up in the output HTML code in checkout_success.php, but the information is not regarded in GA. Any idea?
  3. Kohn

    PayFlow Pro Nightmare

    OK our nightmare is over and I want to share the experience with those of you who are having the same issue. So here it goes. 2 days ago our server crashed when we tried to update plesk. It went back on shortly afterwards but we realized that although no information was lost, credit card transactions are not going through. Nothing was changed, so we assumed that the crash corrupted the SDK file. We proceed to download the new SDK file, untarred it in the same folders, test.sh (we are on a linux server) went through fine and VeriSign confirms it, but OSCOMMERCE just wouldn't work. So what the hell was the problem. We chmod 777 to the pfpro module, bin, the lib, and then set the CERT PATH in ssh, export it, and even verified it with env|grep. Everything was OK but as soon as the information is going to be transferred to VeriSign it returns the dreadful CREDIT CARD ERROR. In the end it was Cardinal Commerce that helped us. We have Cardinal Commerce's modified PayFlowPro modules because we were using them as our Verified by VISA/Master Secured Code validator. Jeff from Cardinal Commerce was extremely helpful, even stuck with me for 45 minutes trying to help us figure out the problem (not to mention doing personal searches on google, verisign). They were even more helpful than VeriSign tech support, who still has not called us after a day. Anyway, within the cardinal modified PFPRO module, there's an option that outputs all the card transaction information to the error log (php.log). From there we found out that these error messages were present in every failed attempt: [17-Nov-2005 12:53:22] PHP Warning: putenv(): Safe Mode warning: Cannot override protected environment variable 'LD_LIBRARY_PATH' in /home/httpd/vhosts/audiocubes.com/httpdocs/includes/functions/php_pfpro.php on line 149 [17-Nov-2005 12:53:22] PHP Warning: putenv(): Safe Mode warning: Cannot set environment variable 'PFPRO_CERT_PATH' - it's not in the allowed list in /home/httpd/vhosts/audiocubes.com/httpdocs/includes/modules/payment/payflowpro.php on line 242 Turned out that after our server went down, when it was back on, PHP was in safe mode. Our tech support disable safe mode in the local value, but that wasn't enough. As soon as local and master value of Safe mode are disabled, eveything went through correctly. This was the last thing we thought of. If we did not have that debugging information god knows when this problem can be resolved. I hope our experience will help some what for you people out there looking at that bright red error message. Good luck!
  4. Kohn

    Seeking help with payflow pro payment module

    OK our nightmare is over and I want to share the experience with those of you who are having the same issue. So here it goes. 2 days ago our server crashed when we tried to update plesk. It went back on shortly afterwards but we realized that although no information was lost, credit card transactions are not going through. Nothing was changed, so we assumed that the crash corrupted the SDK file. We proceed to download the new SDK file, untarred it in the same folders, test.sh (we are on a linux server) went through fine and VeriSign confirms it, but OSCOMMERCE just wouldn't work. So what the hell was the problem. We chmod 777 to the pfpro module, bin, the lib, and then set the CERT PATH in ssh, export it, and even verified it with env|grep. Everything was OK but as soon as the information is going to be transferred to VeriSign it returns the dreadful CREDIT CARD ERROR. In the end it was Cardinal Commerce that helped us. We have Cardinal Commerce's modified PayFlowPro modules because we were using them as our Verified by VISA/Master Secured Code validator. Jeff from Cardinal Commerce was extremely helpful, even stuck with me for 45 minutes trying to help us figure out the problem (not to mention doing personal searches on google, verisign). They were even more helpful than VeriSign tech support, who still has not called us after a day. Anyway, within the cardinal modified PFPRO module, there's an option that outputs all the card transaction information to the error log (php.log). From there we found out that these error messages were present in every failed attempt: [17-Nov-2005 12:53:22] PHP Warning: putenv(): Safe Mode warning: Cannot override protected environment variable 'LD_LIBRARY_PATH' in /home/httpd/vhosts/audiocubes.com/httpdocs/includes/functions/php_pfpro.php on line 149 [17-Nov-2005 12:53:22] PHP Warning: putenv(): Safe Mode warning: Cannot set environment variable 'PFPRO_CERT_PATH' - it's not in the allowed list in /home/httpd/vhosts/audiocubes.com/httpdocs/includes/modules/payment/payflowpro.php on line 242 Turned out that after our server went down, when it was back on, PHP was in safe mode. Our tech support disable safe mode in the local value, but that wasn't enough. As soon as local and master value of Safe mode are disabled, eveything went through correctly. This was the last thing we thought of. If we did not have that debugging information god knows when this problem can be resolved. I hope our experience will help some what for you people out there looking at that bright red error message. Good luck!
  5. Kohn

    PayFlow Pro Nightmare

    Have you guys found out the reason why? We are experiencing the exact problem after our server went down and when it's back again the nightmare just wouldn't go away.
  6. Kohn

    Seeking help with payflow pro payment module

    Have you found out the reason why? We are experiencing the exact problem after our server went down (and came back). Have you found out the reason why? We are experiencing the exact problem after our server went down (and came back).
  7. Hi Paul, Actually after adding the codes you included above, the orders.php shows the Verification Phone and Validation Code fields but the actual information is not there. Any idea on this?
  8. Hi Paul, Sorry for the late reply, I was traveling. That was an excellent mod, now we can double check on the telephone number. As for the telephone requirement, I still would like to see it implemented. If the customer enters some fake number, it immediately confirms that they are not willing to show their telephone number - hence it's even more likely to be a fraud. Remember that because we are using the PayflowPro module by CardinalCommerce, the PayPal and Money Order orders can still go through without customers entering a phone number, or a verification code, so I think this is still needed. Also, it's more professional - you ask customer to enter a code, but you let them pass without entering it, seems kind of sloppy? Let me know of your thought on this and if it's possible (I know I am really pushing it here ... :blush: ) Once again, thanks for the help.
  9. Hi Paul, OK, actually the code should be in payer_auth_start.php, not in auth_auth.php. After moving the code from checkout_process to auth_start.php it work now as intended. I think it's more critical for this check to be for payflowpro since paypal has some sort of registration in place. Great, now we have it working!! I am still wondering if there can be some kind of check that's not exactly like javascript but more like requiring the user to enter the phone number at the checkout_payment page. Is this possible? Meanwhile, the contribution seems to be gone 2 days ago, sorry I failed to let you know, I thought it was a glitch. This contribution really should there. I think it'll help us little merchants a lot! Once again, thank you Paul for your help :) :)
  10. Hi Paul, Thanks for the help. We are using hte CardinalCommerce module, which modifies the PayflowPro module. It seems that when you click on the confirm button at checkout confirmation, the module first goes through payer_auth_auth.php, then to checkout_process and by the time it gets to checkout_process the transaction has already completed. Please see the module here: http://www.oscommerce.com/community/contri...search,cardinal Right now a lot of customers (even those who may not be fraudsters) are simply leaving the telephone field blank, and since the checkout_process.php isn't really validating the verification code, all transactions are still going through. That's why I was wondering if there can be some sort of check to have the telephone number entered (kind of like at user registration the telephone number is necessary?) I really appeciate your help and please let me know what you think.
  11. Hi Paul, Is it possible for you to add the javascript validation for telephone entry at the checkout_payment page? Or is this something that I can find coding for (not a programmer here, but I try my best). Thanks for your help, we are plagued by frauds right now .....
  12. Hi Paul, OK, I tested and verified that if I use PayPal or Money Order, without entering the correct code, I won't pass. However, I am using the PayflowPro contribution and it seems that when I click on Confirm, the checkout_confirmation will use the PayFlowPro module first, bypassing the checkout_process. How can I modify the code so that the verification code is the first thing that confirmation checks? If there's any additional information that you need, please let me know. Meanwhile, keep up the great work :)
  13. Hi Paul, I changed the code but the order still went through without entering a verification code? Also, I think it's actually a better idea to not let customer go through if no telephone number is entered. I think this would deter the fraudster right there and then. Furthermore, if no telephone is entered, the information is still sent to Maxmind and recorded in the log (just a blank transaction) and this actually confuses us a lot, as we cannot match the phone calls with the attempts. Please advise.
  14. Hi pyounan, Great contribution, we are using it right now. However, there seems to be a bug. Right now we are setting the verification at 250 and although everything turns on and works fine, customer can actually not enter a telephone number and still go to the confirmation page. Also, even after that, customer can complete the transaction without entering the verification code (which defeats the whole purpose of having the verification process, we want to stop those customers who did not enter any number, or verification number). We have updated the code as according to the installation instruction. Are we doing something wrong here? Please let us know.
  15. Just a note. I was trying to set this script up for the 2.2milestone and realized that product_listing will not display "click here for price," instead just the price that we want to hide. This is due to that p.products_map was not called in the catalog/index.php so the value of listing[products_map] was always zero. After replacing: $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, with $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, p.products_map, I was able to see the product_listing displaying "click for price" instead of the MAPed price.
×