Jump to content
Latest News: (loading..)

ArtcoInc

Members
  • Content count

    1,331
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by ArtcoInc

  1. ArtcoInc

    Navbar Links

    @JcMagpie The OP hasn't been here in almost a month. Thanks, though.
  2. If you have not downloaded the Final/Frozen version, DO SO NOW! As I understand it, the Github project has been archived, and is pending deletion! Since there will be no more development on it, I propose posting any bugs and/or fixes here. I'll start: In the Also Purchased module ... There is a tiny mistake in cm_pi_also_purchased.php. Line 62 has "Enable Reviews Module" instead of "Enable Also Purchased Module".
  3. ArtcoInc

    Site been working for a year, now broken!

    @Enzo79 What version of PHP was your host using before the upgrade? Can you ask them to roll PHP back to a prior version? Do you have a full backup of your site (both files AND database) from before you made your 'security' changes? M
  4. ArtcoInc

    New Products Listing

    @FXBO To be honest, I did not know the answer to this. So, I started exploring ... I find it useful to use your browser's 'View Source Page' (or whatever the nomenclature is for your browser) of the actual store. Once I find the bit of code that defines an action, I then use a tool such as Windows Grep to search through all the php files, and find the specific file that has that bit of code. HTH M
  5. ArtcoInc

    New Products Listing

    @FXBO There are 2 "New Products" ... One for Index, and one for Index_nested. Which did you change? M
  6. ArtcoInc

    New Products Listing

    @FXBO Admin -> Modules -> Content -> New Products -> <edit> -> Maximum Display HTH M
  7. @tothcom As I mentioned, the only person that can make these changes has been absent. So we, as the community, are doing what we can, with what is available to us. osCommerce is an Open Source project. There have been a number of people/teams who have taken the osC source code and 'spun off' their own shopping carts. You may too, if you choose. However, you can not call yours "osCommerce". M
  8. @makeit4me As @MrPhil said, the 'official' v2.3.4 (and v2.3.4.1 hot-patch) is very much out of date. The osCommerce project was lead by one person that has been absent for quite some time. In his absence, the "community" has continued with the development of osC. Unfortunately, that one missing person is the only one that can make this continued development an 'official' release. The 'Community Edition' (also called osC-CE (for Community Edition), osC-BS (for Bootstrap, the platform it is based on), osC-Edge, osC-Final, and/or osC-Frozen. These are all different names for the same thing) is a big improvement over the last 'official' v2.3.4 release in a number of ways: 1) It is responsive. This means that it will adjust the screen layout depending on the size of the screen of your customer's device. This is very important in this day of mobile devices. The 'official' version is not responsive. 2) It will work with the newer version of PHP, the scripting language used in osC. As more and more hosts upgrade their servers to PHP 7.x, older versions of osC (including the 'official' version) will crash. 3) It is much more modular. This means that you can turn features on or off, change the layout, or even add new features, all without touching the core code. You can find a link to the latest version of the Community Edition in my signature below. Malcolm
  9. ArtcoInc

    Fatal error, webhost is stumped

    @brian_cee Do you have a full backup of your site (both files AND database) before the crash? Malcolm
  10. ArtcoInc

    Nothing happens after install

    @MrPhil Yes, the store's root (ie: /catalog). I did say " the root directory of the shop ". M
  11. ArtcoInc

    Nothing happens after install

    @Subbie If I understand you correctly, you are using the 'official' v2.3.4.1 version of osCommerce, correct? As @raiwa mentioned earlier, the 'official' version is very much out of date! The osCommerce project was lead by one person that has been absent for quite some time. In his absence, the "community" has continued with the development of osC. Unfortunately, that one missing person is the only one that can make this continued development an 'official' release. The 'Community Edition' (also called osC-CE (for Community Edition), osC-BS (for Bootstrap, the platform it is based on), osC-Edge, osC-Final, and/or osC-Frozen. These are all different names for the same thing) is a big improvement over the last 'official' v2.3.4 release in a number of ways: 1) It is responsive. This means that it will adjust the screen layout depending on the size of the screen of your customer's device. This is very important in this day of mobile devices. The 'official' version is not responsive. 2) It will work with the newer version of PHP, the scripting language used in osC. As more and more hosts upgrade their servers to PHP 7.x, older versions of osC will crash. 3) It is much more modular. This means that you can turn features on or off, or even add new features, all without touching the core code. You can find a link to the latest version of the Community Edition in my signature below. Now, having said all of that, the Community Edition has a file in the root directory of the shop called user.css. This is the last CSS file called, and thus will override all other CSS definitions. Out of the box, this file is empty. This is where you, the shop owner, put all of your CSS definitions. This way, you do not have to edit any of the stock CSS files. The user.css file does not exist in the 'official' version of osC. HTH Malcolm
  12. ArtcoInc

    Add Zones to Shipping Zone Rates

    @jimormsbee How many shipping zones do you want? (in particular, post #4) Also this one ... Basically, do a search here in the Forum for 'Shipping Zones'. M
  13. ArtcoInc

    New install messing about.

    @Mtareq http://www.oscommerce-templates.co.uk/ These are all from the developer who lead the Community Edition project. Not free, though . And, as @MrPhil mentioned below, the Community Edition IS responsive, out of the box. No template needed! But, if you want to buy a template instead of doing the styling yourself, check out the above site. M
  14. ArtcoInc

    Add Zones to Shipping Zone Rates

    @jimormsbee Are you looking to set up TAX zones, or SHIPPING zones? M
  15. ArtcoInc

    New install messing about.

    @Mtareq Yes, nowhere does the osC site say that the 'official' version of osC is obsolete and one should use the Community Edition, nor offer a link to it. This is an issue we have been fighting for a while, and is not your fault. That said, while you have already made up your mind, may I point out that you were having issues with a 3rd party template. Many (if not most) of the 3rd party templates out there are very poorly written, often overwriting lots of the core code. And, neither the osC team, nor the community here, can offer support for any of the 3rd party templates. So, I urge you to at least do one clean install (no 3rd party template) of the Community Edition (link in my signature below) and give it a try. If you have any problems with it, support is here. M
  16. ArtcoInc

    Add Zones to Shipping Zone Rates

    @jimormsbee It is a module already included in osC 2.3.4.1 CE. You just need to "turn it on" by following the instruction @JcMagpie laid out. M
  17. ArtcoInc

    osCommerce Online Merchant v2.4.0 Joli Beta

    @Ninolan The osCommerce project was lead by one person that had been absent for quite some time. In his absence, the "community" has continued with the development of osC. Unfortunately, that one missing person is the only one that can make this continued development an 'official' release. The 'Community Edition' (also called osC-CE (for Community Edition), osC-BS (for Bootstrap, the platform it is based on), osC-Edge, osC-Final, and/or osC-Frozen. These are all different names for the same thing) is a big improvement over the last 'official' v2.3.4 release in a number of ways: 1) It is responsive. This means that it will adjust the screen layout depending on the size of the screen of your customer's device. This is very important in this day of mobile devices. The 'official' version is not responsive. 2) It will work with the newer version of PHP, the scripting language used in osC. As more and more hosts upgrade their servers to PHP 7.x, older versions of osC will crash. 3) It is much more modular. This means that you can turn features on or off, or even add new features, all without touching the core code. You can find a link to the latest version of the Community Edition in my signature below. Malcolm
  18. @zefeena 1) Are you running a SSL certificate on your site, either partially or entirely? 2) Do you know if your host is running a Linux or Windows server? M
  19. @jimormsbee The Zack template was written by the developer that has headed up the Community Edition of osC. I have many of his modules ... they are all very good, and his support is excellent. M
  20. ArtcoInc

    Multi Vendor for 2.3.1

    @abd Since you are new here, you may not have realized that DigiScrapDeal posted this thread 6 years ago, and has not been back here since. 1) The add-on s/he initially referenced was written for osCommerce v3.0, which was never released as a finished product. v3.0 has a very different code base than v2.3.4.x, and add-ons written for it almost certainly will not work with v2.3.4.1 without some major changes. 2) In his second post, s/he referenced another thread where people also wanted assistance with adapting it to osC 2.3.x. There wasn't much help there either. If you are unable to adapt this add-on to your store, you can post a RFQ in the commercial part of this forum to see if you can hire someone to do this for you. Lastly, if you are using the 'official' v2.3.4.1 version of osC, please note that it is very much out of date! The osCommerce project was lead by one person that had been absent for quite some time. In his absence, the "community" has continued with the development of osC. Unfortunately, that one missing person is the only one that can make this continued development an 'official' release. The 'Community Edition' (also called osC-CE (for Community Edition), osC-BS (for Bootstrap, the platform it is based on), osC-Edge, osC-Final, and/or osC-Frozen. These are all different names for the same thing) is a big improvement over the last 'official' v2.3.4 release in a number of ways: A) It is responsive. This means that it will adjust the screen layout depending on the size of the screen of your customer's device. This is very important in this day of mobile devices. The 'official' version is not responsive. It will work with the newer version of PHP, the scripting language used in osC. As more and more hosts upgrade their servers to PHP 7.x, older versions of osC will crash. C) It is much more modular. This means that you can turn features on or off, or even add new features, all without touching the core code. You can find a link to the latest version of the Community Edition in my signature below. Malcolm
  21. ArtcoInc

    edit privacy.php

    @mairei Even though I am in the English side of the forum, your post came across my feed, so I opened it. I did not translate your question or problem, but I did notice this problem in your language file. That's why I pointed it out. If you have not had any problems with this, please ignore my post(s).
  22. ArtcoInc

    edit privacy.php

    @mairei In your first post in this thread, you posted your privacy language file. Since the forum uses colors to distinguish different code pieces, it is easy to see that you have a problem in this file. About 2/3's of the way through the file, you will notice that the text changes from green to black. That is because you have an apostrophe in the word " author's " . This apostrophe closes, or ends, the text definition, resulting the remaining of the text potentially causing errors or problems. You need to 'escape' that apostrophe (and any others), either with a leading backslash, or by replacing it with the HTML code &apos; . HTH
  23. Once again, this thread has devolved into a bunch of semi-related topics, all being discussed (argued?) in a random fashion. Let's see if we can bring this together (somewhat). As I see it, the initial issue has expanded to now include: 1) Guest checkout, 2) One page checkout -vs- multi page, and 3) What information is required in order to create an account. So, let's take these one at a time ... 1) Out-of-the-box, osC requires a customer to create an account. There is one very popular add-on (and a number of less popular ones, although most of them probably have not been updated to the latest code base) that adds the Guest Checkout functionality to osC. I use it in my store. It's strange ... I have repeat customers that still prefer to use the Guest Checkout. When one boils it all down, the only thing between a guest checkout and a registered customer is a password. So be it; give them what they want. However, consider what a Guest Checkout *doesn't* have ... Without an account (ie: password), the customer can't check on the status of their order, nor review their purchase history, leave reviews or testimonials, etc. (yes, I acknowledge that there is a commercial module available to allow some of that). If a customer is only ever going to make that one purchase, than these things may not be important. But, if there's a problem with the order I places in your shop as a guest, how can I follow up on it? And, maybe we, as store owners, need to emphasize better the benefits of having an account. 2) This has been discussed here many times. Do you want one LONG checkout page, or a couple of shorter ones? *IF* the customer enters the checkout process, and has no idea where they are, that's bad. On the other hand, *IF* it is clearly shown where the customer is in the checkout process, and what's left to do, a couple of smaller pages are fine (IMHO). I also think that using popup Modals in an effort to reduce the page length is a bad idea, especially if the customer is on a mobile device. 3) Out-of-the-box, to create an account, osC requires the customer's gender and date-of-birth. These are easily turned off in Admin (I do in my stores), and should not be a consideration in what information is needed to create an account. The other main thing that osC asks for is the customer's address (we'll set aside the newsletter sign-up for now). So, if I create an account without having to enter an address, I'll have to enter it when I place an order (see #2 above). And, if I place more than one order through the shop, having to enter my address with each order hasn't saved me any time, has it? The point is, you're going to have to ask for the customer's address somewhere in the relationship. Do you ask up front, or later on? If one wishes to explore yet another option, consider this: Your customer comes into your shop, puts something into their cart, and starts the checkout process. There is only one checkout process. Don't even bother saying, "If you have an account, please log in." The first thing asked for is the customer's email address. Your store checks to see if that email address is associated with an account. If it is, a Modal pops up saying, "Welcome back, <first name>. Please enter your password", logs the customer in, and pre-fills the checkout form. If the email address is not associated with an account, the 'guest' checkout process continues with the customer filling out things as they go. At the very end, after the order is finalized, the (still 'guest') customer is now asked if they want to create an account. All of the benefits are explained, and the customer only has to enter a password. If none is entered, no account is created. To expand this idea further ... if when the customer enters their email address, and there is no account associated with that email address, but there are prior orders (as guests) linked to the email address, your shop could acknowledge the prior orders, re-emphasize the benefits of an account, and ask again if they want to create an account. The bottom line is ... there is no one right answer. As store owners, we can tailor our shops to what our customers want (or, at lease, what we think they want). Since osC is open source, we are free to change anything we want. And, with all the development work being done to make it more modular, these changes are becoming easier to make. (we return you to your regularly scheduled bickering)
×