Jump to content

ArtcoInc

Members
  • Content count

    2,080
  • Joined

  • Last visited

  • Days Won

    37

ArtcoInc last won the day on October 16 2021

ArtcoInc had the most liked content!

Profile Information

  • Real Name
    Malcolm

Recent Profile Visitors

30,660 profile views
  1. @Hotclutch As I stated in my earlier post, some email servers (like GMail) required a proper "sending email address" (from_address) and/or reply_to_address n the email header. Your code segment is adding the from_address to the email header if the version of PHP is newer than 5.3, and you say that this seems to fix the problem. Thank you. A couple of questions ... 1) Is there anything in the PHP mail() function in versions earlier than v5.3 that would crash if the -f parameter is added? 2) If not, why not include the additional -f parameter always, and not even bother testing for the PHP version? 3) And lastly, is anyone still running PHP versions earlier than v5.3? (rhetorical question, no answer needed) Malcolm
  2. ArtcoInc

    Incorrect datetime value

    @aespinal2 Is this a new problem? Has something changed on your friend's host/server? I had a similar issue with the configuration on my in-house development server. I was able to fix the configuration as described here: That said, I don't know how your friend's server is set up. You may have to talk to their host about this. HTH M
  3. @Hotclutch Did this just start in the last week or so, or did you only just notice it in the last week or so? If it just started, you may need to speak to who is hosting your site(s), and ask what's changed. I do recall that there has been a long history of email issues if the 1) sending email address, 2) reply to email address, and 3) your web site's address .... are not the same. You can search the forum for this. IIRC, it happened with both GMail and Yahoo email addresses. HTH M
  4. ArtcoInc

    NIF (VAT NUMBER) in customer email confirmation

    @driven22 You can receive support for Phoenix on their forum: https://phoenixcart.org/forum/ M
  5. Once again, this thread has moved from the original topic, and devolved into a bunch of (imho) useless bickering. This seems to happen a lot on this forum. And yes, I will accept some responsibility for my part in this. Those of us that have been around for a while know the history, and have opinions on what happened, and what should have happened. Rehashing this over and over has no benefit, and drags threads off topic. So please note: if this continues, I will go back and hide all posts in this thread (including mine) that went off topic. Ok? Oh, and @Demitry , I was not referring to you for the "doom and gloom" comment. I apologize if you took it that way. M
  6. @Hotclutch @Demitry Thank you for your input. This gives the op more information with which to base his/her/their upgrade choice. I was not promoting waiting to upgrade to osC v4, merely tossing that out as an option (although not one I would choose). When Vadym announced the new ownership, he *did* say .. But, since he has not been here for some time, and is late in releasing v4, we can't see how smooth that migration might be. There is an osC fork (that we aren't supposed to talk about here) that does have a migration tool. I have used it, and while it is not perfect, it does work. But any migration will have issues. The way add-ons were used in older versions of osC WILL create migration issues. For those of us here that are trying to support other osC users, there has to be a balance between offering encouraging support, and promoting "gloom and doom" by saying osC is dead (that's another discussion), that it is not fixable (Hotclutch has shown that it IS fixable), and that one needs to jump ship. I wish the op luck in fixing their shop. Now, I need to get off of my lazy butt and fix mine, but that's another story. Malcolm
  7. When my shops 'crashed', and I phoned support to ask them to roll back PHP, they could not install the same version of PHP on the crashed sites (no idea why! Same server .... <shrug>). The .htaccess file for one shop loads PHP v5.4, and the .htaccess file for the other loads PHP v5.6. Hence, why one shop is on v5.4.45, and the other on v5.6.40. My thoughts? It's working for now (fingers crossed), and I *really* need to upgrade both shops 'real soon now'! M
  8. @OldPete I have my shops all on the same hose (and presumably, the same server). One shop is running PHP 5.4.45, another PHP 5.6.40, and another 7.4.23. And the down-rev PHP shops all have a similar line in the .htaccess file. M
  9. ArtcoInc

    Admin Links Stop

    @pilon Malcolm
  10. @OldPete You did not mention which version of osC your site is running. However, I will guess that it is an older version. ** ALL ** of the older 'official' versions of osC are not coded to run under newer versions of PHP, and WILL CRASH as hosts upgrade the version of PHP they are running! Your options are: 1) Get your host to down-grade you to an earlier version of PHP (v5.x). This is ONLY A TEMPORARY FIX, and many/most hosts are discontinuing support for older versions of PHP. 2) Look at the code in the examples that Hotclutch linked to, and apply ALL of the changes in his code to your site. No, he is not trying to SELL you anything. Be aware that there is a LOT of updates needed to get the old osC code to run under newer versions of PHP. If you don't feel comfortable doing this yourself, you can hire someone to do it for your (again, Hotclutch is NOT trying to sell you something). 3) Look into one of the newer 'unofficial' versions and/or forks of osC. Hotclutch linked to two versions. There are others. Many of these will offer improvements and upgrades from your old version (such as a responsive display, that adjusts the page layout depending on the screen size of your customers. This is crucial in today's age where most people are using mobile devices). None of these are an in-place upgrade. You would need to install the new code in a new directory, migrate your data over (customers, products, sales history, etc), and apply any mods or add-ons you had in your old shop (make sure they are compatible with whatever new shop code you use!). If you are not comfortable doing this yourself, you can hire someone to do this for you (again, Hotclutch is NOT trying to sell you something). 4) The original developer of osC has sold the name and code to a new party. This new party has announced that they will be releasing a new 'official' version of osC (v4), and will offer a migration path from older versions. However, this new version is late, and the new owners have not been active in keeping us informed as to when it will be available. I am sure that there are other options (like moving to a different shopping cart program), but this will give you an idea of what is needed for you to move forward. HTH Malcolm
  11. @douglaswalker Which version of osC are you using? You posted this thread under the "osC v 4" description, but I suspect you are using an earlier version. I just need to know so I can move this thread to the proper place. M
  12. ArtcoInc

    Add all products to cart

    @Smoky Barnable Maybe you could use a 'bundle' or 'kitting' add-on? Create a bundle, or kit, consisting of one of each of the items. M
  13. @douglaswalker osC version? (just need to know where to move this thread) M
  14. ArtcoInc

    is oscommerce still alive? help this old man

    @johnathansmith1969 Development of the 'official' version of osC stalled several years ago. The last 'official' release will not run under newer versions of PHP, and is not responsive (adjusting the display to fit the screen size ... much needed these days as more people are using phones and tablets). Support for the 'official' code was (and still is) active here on this forum. Recently, new owners bought the rights to the osC code and name, and have announced that a new version will be released with some much needed updated. We are waiting to see what will be released, and when. Since osC is 'open source' code, some people have taken the 'official' code, and have spun off their own 'forks' of the osC project ... * Some have only updated the 'official' code to run under newer versions of PHP (as more web hosts upgrade to newer versions of PHP, older versions of osC will crash). * Some have updated the code to not only run under newer versions of PHP, but also include provisions for being 'adaptive' . * And some have gone so far as to completely update the code, and include additional features and functionality. While originally based on osC, these have essentially become their own projects. But, since this is a forum for the 'official' version of osC, we are not allowed to discuss, or support, any of these forks here. So, like Schrödinger's cat, osC is both alive and dead. While the the last 'official' version of osC still 'works' (sort of), it is not truly practical in today's environment. A new 'official' version of osC has been announced, but we don't know what it will consist of, nor when it will be available. And lastly, development on osC 'forks' still continue, but they are just that ... 'forks' ... and as such, are not supported here on this 'official osC' forum. HTH M
×