Jump to content
Latest News: (loading..)

ArtcoInc

Members
  • Content count

    1,468
  • Joined

  • Last visited

  • Days Won

    30

Reputation Activity

  1. Like
    ArtcoInc got a reaction from raiwa in Frozen bug list   
    As a store owner, I don't want to have to visit Github (or wherever) to see if there are any patches I need to apply to my live store(s). For me, I was very happy when Edge/Final/Frozen was 'finished'. That's not to say that there aren't any bugs still in it. That's the reason for this thread ... a place to document bugs, and hopefully fixes.
    I am also pleased that development is still happening. Keep it up, guys. Use this thread as a source of information to improve your forks. But please, for this thread, let's keep it just for Edge/Final/Frozen, ok?
  2. Like
    ArtcoInc got a reaction from PiLLaO in Frozen bug list   
    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. Like
    ArtcoInc reacted to Jack_mcs in Frozen bug list   
    I've been thinking of doing the same. Here are some changes that should be made (not all are mistakes):
    1 - In includes/modules/content/product_info\templates/tpl_cm_pi_price.php, the variables in sprintf are in the wrong order. Change
    <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $specials_price, $products_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> to
    <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $products_price, $specials_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> 2 -  In languages/create_account_success.php change priviledges to privileges.
                                                                          
    3 - In languages/shopping_cart.php change two instances of "don't" to "don\'t".
    4 - In languages/shopping_cart.php change "immediate deliver" to "immediate delivery".  
    5 - In includes/application_top, add the deprecated flag to prevent future warnings and disable display errors since it is a security hole by changing
    error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); to
    error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_USER_DEPRECATED); ini_set('display_errors','0'); 6 - In includes/template_top.php, change the version number to the current one because some icons being used won't work in V 5.0.6.
    <script defer src="https://use.fontawesome.com/releases/v5.0.6/js/all.js"></script> to
    <script defer src="https://use.fontawesome.com/releases/v5.0.9/js/all.js"></script>  
  4. Like
    ArtcoInc got a reaction from PiLLaO in Frozen bug list   
    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".
     
  5. Like
    ArtcoInc got a reaction from PiLLaO in Frozen bug list   
    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".
     
  6. Thanks
    ArtcoInc got a reaction from ce7 in untouchable genearl.php   
    @ce7
    It is never wise to mix files from different versions of osCommerce.
    You said that you are using osC Edge, and have the compatibility add-on installed. You are now trying to install KISSit Image Thumbnail when you discovered this problem. Is this all running on an in-house server, or on your host's server? What version of PHP is being used?
    Dreamweaver is NOT a good tool to use when editing osCommerce files. Many people recommend Notepad++ (which I use, although I also use plain old Notepad most of the time). Notepad++ also uses colors to highlight areas and/or missing bits.
    If your files are on your host's server, some FTP clients (such as Filezilla) allow you to edit the file directly on the server (well, it makes a copy on your workstation, you edit it there, and then it uploads it back to the server). The other way is to have a complete copy of all your files on your local workstation, edit them locally, then upload any edited files back to the server.
    As @Jack_mcs pointed out, there are some blank spaces before the opening <?php in the code you posted. This can cause the PHP engine to crash. Remove those blank spaces, so that <?php begins in the first column.
    HTH
    Malcolm
  7. Like
    ArtcoInc reacted to 14steve14 in Restoring 'Searches in Description' functionality of header search box   
    I just installed the twitter typehead search. https://apps.oscommerce.com/c1sKS&twitter-typeahead-autocomplete-search
    Its a module so you just upload the files, turn the old module off and turn the new one one. Real easy now. No code changes what ever. Anyone altering the core code on the CE version wants to learn to do things properly.
  8. Haha
    ArtcoInc got a reaction from burt in We've updated our Terms & Conditions / Privacy Statement   
    Actually, all we've done is change the date on it. It's still the same mumbo-jumbo that no-one ever reads.
    After receiving sooooooo many emails from other sites stating that they have changed theirs, we just felt left out ...
    (carry on)
  9. Like
    ArtcoInc got a reaction from valquiria23 in Colors on Boxe Titles Change   
    @AAWISDOM
    Since it looks like you are starting out with a clean install of osC 2.3.4.1, listen to what @Jack_mcs said. While v2.3.4.1 is the last 'official' release, it was just a hot-fix to v2.3.4, which is several years old. In addition to being old, there are concerns that v2.3.4.1 will fail when your host upgrades their version of PHP.
    The 'community edition' of osC, while not 'official', is the latest version. It is responsive (meaning it will adjust the display to fit the screen size (important for all of the people using mobile devices these days)), much more modular (meaning you can turn features on or off, or even add new features, all without touching the core code), and is PHP 7.x ready. And, as @Jack_mcs said, it handles CSS much better. There is a user.css file which loads last, so you can enter any css definitions you want, all without having to touch the 'stock' css files (which you should never touch). You can find a link to it in my signature below.
    Now, before you bitch about why the community edition is not official, nor is there any reference to it on the osC website, please note that the owner of the osC name and code has stepped away from the project (we don't know for how long), and he is the only one that can make that change. This is why the community has stepped up to produce an updated version of osC. After all, this is an open source project.
    Nice way to ask for help, by the way ...
    Malcolm
  10. Like
    ArtcoInc got a reaction from valquiria23 in Colors on Boxe Titles Change   
    @AAWISDOM
    Since it looks like you are starting out with a clean install of osC 2.3.4.1, listen to what @Jack_mcs said. While v2.3.4.1 is the last 'official' release, it was just a hot-fix to v2.3.4, which is several years old. In addition to being old, there are concerns that v2.3.4.1 will fail when your host upgrades their version of PHP.
    The 'community edition' of osC, while not 'official', is the latest version. It is responsive (meaning it will adjust the display to fit the screen size (important for all of the people using mobile devices these days)), much more modular (meaning you can turn features on or off, or even add new features, all without touching the core code), and is PHP 7.x ready. And, as @Jack_mcs said, it handles CSS much better. There is a user.css file which loads last, so you can enter any css definitions you want, all without having to touch the 'stock' css files (which you should never touch). You can find a link to it in my signature below.
    Now, before you bitch about why the community edition is not official, nor is there any reference to it on the osC website, please note that the owner of the osC name and code has stepped away from the project (we don't know for how long), and he is the only one that can make that change. This is why the community has stepped up to produce an updated version of osC. After all, this is an open source project.
    Nice way to ask for help, by the way ...
    Malcolm
  11. Like
    ArtcoInc reacted to burt in Frozen   
    Dead?
    It's at a place I am mostly happy with; php7, a bit modular, responsive etc.
    Good Luck to all Shopowners.
  12. Like
    ArtcoInc reacted to raiwa in Purchase without account for 2.3.4 and BS2334   
    Just uploaded:
    Purchase without account BS 3.0
    Compatibility: Responsive 2.3.4.1 BS CE Frozen PHP 7.0-7.2
    -------------------------------------------------------------------------------------------------------------
    Older 2.3.4.(1.) versions please use PWA for BS 2.5r2
    -------------------------------------------------------------------------------------------------------------
    Changes Version. 3.0:
    updated all core references and included modified core files to Responsive 2.3.4.1 BS CE Frozen removed hook register from checkout_process.php moved all delete guest account scripts into ht module updated checkout_success.php content module modifications to use only new and optional "keep account" pwa module modify all other checkout_process.php content modules by javascript included in ht module. offer subscribe to product notifications in checkout success for guests who opt on permanent account less core file changes  
  13. Like
    ArtcoInc reacted to raiwa in Undefined variable: language   
    $language is defined in application_top.php, so you have to include it before using $language.
    Global $language is not required if you use it in the main page file, remove it everywhere.
    and yes, @JcMagpie is right, you missed one slash, it must be:
    require('includes/languages/' . $language . '/conditions.php');  
  14. Like
    ArtcoInc reacted to clustersolutions in After reading Terms and Conditions, return to prior page   
    Use modal popup instead.
  15. Like
    ArtcoInc got a reaction from valquiria23 in AUTO EMAIL REPLY   
    @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
  16. Like
    ArtcoInc got a reaction from valquiria23 in AUTO EMAIL REPLY   
    @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
  17. Like
    ArtcoInc reacted to burt in Frozen   
    https://github.com/gburton/Responsive-osCommerce/releases/tag/2341-Frozen
    There will be no further Code Changes.
    Issues will be immediately closed.
    What is broken, stays broken. PRs will be immediately closed.
    What is now there, is there. Thank You to all Shopowners and Developers who have supported the Project in the last 4 and a bit years. 
    Personal Thanks go out to all those Shopowners who were able to support my 28d bits and pieces for 3 of those 4 years - it is you guys who have made it possible for the hundreds of other Shopowners to continue using osCommerce.  A big Thank You and  from me, I will not leave you guys high and dry - you have my support always, we are a Band Of Brothers.
    Onwards!
  18. Like
    ArtcoInc reacted to burt in Test New List/Grid   
    The main reason I would like to use this new code is to dump this Cookie that the grid_list uses.  If we can dump that Cookie, shopowners may no longer have to ask people to accept Cookies as all the Cookies in the Edge download are then absolutely required for it to perform its primary function => allow shoppers to buy your stuff.
    Please feel free to have your say on that.
  19. Like
    ArtcoInc got a reaction from Demitry in 2.2 to Edge - Design Help Please   
    Thanks for the clarification, @Demitry
     
  20. Like
    ArtcoInc got a reaction from JSONcart in 2.2 to Edge - Design Help Please   
    @graveyardrecords
    Sometimes, it comes down to whether to answer the question asked, or point the person in a 'better' direction.
    As you are finding out, Edge is very modular. You can turn modules on or off in Admin, all without any core changes. New modules can be installed easily, also without any core changes. It's a new way of doing things. If you try to maintain your new shop the way you did with the old shop, you'll loose all of the benefits of the new system.
    If you need a module that doesn't already exist, it's not difficult to copy and modify an existing one, and make one that does what you need.
    I strongly encourage you to NOT try and make your new shop look exactly like your old one! All the effort you put into making it look the same on a large screen will be lost on smart phone. Make sure you view your site in ALL of the display sizes.
    Malcolm
  21. Like
    ArtcoInc got a reaction from JSONcart in 2.2 to Edge - Design Help Please   
    @graveyardrecords
    Sometimes, it comes down to whether to answer the question asked, or point the person in a 'better' direction.
    As you are finding out, Edge is very modular. You can turn modules on or off in Admin, all without any core changes. New modules can be installed easily, also without any core changes. It's a new way of doing things. If you try to maintain your new shop the way you did with the old shop, you'll loose all of the benefits of the new system.
    If you need a module that doesn't already exist, it's not difficult to copy and modify an existing one, and make one that does what you need.
    I strongly encourage you to NOT try and make your new shop look exactly like your old one! All the effort you put into making it look the same on a large screen will be lost on smart phone. Make sure you view your site in ALL of the display sizes.
    Malcolm
  22. Like
    ArtcoInc got a reaction from TITO4 in default shipping method change.   
    @burt
    If your suggestion works (and I see no reason it shouldn't), maybe this should be added to the core?
    Malcolm
  23. Like
    ArtcoInc got a reaction from Stephan Gebbers in Upgrade, or change cart?   
    (a subject came up recently in a private conversation)
    As a store owner, changing the shopping cart software for your existing store is a major change. Then again, if your cart's software core foundation changes drastically (such as osC v2.3.4 -> v2.4 looks like it is doing), you've got the same issues.
    As a shop owner who currently maintains your own store, if osCommerce changes its core foundation (again, as v2.4 looks like it is doing), would you choose to learn the new code structure, or would you be tempted to move to another cart?
    Personally, I am comfortable with maintaining my 2.3.4 stores, but I see 2.4 as such a drastic change, I'd consider looking elsewhere.
  24. Like
    ArtcoInc reacted to greasemonkey in Shopowners Club - Core Suggestions   
    Just trying to present a shop owners opinion here............
    And as a shop owner, there are options when it comes to ecom platforms:
    Shopify - fantastic, built ready to go.... any addon you can image.... BUT you will be nickle and dimed TO DEATH - mostly by shopify and their per-transaction fees Magnito - you better no what you are doing BigCommerce - see shopify On, and on and on.....
    Unfortunately, the easy to use, ready to go, out of the box platforms - are essential pyramid schemes. Where you are signing up for life and pay a per-transaction fee - the more successful you are the more successful they are. And I for one, would not have been able to scale our business into multi million dollar ecom business - without an open source platform like OsC.
    That doesn't mean FREE.... I would be willing (and have) to pay for ANY (almost all) addons - as long as I don't have to sign up for life to a per-transaction fee.
    The good news - I beleive the community is going the right direction...
    Just remember, PROGRAMMERS (please take note), for OsC to survive it MUST present a better option than what is currently available and popular. And this means is: easy to use, ready to go, out of the box AND scale-able.
    To my last point - @wHiTeHaT I'm not smart enough to know if making product_listing modular would make any difference in the long run.... but as long as easy to use, ready to go, out of the box AND scale-able are there - I will be happy.
  25. Thanks
    ArtcoInc got a reaction from tobme in Setting up PayPal API on my website   
    @tobme
    Forgive me if I am stating the obvious, but ...
    osCommerce is an online shopping-cart program, allowing you to sell products. You need to install osCommerce on a server. The server needs to meet the requirements of osCommerce, including having a web server (typically Apache), PHP (a programing language interpreter), and a database (typically mySQL). If you don't meet these requirements, you can not install or run osCommerce.
    Please note that you can install osCommerce on an in-house test server (I have one here for my testing and development), or on a host's server. If you are taking your store live (and actually plan to sell items), please use a host. DO NOT try to host a live site yourself ... the hackers will eat you alive!
    Your initial question asked about the Paypal module. This is a module that you ADD TO your osCommerce shop. It is NOT a standalone application. Nor can the Paypal module be installed on a website that does NOT have osCommerce installed.
    Now, before you go any further, please realize that the 'official' v2.3.4(.1) version of osCommerce is obsolete. Do NOT waste your time with it. Please download the community supported Edge version (link in my signature below).
    If you need help getting osCommerce up and running, please start another thread asking how to do that. Once you have osCommerce (the Edge version) running, and if you are still having problems getting Paypal to work, there is a section of this forum specifically for payment module problems (including a section just for Paypal problems).
    HTH
    Malcolm
×