Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

ArtcoInc

Members
  • Posts

    2,108
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by ArtcoInc

  1. @LeeFoster By chance, are you running PHP v7.x ? M
  2. @sinopia Just out of curiosity, which theme did you buy? I see 7 themes for osCommerce there, some of which haven't been updated in years! As others have mentioned, *most* themes available for osCommerce are poorly written, including many hacks to the core code. This makes the themed code a 'fork' in the osCommerce line. As such, the community here can not offer support for any of these themed forks. We have no way of knowing what changes the theme made to the core code. So, you will need to go to TheThemeForest for support (good luck!). Or, start over with the Community Edition of osCommerce (link in my signature below). M I just re-read your post stating that the owner/item has been removed from TheThemeForest.
  3. @sinopia When you say "2.3.4", do you mean the 'official release' of osCommerce, or the responsive Community Edition? M
  4. @fantomen I understand the convenence of being able to edit information pages through Admin, and not having to deal with uploading new files anytime you want to change the text in these pages. In fact, I have used one of these type of packages in one of my shops. However, I won't be using one for any future shops, and I will most likely remove it from the existing site. Here's why: I find that for the type of shops I run, I want the information of ALL pages to be searchable. If a customer enters a search request for some information that is on one of these pages, they won't find that page using one of these packages. So instead, I am using a search module that allows my customers to search products, categories (where I have a LOT of information), and any standalone page that uses a language file to display that page's content. So, if my customer searches for "entertaining" or "adult only", they can find those expressions, even if they are not in a product's name (the stock search function is limited to just the product name). Also, pay attention to how these packages work if you intend to have more than one language on your shop. HTH Malcolm
  5. This reminds me of something I heard years ago. Television stations were told that they could not turn up the audio volume on commercials. So instead, they turned the volume down for the program. Whether it is true or not ... I also see people involved in private transactions often asking for the buyer to pay the Paypal fees ...
  6. @fantomen As @Jack_mcs has pointed out, this add-on was written for an earlier version of osCommerce. You can adapt it to 'Frozen', but it will require a few edits to the add-on code. While I have not downloaded this add-on to examine the code, here are some of the changes you will have to make: Some time ago, Burt got rid of the filenames.php and database_tables.php files. Instead, all calls to a file, directory, or database table are now hard-coded (in both the core code, and in any add-on). You can address this in one of two ways: 1) Install the compatibility add-on http://addons.oscommerce.com/info/9506 2) Hard-code the paths into this add-on. This is not difficult to do ... probably the biggest mistake people make is that they miss one (or more) of these needed edits. (like I said, I have not downloaded this add-on, so the following example are just that ... examples. You will have to find the applicable code in your add-on) Search through the code, and wherever you find something like this: require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_CREATE_ACCOUNT); notice the names in capitol letters. You will have to change both of these: a ) Where it says DIR_WS_LANGUAGES , this was a definition in the configuration file telling where the LANGUAGES directory is. You will need to change this to the actual directory name, which in this case is languages/. b ) Where it says FILENAME_CREATE_ACCOUNT, this is where the filenames.php file defines what the CREATE_ACCOUNT file is called. You will need to change this to the actual file name, which in this case, is create_account.php. Changing both of these will result is something like this: require('languages/' . $language . '/create_account.php'); (like I said, this is just an example, and not some actual code from this add-on) So, just go through all of the code in the add-on, and search for anything with all capitol letters. If it starts with DIR_ , it is a directory name. If it starts with FILENAME_ , it is a file name. c ) In any database call, you will see something like this: $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from " . TABLE_CUSTOMERS . " AS a, " . TABLE_ADDRESS_BOOK . " AS b LEFT JOIN " . TABLE_ZONES . " as c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company,customers_lastname"); let me reformat that to be easier to read ... $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from " . TABLE_CUSTOMERS . " AS a, " . TABLE_ADDRESS_BOOK . " AS b LEFT JOIN " . TABLE_ZONES . " AS c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company, customers_lastname"); There are three entries that begin with TABLE_ . These are the database table names, and will now have to be hard coded. In this case, TABLE_CUSTOMERS refers to the customers table, TABLE_ADDRESS_BOOK refers to the address_book table, and TABLE_ZONES refers to the zones table. So, the edited command would now be: $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from customers AS a, address_book AS b LEFT JOIN zones AS c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company, customers_lastname"); (like I said, this is just an example, and not some actual code from this add-on) d ) One other coding style has changed, preparing osCommerce for newer versions of PHP. In the code, you may find something like this: $email_address = tep_db_prepare_input($HTTP_GET_VARS['email_address']); if (!@ $HTTP_POST_VARS['action']) { Whenever you see a $HTTP_POST_VARS or a $HTTP_GET_VARS, these will need to be changed to $_POST or $_GET, respectively. Please note that these changes are to make the code compatible with newer versions of PHP, and is not an indication of the add-on, or of osCommerce. If you can apply all of these changes, and get this add-on to work properly, you could then give back to the community by uploading your updated code to the add-on repository. If you find that this it too much for you to do, you can always post in the commercial portion of the forum to hire someone to do this for you. If you do do this, please pay it forward by uploading the revised code to the repository. Or, as @Jack_mcs has suggested, you could try another add-on. HTH M
  7. @fantomen Like the instructions said, in the default installation of osCommerce, the shop is loaded in the /catalog sub-directory. This is the 'root' of the shop, NOT the domain. This is typically done so that you may have other functions (ie: a blog, etc) under your domain. For example: <your domain> <your domain>/catalog/ <your domain>/<your blog directory> <your domain>/<any other function or directory you want> If you have installed osCommerce in the root directory of your site, just ignore the part of the instructions where it includes the directory path "catalog/", and do the changes in the root directory of your site. HTH M
  8. @churchillj54 If you site used to work fine with the Paypal module, and now it doesn't, that usually means that something somewhere has changed. Ask your host if they updated anything, especially if they updated the version of PHP the server is running. Many hosts will deny that they changed anything, but if pressed, will finally (and/or reluctantly) admit it when they have indeed made a change. M
  9. @14steve14 Depending on the shipper .... UPS, in my experience, starts at a base rate, and adds to that with the addition of the packages weight. M
  10. @nedragdnuos Many of the 'warnings' you are getting is because PHP v7.2 is MUCH more strict that prior versions. I think you are going to find that many (if not most) add-ons are not PHP v7.2 ready. And, even the 'Frozen' version of osC has some PHP v7.2 issues. So, unless you are running the latest 'Edge' version of osC, it may be better to fall back to PHP v7.0 (or maybe even v7.1), and these warnings should go away. M
  11. @nedragdnuos Which version of PHP are you running? M
  12. osC v2.3.3.4 BS (yes, it's that old) I received an order this morning where all of the order details are there, including different billing and shipping addresses. However, the Customer Number shown is '0', and there is no record of the customer in the customer table. I have the Create Account and Order Maker add-on installed (I've manually created orders with it many times), so I figured I'd manually create the customer, and edit the order table to point to the newly created customer number. Unfortunately, after entering the customer information, it keeps looping back when I click on the 'confirm' button, and no customer info is saved. Help?
  13. Which version of osCommerce are you using? The standard English language included with osCommerce is usually sufficient for use here in the USA. And, you can 'tweak' the wording for just about anything, by editing any the language files that come with osC. Be sure to back up your shop before making any changes 🙂 M
  14. @Chrisso While I see that your site is in both English and German, your 'Conditions of Use' page is only in German. Malcolm
  15. @odracirjf AFAIK, osC Frozen is ready for PHP 7.1. Development is still happening to bring it up to PHP 7.2. I think you'll find that unless any add-on has had a very recent update, most (if not all) they will NOT be PHP 7.2 ready (or even PHP 7.x, if the add-on is quite old). If you want to help support the community, and if you find an add-on that you want, and put in the effort to bring it up to PHP 7.2 ready (and/or osC Frozen ready), please upload your work to the add-ons site, so others may benefit from your efforts. M
  16. @odracirjf Which version of osCommerce are you using? If you are doing a new install, please make sure you are using the Community Edition of osCommerce (link in my signature below), and NOT the last 'official' version. Which version of PHP are you using? I'm guessing it is 7.2 ? M
  17. @lucsangel PHP 7.2 is much more strict than prior versions. Both Frozen and almost all add-ons need updating to work without warnings under 7.2. If you can try running PHP 7.1, I think most of those warnings will go away. M
  18. @puggybelle What was the original product title? By chance, did it have any unusual characters in it? M
  19. @Chrisso They are all just different names, used over time, as the development continued. 'Frozen' is the last released version. I am sure that there are developers in the Commercial Support area of the English forum that could assist you with migrating your products. Do be aware that the Community Edition may not have the German language translation complete. You could assist the community if you were able to help in the translation, and make that available back to the community. Malcolm
  20. @Chrisso osCommerce v2.2 is very old, has many security risks, and will begin to crash as your host updates their servers. So, your choice is to upgrade to the latest version of osCommerce, or move your shop to another shopping cart (such as WooCommerce). If you move to another cart, you will be starting from scratch. You may be able to bring your customers, products, and sales history over, but the information may, or may not, be complete. If you stay with osCommerce, there is an upgrade path from v2.2 to the last 'official' version, but I do not recommend it. To try and patch your old v2.2 store up to the latest 'official' version would result in a "Frankenstore", resulting in code that no-one else can support. You would basically be making your own fork of osC. Unfortunately, the last 'official' v2.3.4 (and the v2.3.4.1 hot-patch) versions are also 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. And, while versions 2.4 and 3.0 were announced years ago, but there has been no development done on these in years. There are several people working on their own 'forks' of these versions, but they are doing so on their own, without any acknowledgement or support from the osC team. The latest version of osC is the 'Community Edition'. Sometimes called by different names (osC-CE (for Community Edition), osC-BS (for Bootstrap, the platform it is based on), osC-Edge, osC-Final, and/or osC-Frozen), it 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. So yes, the Community Edition is contemporary in regards to privacy, responsive design, security, etc. Many of the more popular add-ons (or apps) have been updated to work with the Community Edition. The better ones are also following the current coding style of no core code changes. Simply copy the files to your server, enable the new module(s) in Admin, and configure them. You can find a link to the latest version of the Community Edition in my signature below. Now, having said all of that, there is no 'upgrade path' to the Community Edition. You would install it clean into a separate directory on your server (local or hosted), and migrate your images and data over from the old store. This will not carry over any mods or customizations you may have done to your original store. You would have to apply these all over again (the person from whom you inherited the shop keep notes on what they did to the shop, right?). Fortunately, many of the mods needed in the older versions of osC are now built-in in the Community Edition. Any styling changes will have to be applied again too. That said, it's probably time to give your shop a 'face lift' anyway, to keep it fresh and current. Finally, the lead developer of the Community Edition created a bundle of modules earlier this year that address the new GDPR regulations. So, if you move to a new cart, or stick with osC, you will essentially be building a new shop. If you want to keep your customers, products, and sales history, you'll have to migrate that from your old store. HTH Malcolm
×
×
  • Create New...