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. @Owl Sauron If I may ask, exactly is it you are trying to do? Is it, if an item has attributes (ie: options), and your customer selects one of the attributes, you want the price shown on the page to reflect the actual cost, with all of the options applied? @Tsimi If the above is correct, didn't Burt have a module to do this in his last 28 days bundle? M
  2. @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
  3. @MrPhil Yes, the store's root (ie: /catalog). I did say " the root directory of the shop ". M
  4. @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
  5. @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
  6. @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).
  7. @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 ' . HTH
  8. @ezfindit (while not exactly on topic ...) Is it only in the Order Confirmation email that you want this changed? M
  9. @phi148 Is this on a live site? If so, do you have a link? M
  10. @burt This is what I was asking about ... if this was even possible. Way above my pay-grade, though. I had considered creating a new table instead of adding additional fields to the existing Countries table, but thought it would require more work than it was worth. I may have to reconsider that. But, since Admin is not modularized, there is no built-in way to install any new modules. The store owner would have to manually copy files, run something like phpMyAdmin to work on the database tables, etc. Definitely not a copy/one-click install/configure/go type of thing. So, maybe this isn't something that really is suitable as an add-on. At least, not one that tries to conform to proper coding practices. Thank you, though! M
  11. @burt Let's say that I want to add additional fields to the 'countries' table. And, to be able to administer these new fields, I will want to make changes to /admin/countries.php (a core file). To change this file, I could overwrite the stock /admin/countries.php file. Not the best choice, in my opinion. Even in Frozen, the stock ADMIN menus are still hard coded (in this case, the link to /admin/countries.php is in /admin/includes/boxes/localization.php). So, instead of overwriting /admin/countries.php, let's say that I call my new admin file something like /admin/new_countries.php. I can add a link to my new file to the menu (I have seen how to add a new menu item to the array), but the stock link to the stock /admin/countries.php file would still be in the menu. I'm concerned that a shop owner (or some hired help) might use the stock /admin/countries.php link and file, and possibly mess up the database table. I could overwrite the /admin/includes/boxes/localization.php file, but there's the chance that the store owner has already made their own changes to /admin/includes/boxes/localization.php, so overwriting it would also not be a good choice. What I originally asked was ... is there a way THROUGH THE ADD-ON INSTALLATION process, to be able to remove (or hide) a link in /admin/includes/boxes/localization.php menu file, and be able to add it back (or un-hide it) if the add-on is ever uninstalled? After some additional thought, though, I might have a better solution. During the add-on installation, I could: 1) rename the stock /admin/countries.php file to something like /admin/countries.old, and 2) copy my new /admin/countries.php file into its place. This way, no changes to the menu structure have to be made. And, if the store owner ever chooses to uninstall the add-on, the new /admin/countries.php file would be deleted, and the renamed /admin/countries.old file would be renamed back to /admin/countries.php. Thoughts? M
  12. (using osC Frozen) I am working on an add-on that expands the functionality of one (or more) of the stock, built-in ADMIN modules, and it involves adding additional fields to the existing databases. Since ADMIN is not modular (yet), I can't just un-install the stock module(s). So, I can either: 1) Overwrite the stock modules (clearly not the best choice), or 2) Give the new modules different names, and just add the new module name(s) to the menu structure. But, this would leave the original modules intact and still in the menu structure, where: a) the original module may not functional any more, or worse, b) they may actually mess up the newly expanded database tables. or 3) Add the new module names to the menu structure, and try to figure out a way to remove the original module names from the menu structure (and add them back if the new module is ever removed). I have seen examples of how to add a menu item, but not how to remove a stock one (without editing the 'core' menu definition files (I suppose I could just replace the stock menu definition files, and put the original ones back if uninstalling. But, that could mess up someone that had already hand edited their menu definitions)). Can someone point me toward a Best Practice way to do this? TIA Malcolm
  13. @rebecca@goldiemediagroup Unfortunately, NO. The lead developer here on the osC project has been absent for some time. The last 'official' release was v2.3.4.1, which was just a hot-fix to version 2.3.4. And, both of these are, unfortunately, very much out-of-date! With no further 'official' development being done, the community has stepped up and continued with the development. Unfortunately, only the lead developer can declare what the community has done to be an 'official' release. And, since he hasn't been here, that hasn't happened. So, NO. What your host has available is NOT up to date. Sorry ... M
  14. @rebecca@goldiemediagroup Welcome to the osC forum. In the future, it is VERY useful if you first tell us which version of osC you are using, which version of PHP, and any add-ons you may have installed. Since you say that you do not have a Content folder, it *sounds* like you are using an older version of osC. The version of the Stripe payment module is probably written for the newer version(s) of osC. If this is a new installation, I'd STRONGLY suggest that you start over with the latest Community version of osC (link in my signature below). The Community version of osC (sometimes called osC CE, osC Edge, osC Final, or osC Frozen. All the same thing) is compatible with PHP v7.x, is responsive (meaning it will adjust how your store is displayed depending on screen size of your customers), and is much more modular (you can enable and disable modules, or add new modules, all without any core code changes). Older version of osC WILL crash and burn when your host upgrades their version of PHP. M
  15. @sinopia A stock 2.3.4 shop will have issues with PHP 7. To try and make your old store work under PHP 7 will take a lot of work, and will result in a FrankenShop fork that no-one else will be able to support. Your choices are: 1) Spend a lot of time and effort to make your shop run under PHP 7 (not recommended), or ... 2) Ask your host to roll PHP back to 5.x (a temporary fix, while you ...) 3) Upgrade your shop to the latest Community build of osC (link in my signature below). M
  16. @sinopia Is this a new installation? If so, please realize that osC v2.3.4 is way out of date, and will not continue to run as our hosts upgrade to the newer versions of PHP. So, if this is a new install, I'd strongly suggest you start over with the Community build of osC (see link in my signature below). If this is not a new installation, you should begin thinking about moving your shop up to the latest version. Unfortunately, it is not an in-place upgrade. You'd basically create the new store in a separate sub-directory, migrate over your database and images, and re-apply any add-ons and/or styling changes you made (you kept good notes, didn't you?) M
  17. Ok, I came up with a workaround ... I added the opening <form> line to the options_attributes template file too. Then, in the buy_button template file, I tested to see if there were any attributes. It there are, I do NOT add the opening <form> line, since it is already added in the options_attributes template. If there are NO attributes, I do add it in the buy_button template. Seems to be working so far (fingers crossed). M
  18. I started to play around with this again, adapting it to work with Edge/Frozen. I moved the <form> line of code from product_info.php into the Buy-Button template file, and it works! ... except ... If the product has attributes, not only don't the attributes get added to the order, the product does not get added to the cart at all. Back to the drawing board ... M
  19. @deepsonline This is the second post you've made where you have not indicated which version of osC you are using. This is critical for anyone to help you. That said, if you are running any version of osC other than the Community Edition version (sometimes called osC-BS (for BootStrap), or Gold, or Edge), there will not be any Hamburger. The Hamburger is ONLY available on the responsive CE version. And no, you can not add that feature to the non-responsive version. 'Official' development on osC has stalled for several years (for reasons I won't go into here). The community stepped up and developed the CE version. While it is not an 'official' version, it is the latest, and offers responsiveness (the display adjusts to the device's screen size), is much more modular (you and enable and disable features, and even add new features, all with any core code changes), is PHP 7.x ready (older version of osC will crash when your host upgrades their version of PHP), etc). Unless you are trying to work on an older existing store, I strongly recommend that you start over with the CE version of osC (link in my signature below). And, as for your other question regarding a Template system, the 'official' version of osC was not designed to accept templates. The companies that offered templates hard-coded their design changes into the osC code. Some were coded well, most weren't. The CE version of osC is based on the Bootstrap framework. With this, color schemes and similar design elements can be changed through CSS, all without core code changes. Plus, there are commercial templates available for the CE version. HTH Malcolm
  20. @valquiria23 I looked at the add-on in question. I see some language additions and some logic changes in the contact_us.php file. Just from a casual glance, neither should be a problem with Edge. However, there are some input field additions in the contact_us.php page that will likely need to be tweaked to work with Edge. Not too much of a chore, but something there none the less. Two notes: 1) You can eliminate adding the additional input fields (they added a Company and Phone Number field), but you will also have to delete all other references to these fields in the new logic code. So, it's a question of which is more important (or easier) ... keeping the additional fields, or removing all references to them in the logic code. 2) The author has two sets of instructions intermingled ... one set for if you have another add-on (called Visual Verify Code) installed, and another for if you don't. Pay attention, and don't get the instructions mixed up. HTH
  21. @valquiria23 Considering that the files were last updated in 2009 (pre bootstrap, pre osC 2.3.x), I will assume that you will have to make some edits and changes to make it work with Edge. Malcolm
  22. @indigoinstruments While this doesn't answer your specific question (and no, I didn't test any of these with v2.2), have you read this: HTH Malcolm
  23. There is also a lot of good information regarding this add-on in its support thread:
  24. @graveyardrecords I have used that menu app, and it does work fine on a desktop pc. Mind you, you have between 250 and 300 categories, so any drop-down menu is going to fill up a lot of space! Malcolm
×
×
  • Create New...