Jump to content
Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by MrPhil

  1. Email 5 minutes later: "Hey, where's my package??!"
  2. MrPhil


    Do our moderators have the ability to move misplaced threads into the right area? If they do, they should be doing so! Assume that it's "official" if the poster doesn't state their osC version.
  3. Never try to run a live, public-facing website on your own server. Hackers know far more about security vulnerabilities than you ever will, and they will eat your lunch. It's OK to run your own server if you're only playing around to see if you want to get into running a site, or experimenting with something like a PHP version that your commercial host doesn't yet support. Otherwise, stick with a professional hosting service. Since you're just starting out, make sure you are running the right osCommerce if you actually want to run a production store. It should be "Frozen" (or, if you're adventurous and don't mind constant changes, "Edge"). Do NOT under any circumstances run the "official" release -- it is totally obsolete. Do not run osC v 3.0 -- it is experimental/developmental. Don't even try running osC 2.4 -- it's not really yet ready for production use. Ignore instructions to chmod to 777. They're just telling you that the PHP process running on the server needs to be able to read and write the files. First of all, .php files rarely need the execute bit set any more (so 666 would be sufficient). Second, many modern servers don't even allow "world writable" files or directories, and will give you a 500 error if you try. Always start with typical default file permissions (usually 644) and add write permissions (+020 and/or +002) as needed. Instructions to chmod to 777 may have been reasonable 20 or 30 years ago, but back then you could trust anyone else sharing your machine to be honorable. You can't now. Always start with the most restrictive permissions your site will function with, and loosen restrictions only upon demonstrated need.
  4. MrPhil


    You should not be using osC v 3.x unless you are a very experienced developer. It is an experimental/developmental version which will probably never see the light of day. What you should be using is the community-supported osC "Frozen". If you're experienced enough to deal with an unstable, constantly changing version, there's also "Edge".
  5. MrPhil

    Compare my shop with "Frozen"

    I take it that someone massively modified your copy of pre-Frozen, and thus it would be difficult to modify a stock Frozen copy to match? If it wasn't tremendously modified, you may want to consider starting with the current Frozen and (slightly) modifying it to do what you want. That would probably be a lot easier.
  6. MrPhil

    Compare my shop with "Frozen"

    Yes, you can give WinMerge two directories and it will tell you files were added/deleted and which files are different. Then you can click on a "changed" file to get a line-by-line report of the differences.
  7. MrPhil

    Adding images into product description

    No virus at all.  is the UTF-8 Byte Order Mark. You're using a dipshit editor that insists on inserting the BOM at the beginning of any file you create in UTF-8 encoding. That includes most Microsoft editors. Either find a way to turn off adding BOM, or get a better editor (e.g., Notepad++ or ViM).
  8. MrPhil

    Adding images into product description

    Check your HTML page source to make sure the browser is using the exact code that you typed in: <img class="img-responsive" src="img_ tempo-size.png" alt="Aneros Tempo Sizing"> If that's what you see, what directory are you in when this should be displayed? Your path to the image file has to take this into account. If you're showing the page under /index.php, the image would have to be in the root (/). Or you can make it images/img_tempo-size.png with the image in /images/. I presume the space between img_ and tempo-size is a typo? Not all operating systems are happy handling spaces in names, and in any case you need to be consistent. I think there is an add-on or two to display additional images for you -- you might want to look at that.
  9. MrPhil

    Overwriting system files

    A new installation of osC would overwrite any file that you've changed. It can be done, with care -- you need to keep track of all your customized files, save them to the side when overwriting the existing installation, and then manually put your custom changes back in. I don't know if we'll ever get back to the old way of incremental updates on new osC versions -- add-on-like updates that might preserve your changes. Do be sure to look at recent add-ons for osC (CE) -- the idea is to get away from changing "core" files. You might be able to configure your desired changes in the same manner, so that a new install won't wipe you out, but no promises. Speaking of add-ons, first look at existing add-ons to see if what you want has already been done! Contrast this with CMSs like Drupal, where all the customization is either stored in the database, or in an approved library of new PHP code, so typically you would never modify their PHP code yourself.
  10. MrPhil

    Paypal Standard Suddenly Displaying Errors?

    You're trying to run osC 2.3.1 (which is ancient) on PHP 7.1? I wouldn't be at all surprised that something is breaking (and probably not just PayPal). I'm surprised it ran at PHP 5.6. The only out-of-the-box osC versions that work on PHP 7.1 are "Frozen" and "Edge". Roll back to PHP 5.6 if you can, so you can at least run your store, and start making plans to upgrade to "Frozen" as soon as possible.
  11. MrPhil

    Serve images in next-gen formats

    To really convert on the fly, at each request from a browser, would be foolish. The added time to do the conversion would far outweigh any time savings in transmitting a smaller image file. You want to do it just once, preferably in batch, rather than as-needed (where you need to track which images have already been converted). Secondly, you need to know whether the customer's browser can handle .webp. That might be possible by querying the browser and release number, but offhand I can't tell you a good way to do that. If the Javascript (running on the browser) decides it's safe to ask for .webp, it might change the <img> src on the fly to ask for .webp instead of some other format. That will take additional time to do both tasks, so I'm not sure you end up with any net savings in time. Notice that you have new PHP code running on both the server (if you do the conversion to .webp there, rather than on your PC), and JavaScript on the client (browser) to select which format to use and rewrite the <img> src. If you want to assume that everyone is running a fairly up-to-date browser (no one required to run IE6 any more!), you might serve only .webp, having done the conversion only once (on your PC). Of course, you still have to go through all the places where image URLs are stored on your site, and update them to .webp. In the end, is this worth the effort? Unless you can reduce image transmission time by 200 - 300% I don't think you're going to end up saving anything.
  12. MrPhil

    Product Name & Price Size Change

    The first thing would be to confirm that you're editing the right files, saving them properly, and uploading them properly. When you display the HTML source for the page, it's not changing <h1 and <h2 to <h3 as you're trying to do? You can temporarily add doug to the list of classes, to confirm that you're hitting the right place and the file is getting used. If it is changing to <h3 but you're not seeing any effect, could there be CSS overriding the default heading text settings and setting a fixed font size? A browser should be able to show you the CSS in effect and where it came from.
  13. Also, you are talking about osC 2.3.4. Note that this section of the forum is for osC 2.4, which is an entirely different product (still under development at this stage).
  14. If you want Terms and Conditions applicable to your shop and products (don't forget warranties and guarantees, and licenses too), you're not going to find a "rules generator" that's going to fit you. My suggestion would be to grab copies of T&C, etc. from other stores and vendors, and use the ideas there to generate your own. Just don't copy verbatim (a copyright violation). Please note that this is a legal document, so you want to be careful not to include discriminatory terms, etc., and you want to cover all the bases. It might be a good idea to run it by a lawyer to see if there are any problem areas. You don't want to run afoul of your country or state's laws (discrimination, consumer protection, privacy, etc.).
  15. MrPhil

    Serve images in next-gen formats

    .webp is a new format (essentially a new compression method) for images. They will probably transfer a bit faster (being smaller), and most major browsers now support the format. Is it worth the effort to convert? Who knows. It may well suffer the same fate as JPEG-2000... improved compression that got little support. When you say "convert on the fly", what exactly are you looking to do? You don't want to store your images as .png, .jpeg, etc. and then literally convert them as served to .webp -- that would slow things down considerably (the whole point of the exercise is to speed things up). You would want to use some utility to convert (in batch) your images to .webp, and then serve those like you currently serve other formats. Don't forget that anyone with older browsers (not Chrome, Edge, or Firefox current versions) is going to be left holding the bag when your site serves them .webp images that their browser can't handle. Are there any provisions in JS/CSS for selecting which type of image to call for?
  16. MrPhil

    New Install PHP 7.2 sizeof()

    On the contrary, I've seen many reports of official installing OK, but failing to run properly due to incompatibilities with PHP 7.x. Unless HPDL did a sneak update recently (without bumping the point release number), the last time I looked, all he had done was to suppress PHP 7's "deprecated" warnings. If he's actually gone through and fixed all the PHP 7 problems, I'll be happy to retract my statement. Get a copy of 2.3.4 and a copy of, and file-compare them, as I did last year.
  17. MrPhil

    New Install PHP 7.2 sizeof()

    osCommerce has always been community supported, but unfortunately, developed by only one person (at least, he's the gatekeeper). This one person has not been active for a year and a half now, and has let the official version grow obsolete. We've repeatedly told him that you cannot let a product stagnate for years at a time, and then release an updated version in a blaze of glory, because we have to start all over again building a track record for the product, but he's set in his ways. As for how responsible would it be to use the community edition ( Frozen), it would certainly be more responsible than using a totally obsolete version (that won't even run on most servers today. At least, the CE is up to date and is being maintained. If your client is uneasy about depending on such an informal arrangement, then by all means they should switch to another shop which has a more robust and formal organization behind it. Just keep in mind that even the best professional shops eventually fade away, and your client will be looking to move once again! That's a fact of life: no shopping cart software will ever be eternal, and no matter what you use, you will sooner or later have to migrate to something else. All you can do it keep good records on everything you've done to a shop, so that it's less painful to migrate in the future, whether it's to a newer version of your current software, or to a whole new platform.
  18. MrPhil

    Site Meta Tags not applying when tested.

    I had never seen a title meta tag before this thread. Apparently you can specify different titles for a page via <meta name="title" content="My Title" /> and <title>My Other Title</title> . https://stackoverflow.com/questions/21076201/difference-between-meta-name-title-tag-and-title-title-tag discusses the difference between the two, although there seems to be debate over who actually uses the meta variety. That was several years ago, so maybe things have changed. Anyway, does having a meta title really have a significant impact on SEO? Is it worth the bother?
  19. MrPhil

    Grundsätzliches Module

    First of all, make sure you are installing a current version of osCommerce, one that is PHP 7-ready, secure, mobile-friendly, and up to date with many new features. That would be osCommerce "Edge" or "Frozen". As you are not experienced with osC, I would recommend "Frozen" (see my signature below for the link), even though it is not PHP 7.2-ready and has a list of patches. Under no circumstances should you even think about installing the "official" version downloadable from this site. It's obsolete, even though it's also called "". via Google Translate:
  20. MrPhil

    New Install PHP 7.2 sizeof()

    Try to avoid rolling back to anything earlier than PHP 7.1, because all earlier versions (up through 7.0) are completely out of support. Hackers are going to have a field day breaking anything running on less than PHP 7.1, as there will be no further patches to those PHP levels. In practical terms, that means that only osC "Frozen" and "Edge" should be used. Frozen has a short bug list (which needs patching), and Edge is unstable (the author is constantly changing it). Frozen needs further fixes to run on PHP 7.2, and Edge is at least most of the way there on PHP 7.2 compatibility (I don't know if it will run on 7.2 out of the box).
  21. null is a special keyword with a special meaning. It does not get quotes around it, nor is it capitalized. Some older versions of MySQL may have allowed '' instead of null.
  22. Do one of two things: Omit 'zone_id' and '' from the two lists, or Replace '' with null One of them should work. zone_id is autoincrement, so omitting it or giving null should increment it to the next value.
  23. Note that Frozen is compatible with PHP 7.1. To run on PHP 7.2, some fixes might have to be made to the code. You may be better off dropping back to PHP 7.1, if you can.
  24. There is no upgrade script for the code. It's a fresh install. There might still be some SQL scripts included with each version to "import", that modify your database from to 2.3.4 and then to Frozen, or you can do it manually (compare schemas and update a backup with an editor). Of course, proceed carefully, back up your current code and database first, make sure they're good backups, and know how to restore them if you botch the upgrade job. Or, hire someone to do the job for you.
  25. MrPhil

    HoneyPot Captcha

    You might want to read this article on CAPTCHAs: https://www.theverge.com/2019/2/1/18205610/google-captcha-ai-robot-human-difficult-artificial-intelligence . It states that AI is expected to improve to the point that it will solve any CAPTCHA puzzle much better than humans can. It's just about there, already. The emphasis will have to shift from how perfectly the "user" can solve a problem to watching how very human imperfections and randomness in the interaction betray who is human. Also, rather than relying on a one-time hard-shell defense against bots, we will have to watch users in their interactions with a site and see if they're doing bot-like things. Big Brother, anyone? The article points out that Third World CAPTCHA farms use people to sign up for forums and blogs, etc., which then can be handed over to bots to do the spamming. This would require monitoring of the user interactions beyond just the signup, such as an occasional CAPTCHA challenge from time to time. If most spammers crap on your forum just once (or use your tell-a-friend function for one mass mailing) and then never come back, that may be more annoying than useful. The comments are rather interesting too. Several people pointed out that the reCAPTCHA emphasis on traffic lights and street signs and vehicle recognition suggests that we are being used to train Google's self-driving cars -- for free.