Jump to content
Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


MrPhil last won the day on January 19

MrPhil had the most liked content!

Profile Information

Recent Profile Visitors

107,894 profile views
  1. If your version has a filenames.php (and it came with the installation and is actually used), you can add missing file names. Otherwise, names get hard coded now, and you will have to find any place FILENAME_MODULES is used and replace it by the string 'modules.php'. That should not happen in base code, but it's quite likely in add-ons.
  2. MrPhil

    Email queuing system

    Do you mean "the DEFAULT change to TIMESTAMP"? datetime should still be a valid field type, shouldn't it? CURRENT_TIMESTAMP appears to be a more recent addition to MySQL -- is the failing database a much older version? I think the intent is that it acts like INSERT INTO with a now() value, but it can now be defaulted to do that. For older MySQL versions, it won't work, and you may have to explicitly give a now() in the VALUES list. That, or declare a minimum MySQL version number.
  3. As PHP 7.2 is now fairly well established (and PHP 7.3 is starting to show up), any thoughts on how "Frozen" could be upgraded to work on 7.2 and up? If there are a lot of changes to make, perhaps general guidelines would be in order, rather than an exhaustive list of fixes (or even an add-on!). This would still leave a lot of work to be done by shop owners, but it may be the best we can do. Add-ons will be yet another issue. I presume that Edge is/will be PHP-7.2 ready out of the box, but there are still a lot of people on Frozen just because it's nice and stable. That's the one that I install for clients. Once Slushee comes out (next freeze of Edge), that is at least PHP-7.2 ready, I would assume that any further work on Frozen would cease. And oh, how about calling the next one osC 2.3.5? It's obvious that HPDL is never going to accept any of Gary's work as the official product, and he's probably never going to release another osC, so why not ease the confusion?
  4. If you're really trying to install on a PHP 7.3 system, you aren't going to find any version of osCommerce that will work at that level. It's unlikely you'll find any other e-store that will, either. I presume you're trying to install on a PC with *AMPP stack, which often have absolute bleeding edge versions on them. If you must install on your PC, you'll need to back off to PHP 7.1. Do not, repeat, do not, try to run a real store with real customers and real money on your own PC. Hackers know far more about security issues than you ever will, and will eat you alive. Such a setup is OK for playing around to see if you want to get into running a site, or to experiment with more advanced software levels than your host supplies. But for a real site, stick with a commercial hosting service who can devote the necessary time and energy to maintaining security.
  5. My client carries items that weigh anything from a few grams to several kilograms. They prefer to work with grams rather than kilograms, and with weights in kg, they would need at least another decimal place or two (5,2 -> 7,4). Why was this field done in decimal rather than a real/float in the first place? It might be too much bother this far down the road, but maybe it would be/have been nice to have a weight unit for each product (oz or lb, g or kg). Just another products table field. The messy code comes when combining product weights for a shipping total, but it could be done.
  6. In oscommerce.sql (or via phpMyAdmin after installation), consider increasing the size of products.products_weight from decimal(5,2) to something like decimal(9,3). At 5,2 the maximum weight is 999.99 units, which is a bit small if you're working with grams, or even possibly with ounces. I just had this setting up a shop for a client, who couldn't figure out why he was limited to 999.99 grams for a 3300 gram item!
  7. MrPhil

    credit card skimmers (in JS)

    Is "slow ass Magento" the new "slow as molasses" way to describe pokey things?
  8. MrPhil

    reCAPTCHA addon recommendation

    It's not clear that CAPTCHAs or reCAPTCHA do more good than harm. Bots have gotten so good at processing them that you can say that a CAPTCHA is more likely to exclude a human than a bot! If such challenges are going to do any good, they will need to look at how the puzzle is solved (including timing and minor mistakes) to see that it's a human and not a perfect bot. Of course, bots will then be modified to look more like humans in how they work the puzzle... In the end, the behavior once "inside the gates" will have to be monitored to detect bots and/or spam content being sent, rather than trying to keep bots out.
  9. MrPhil

    Email queuing system

    The first time I read it, I thought he was just using Black Slang (bad = good, get down = get frisky/get busy). Now I'm wondering. Not having to create an account seems to be widely popular, as people fear their information will be used to harass them (marketing emails, sale of personal information, etc.). I too, would like to hear his reasoning.
  10. MrPhil

    credit card skimmers (in JS)

    An interesting (and concerning) article: https://arstechnica.com/information-technology/2019/03/a-new-rash-of-highly-covert-card-skimming-malware-infects-ecommerce-sites/?comments=1 . It seems there are ways to inject encoded Javascript credit card skimmers into shops (Magento, so far, has been hit hard). One of the comments brought up Content Security Policies to control where Javascript comes from on your site.
  11. It's telling you that something on line 1 of turkish.php is outputting to the browser. Should the first line be nothing but <?php ? That's the usual case. Did something get added to it, such as a Byte Order Mark (3 odd characters)? Use a good editor to remove any BOM, and check that it didn't add it back in!
  12. It depends on how customized a site you're looking to do. Some of the things that Loic mentioned are geared specifically towards a store site. Others are more general Content Management Systems, which have a lot of prewritten modules for stores, blogs, galleries, etc. Still others are just the basic frameworks themselves, such as Zend, CakePHP, etc. There is no one "best" that can be recommended -- it depends on what depth you wish to get into, and your experience and skill level.
  13. MrPhil

    Email queuing system

    This is an interesting subject. It sounds like the desire is for ability to trigger sending an email on many different kinds of events (calendar, order shipped, shipment delay, abandoned cart, follow-up on order, merchandise return, no orders in the last X months, etc.) "slugs" of a template for the email (anything starting "Hey Phil" gets immediately deleted from my inbox! I had a credit card which used my initials, and I'd get mails "Dear P" from the issuer.) -- perhaps several different templates to choose from, based on customer specifics (e.g., a Valentines Day offer geared differently towards singles and couples)? ability to pull information from the database (customer name, order information, ship date, etc.) and put it in the email possibly updating the database, such as a coupon was issued on my birthday Without a lot of custom-written code, especially to read/write the database for all sorts of different things (and combinations of data), I don't think you can generalize this with one piece of code. However, specific modules could be supplied to do specific tasks (e.g., look up customer birthdays), maybe with a hook system so new ones can be added. The data found should influence the content of the email, so that it's appropriate and has the maximum impact. Be careful about queuing up so many emails that your host slaps you (is a rate limiting mechanism assumed? if so, do different messages have different priorities?). Also be careful about straying into actual marketing mails if the customer has not granted permission to send such to you.
  14. Free and Advanced? Is this in reference to the add-on, or to the base osCommerce? osC is only free. By the way, as you're new here, make sure you're building your site on the only supported and current version, which is osC "Frozen". See the link to it below in my signature. Do not use the official release, as it's unsupported, unresponsive, and quite a few years behind the times (e.g., doesn't properly handle PHP 7).
  15. It's a fresh install of Frozen. There were some changes to parallel the "official" patch, but there have been myriad other changes since 2.3.4BS. You will be able to migrate your database and product images, although I don't think there's any "one-button" process for that (you need to compare database schemas and upgrade your DB field by field and table by table). It should not be anywhere near as bad as migrating from the non-BS official versions. It will also bring you up to PHP 7.1 compatibility. Don't forget to go over the "bugs in Frozen" thread to fix a number of minor issues.