Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

1 Follower

About HowardR

Profile Information

  • Real Name
    Howard Richman

Recent Profile Visitors

2,312 profile views
  1. I wonder if anybody else has encountered this weird bug? If so, I would be interested in hearing how you solved it. The problem occurred in my second store, for which I upgraded my 2.3.3 store database (which used Option Types) to Edge using the attached file. The weird bug is that in my 2.3.3. store, my database allowed Option Values (for the "select" option type) to be at least 40 characters long, but my new Edge store only allows them to be 32 characters long or less. If I go over 32 characters, I get the following database error from checkout_process.php *after* successful processing of the customer's credit card: At first I thought that all I would have to do was change the "Value Length" for my option names from the transferred in value "0" to "40". But that didn't affect anything. So I "solved" the problem by abbreviating the names of all of my option values that were longer than 32 characters so that they would be 32 characters or less. Howard 233_to_234BS.sql
  2. clustersolutions: I think I can answer your question. The problem with dropping 5.010 directly into Edge is that it was coded for OSCommerce 2.3.5, not for OSCommerce2.3.4Edge. (I may be wrong about this.) However, according to the V 5.010 thread, you can install 4.039 and then upgrade to 5.010 with just one click. See: Some people who tried that in April got errors due to deprecated syntax in the code. My guess is that those errors could be easily eliminated by installing the compatibility add-on: Add-On Compatibility for 2.3.4 EDGE. If you install 4.039 and then click the button to upgrade to 5.010, please post here how it went. If you succeed, I'll probably do it myself. Howard
  3. frankl, The service settings are at If you are wondering about my Service Settings, do check out my thread about how I set up OsCommerce 2.3.4BS EDGE version to work with PayPal PayFlow-- And don't miss my response to my own initial posting in which I described a small change I made in those service settings just before I put my store online. My thread is at: My store is online and working. I have been taking orders for a couple of days and they have been coming through without problem. Howard
  4. Bonbec's solution worked! I have now uncommented the error-causing line and I don't get an error when I click on "Products Attributes" after clicking on "Catalog" while using the administration tool (/admin/index.php). In my code, the line (about line 29) of /admin/products_attributes.php now reads: Bonbec, you are brilliant! I should have thought of that solution myself! I should have been tipped off by the fact that (int) appears before the $languages variable in the very same command. Tsimi, I love your idea of updating the code and uploading a new add-on. When you do so, *please* put up the updated files also; you would save everyone hours and hours of time! For the record (in case the bug was due to MySQL version), my version is 5.6.35. Howard
  5. I've got my store online. One of the last things I did was change the Return URL in the PayPal Service Settings on the PayPal website to checkout_process.php from checkout_success.php. I did so because checkout_process.php sends out an email before it exits with checkout_success.php.
  6. Tsimi, Thank you. You guys are the best! I very much appreciate your fast responses to my questions. And your add-on is the best! I wouldn't use OSCommerce without it! The compatibility link that Raiwa posted was very easy to install, and it solved all of my other "bugs". By the way, I don't think that commenting off that one line has affected my store. Option types appears to be working fine without it. Howard
  7. Thank you Naiwa, But the line that I had to comment off does appear to contain a bug. The database is getting the string 'Options_Values_Text_ID' for a value that requires an integer. Howard
  8. Here's something else to add to the admin/includes/configure.php file if you are using the boot strap 2.3.4 version: define('FILENAME_PRODUCTS_ATTRIBUTES', 'products_attributes.php');
  9. I found and fixed a couple of bugs in the Bootstrap version and I think things are working now: 1. I added the following to both configuration files (includes/configure.php & admin/includes/configure.php): define('DIR_WS_INCLUDES', 'includes/'); 2. I couldn't find the error that I posted about above in the /admin/products_attributes.php file. So I commented off the line that was causing the database error. In other words, I inserted // at the beginning of the line. (It's near the beginning of the file -- about line 29.) If anybody can find the error in this line please post here. I may run into problems as a result of commenting it off. It has to do with the names of attributes in each language: //tep_db_query("insert into " . TABLE_PRODUCTS_OPTIONS_VALUES . " (products_options_values_id, language_id, products_options_values_name) values ('" . OPTIONS_VALUES_TEXT_ID . "', '" . (int)$languages[$i]['id'] . "', '" . TEXT_UPLOAD_NAME . "')");
  10. Dear Community: I'm doing a new clean install of Oscommerce 2.3.4BS Edge, and I just added the Option Types for 2.3.4 BS contribution. But when I go into my administration tools and click on "Catalog" and then "Products Attributes", I get the following error message on the admin/products_attributes.php page: Apparently, the database expects an integer value but is getting 'Options_Values_Text_ID' instead. I thought that the error could be due to me having installed admin/products_attributes.php incorrectly, but both of the files that came with the add-on gave me the same error. I even tried carefully installing one-by-one the changes in the products_attributes.php file, but I still got the same error. Has anybody encountered this error before? If so, is there a known fix? I suspect that the problem is that Options_Values_Text_ID is being treated as a literal when it is actually a variable that has an integer value. If I find the fix, I'll post it here. Howard
  11. Burt, Thank you very much for the response. I'm probably wrong about v5. Could you go to PayPal Manager and check out your PayPal Service Settings Set Up? V5 settings are most likely the same as v4. Did you: Use GET or POST? Return to checkout_process.php or checkout_success.php? Enable Secure Tokens? Howard
  12. There will be other people who will be in a rush this week to set up new OSCommerce stores in order to work with PayPal PayFlow. If your store is on an old website that doesn't support TLS 1.2, you have to move fast. My store was on a Centos 5 website which didn't support TLS 1.2. I was paid up until early July, so I waited until now to make the switch. Here's how I got the Edge Version of OS Commerce 2.3.4 working with PayPal PayFlow: 1. Purchased a new dedicated server from GoDaddy. 2. Installed GoDaddy's SSL certificate on the new server. 3. Upgraded the dedicated server from EasyApache 3 to EasyApache 4, in order to get TLS 1.2 level of security. 4. Downloaded OSCommerce with Bootstrap Edge version from the following website: 5. Changed the root directory of my store to oscommerce234Edge and uploaded the entire directory to the public root directory of my website. 6. Downloaded PayPal App v4.039 from following website: and navigated to catalog\includes\modules\payments in that app and to oscommerce234Edge/includes/modules/payment in my store. I deleted every payment module that was in the online directory. Then I uploaded the four payment modules from the PayPal App directory because they fix the checkout_payment/checkout_success bug that has not yet been fixed in the Edge download. 7. I added "& ~E_DEPRECATED" to the error_reporting line in the BootStrap Edge files oscommerce234Edge/includes/application_top.php and oscommerce234Edge/admin/includes/application_top.php. 8. I used my CPanel to create a new mysql database and gave myself, as user, administrative privileges with that database. 9. I made following changes to Service Settings at PayPal Manager: Changed all URLs to the correct URLs on my new website. (Note that Edge no longer has a "catalog" directory.) Changed Get to Post in two places Changed checkout_process.php to checkout_success.php Set Enable Secure Token to "No." 10. I used Google Chrome to go to to https://mydomain/oscommmerce234Edge/install/. At the prompt for WWW Address I used https://mydomain/oscommerce234Edge/ 11. I downloaded the newly created configuration files and made some slight changes: in the includes/configure.php file I changed define('ENABLE_SSL', false); to define('ENABLE_SSL', true); in the admin/includes/configure.php file I changed define('ENABLE_SSL_CATALOG', 'false'); to define('ENABLE_SSL_CATALOG', 'true'); 12. Then I used Google Chrome, to go to my administration file: https://mydomain/oscommerce234Edge/admin/index.php 13. I clicked on "PayPal" and clicked on "Start". Then I clicked on "Retrieve Live Credentials." And saved the result. (I didn't retireve my sandbox credentials, which was a mistake.) 14. Then I added a $1 item to my products which I called "Bumper Sticker" and I set set Flat Rate shipping to be 0, so that I could buy an item that would just cost $1 15. Then I came into my store and tried to buy the bumper sticker. I was never prompted to enter my name. The only way I was able to check out by clicking on "Check out with PayPal" but I got an error message that my credentials were not installed correctly. (Probably because I had not retrieved by Sandbox Credentials when I should have done so. 16. Then I went back to my administrative tool and clicked on "Modules" and "Payment" to see what payment modules were installed. The only one installed was PayPal Express Checkout. The only option for editing it was the sort order, which I edited and set to 1 and clicked "save". 17. Then I clicked on "Install Module" and installed a second module: "PayPal Payments Pro (Direct Payment)" which took me to a page where the highlighted items (orange with white background) indicated which cards had been enabled and that the status was "Live" and the transaction Method was "Sale". So I Saved those settings. 18. Then I clicked on PayFlow and filled in my credentials which I got from my old store's PayPal Payflow Version 1.2 Payment Module. Where it said "Merchant Login" I put in what was called "Vendor" in my old store. I inserted the same credentials for Sandbox. Then I clicked "Save." 19. Then I went into my store as a customer. I tried to buy a bumper sticker with a credit card, and it worked. 20. Then I went back into my administration tool and clicked on PayPal and credentials to see what the problem was. It showed that I had never entered my Sandbox credentials. When I tried to retrieve those, it sent me to a page where it wanted me to set up a business account, which I already have. So I simply copied my Live Credentials into the boxes for my Sandbox Credentials and I clicked "Save." 21. Later, I went back into the store as a customer and tried to check out with PayPal and everything seemed to be working. Everything that I did could be done in a short time, but it took me hours and hours. I made lots of mistakes such as trying to install Version 5 of the PayPal app which doesn't work with the Edge version and trying to install the PayPal modules before installing the PayPal tool.
  13. I am migrating my stores to a secure website that supports TLS 1.2 in time for PayPal's June 30 deadline. My old OSCommerce 2.3.3 store uses PayPal PayFlow Module Version: 1.2. My new store will use the Edge version with the latest PayPal modules (probably 5.010). Anybody have any tips for changes in the way that PayPal Service settings should be set up? For example, in my old store, I used "GET" for my Cancel URL Method and my Enter URL Method. Should those be changed to "POST"? Similarly, in my old store, I set Enable Secure Token to "Yes." Should that be changed to "No"? Any tips that you can give on how you did it would be appreciated. Howard
  14. Now PayPal says that we have until the end of June before the change goes into affect.
  15. Actually, the deadline is the *end* of May, not the beginning. Also, the June 9, 2014, add-on has the PayFlow modules while the March 17, 2017 version has other PayPal payment modules as well as some admin improvements that work with the PayFlow modules.