Jump to content

ArtcoInc

Members
  • Content count

    1,838
  • Joined

  • Last visited

  • Days Won

    31

Reputation Activity

  1. Like
    ArtcoInc got a reaction from Dnj1964 in Left Column - pushed to bottom on poduct page   
    @Dnj1964
    If you use a program like Notepad++, it makes it a lot easier to find un-matched divs, etc.
    M
  2. Like
    ArtcoInc got a reaction from Dnj1964 in Article Manager v1.0   
    @Dnj1964
    Dreamweaver has been known to create problems with PHP bases, data-drive websites. As I mentioned to you in another thread, try using a different code editor, such as Notepad++.
    M
  3. Like
    ArtcoInc got a reaction from Dnj1964 in Left Column - pushed to bottom on poduct page   
    @Dnj1964
    If you use a program like Notepad++, it makes it a lot easier to find un-matched divs, etc.
    M
  4. Thanks
    ArtcoInc got a reaction from alex121121 in I have no "main_page.tpl.php" file   
    @alex121121
    I downloaded the add-on in question to take a look at it. While it *may* have worked way back when, I don't think it will do what you want it to do now, especially with the current Community Edition of osC.
    Sorry 😕
    M
  5. Like
    ArtcoInc reacted to BrockleyJohn in Frozen bug list   
    I suggest
    if ( ! is_array($params) ){ $params = array(); } if ( ! isset($params['type']) ) { $params['type'] = 'submit'; } instead. That prevents you losing other parameters if type is not set.
  6. Like
    ArtcoInc reacted to 241 in Frozen bug list   
    includes/functions/html_output.php
    if ( !isset($params['type']) ) { $params['type'] = 'submit'; } change to
    if ( !isset($params['type']) ) { $params = array('type' => ''); $params['type'] = 'submit'; } the addition is
    $params = array('type' => '');  
  7. Like
    ArtcoInc reacted to artfulweb in Frozen bug list   
    The above fix by 231 was in answer to my error log in includes/functions/html_output.php lines 303, 306, 307, 310, 320, 329, 348-  which begins as:
    __________________________________
    ////
    // Output a jQuery UI Button
      function tep_draw_button($title = null, $icon = null, $link = null, $priority = null, $params = null, $style = null) {
        static $button_counter = 1;
        $types = array('submit', 'button', 'reset');
        if ( !isset($params['type']) ) {
          $params['type'] = 'submit';
        }
    ___________________________________
    So making the change just in the beginning it becomes
    ___________________________________
    ////
    // Output a jQuery UI Button
      function tep_draw_button($title = null, $icon = null, $link = null, $priority = null, $params = null, $style = null) {
        static $button_counter = 1;
        $types = array('submit', 'button', 'reset');
        //if ( !isset($params['type']) ) {
        //  $params['type'] = 'submit';
        //}
        
        if ( !isset($params['type']) ) {
            $params = array('type' => '');
            $params['type'] = 'submit';
        }
    ____________________________________
    and the errors go away. Hope this helps.
    -Barbie
     
     
     
     
  8. Like
    ArtcoInc reacted to 241 in Illegal string offset 'type'   
    done
    Frozen bug list post
  9. Like
    ArtcoInc reacted to burt in Confusion over osC Versions.   
    It maybe worth everyone who has a link to link to the post that is in my sig.
    I can then keep that post updated as more releases come along.
  10. Like
    ArtcoInc reacted to burt in Confusion over osC Versions.   
    CE is the umbrella term for my "Responsive" fork on Github.  
    What I am working on is called Edge.
    Gold (release) is a fixed point along that Edge timeline.
    Frozen (release) is a fixed point along that Edge timline.
    I suspect there may be more fixed points in the future, but that depends on the Community at large helping...instead of throwing stones.
      Edge is (and always has been) a work in progress.
    It's easier to say the work is "bad" than to actually help shopowners get a good responsive and useable version of osCommerce, hence some of the posts we've all seen in the last 12 months.   And then I see those same moaning minnies using the CE for their clients  or for their own shop  
      Copyright
    Any file that IS in CE and IS NOT in official is a new file.  New files are copyright their respective author.
    If anyone believes they wrote one of these new files and the copyright is incorrect on that file, raise an issue on Github and it will be sorted.
    Respecting copyright is very important and if I have failed in that, I want to know.
      Naming/Tagging (and other areas that could be changed)
    Agreed that things could be better, but you know what...get involved and it might get changed.  The last person who did get involved...wanted the version checker changed on release of Frozen, so it was changed to accommodate what he wanted.
    Moaning and groaning (about anything I do or don't do) whilst you have done nothing to help...is not an ideal situation. When all that is said and done, I thank you all for your feedback, it's been taken on board.  Now, a couple of people who have posted in this thread have actually done positive things for the community since Frozen was released - I'm sure you have received thank you's from the thousands of users of the CE releases.  If not, that's not ideal - accept my thank you now - thank you.
    As for the ones who are "loud" in their opinions yet have done nothing to help, I challenge you to actually step up to the plate and start swinging.  If you don't swing you won't get a home run...
    As you guys have been so candid in your opinions, I hope that I'm allowed to give my opinion in the same candid manner.  So I ask each of you who have posted here and anyone else reading this a rhetorical (ie does not need answering here, just have a think on it) question..."have you done your part in making osCommerce a viable option for todays shopowner needs" ?   
  11. Like
    ArtcoInc got a reaction from greasemonkey in Confusion over osC Versions.   
    (as a bit of background)
    As has been said before, the Community Edition does not have an accurate version numbering system.
    When Burt started this project back in 2014, osC was at version 2.3.3.4. So, the Community Edition, all through its early development, was also v2.3.3.4. Every release of the Community Edition during these early times was called v2.3.3.4.
    When osC upgraded to v2.3.4, Burt brought the Community Edition code base up to the v2.3.4 code base, and the Community Edition became (and stayed at) v2.3.4 while further development was happening. In January 2015, Burt released the 'Gold' fixed release. Development still continued, with every release still being called v2.3.4.
    When osC had the v2.3.4.1 Hot Patch applied, Burt also applied the Hot Patch, and the Community Edition was bumped up to v2.3.4.1. Once again, development continued, with every new release still being called v2.3.4.1.
    Burt released the 'Frozen' fixed release in August 2018. No additional development is being done on 'Frozen'. Some bugs have been identified in 'Frozen', and there is a thread here on the forum identifying them (and some fixes too). At lease one member here is maintaining a patch file of these fixes needed for 'Frozen'.
    Development still continues (usually called 'Edge', although that is not a fixed release), and the version number is *still* v2.3.4.1. Some significant changes have been made since 'Frozen' (such as the 'upgrade' from BootStrap v3 to v4), causing some compatibility issues with prior versions, and many (most?) add-ons out there.
    So, there is no one 'Edge' version. Releases prior to 'Frozen' could technically be called 'Edge', and every release since 'Frozen' is also technically 'Edge'. A release of 'Edge' from a month ago may not (and probably is not) the same as 'Edge' today.
    Also, there is no 'Frozen' BS4. All changes to upgrade to BootStrap v4 came *after* the release of 'Frozen'.
    I won't go into why this has happened, nor into what could/should be done to address this. And I encourage others to not feed into a woulda/coulda/shoulda rant that will add nothing to the discussion.
    Malcolm
  12. Like
    ArtcoInc got a reaction from greasemonkey in Confusion over osC Versions.   
    (as a bit of background)
    As has been said before, the Community Edition does not have an accurate version numbering system.
    When Burt started this project back in 2014, osC was at version 2.3.3.4. So, the Community Edition, all through its early development, was also v2.3.3.4. Every release of the Community Edition during these early times was called v2.3.3.4.
    When osC upgraded to v2.3.4, Burt brought the Community Edition code base up to the v2.3.4 code base, and the Community Edition became (and stayed at) v2.3.4 while further development was happening. In January 2015, Burt released the 'Gold' fixed release. Development still continued, with every release still being called v2.3.4.
    When osC had the v2.3.4.1 Hot Patch applied, Burt also applied the Hot Patch, and the Community Edition was bumped up to v2.3.4.1. Once again, development continued, with every new release still being called v2.3.4.1.
    Burt released the 'Frozen' fixed release in August 2018. No additional development is being done on 'Frozen'. Some bugs have been identified in 'Frozen', and there is a thread here on the forum identifying them (and some fixes too). At lease one member here is maintaining a patch file of these fixes needed for 'Frozen'.
    Development still continues (usually called 'Edge', although that is not a fixed release), and the version number is *still* v2.3.4.1. Some significant changes have been made since 'Frozen' (such as the 'upgrade' from BootStrap v3 to v4), causing some compatibility issues with prior versions, and many (most?) add-ons out there.
    So, there is no one 'Edge' version. Releases prior to 'Frozen' could technically be called 'Edge', and every release since 'Frozen' is also technically 'Edge'. A release of 'Edge' from a month ago may not (and probably is not) the same as 'Edge' today.
    Also, there is no 'Frozen' BS4. All changes to upgrade to BootStrap v4 came *after* the release of 'Frozen'.
    I won't go into why this has happened, nor into what could/should be done to address this. And I encourage others to not feed into a woulda/coulda/shoulda rant that will add nothing to the discussion.
    Malcolm
  13. Like
    ArtcoInc reacted to greasemonkey in Hack attempt - is there a way to prevent this?   
    @ArtcoInc I think the link to your review is very relevant to the thread - and the threat of this hack attempt (I can’t recall the level of detail in your review but maybe you’d update to include this potential risk). 
  14. Like
    ArtcoInc got a reaction from greasemonkey in Hack attempt - is there a way to prevent this?   
    @greasemonkey
    (while off topic regarding hack attempts ...)
    I also reviewed that search add-on here ...
    M
  15. Like
    ArtcoInc got a reaction from puggybelle in Hack attempt - is there a way to prevent this?   
    @puggybelle
    I had an attack on one of my sites yesterday ...
    I also have a Keyword Search Report on this site. I hadn't checked it in a while, but after reading your post, I went to check it out. Guess what? Same thing here ...

    That's just part of one page! There are over 20 pages of this!
    Thank you for reporting this ... I wouldn't have thought to look at this.
    Malcolm
  16. Like
    ArtcoInc reacted to Harald Ponce de Leon in Support thread for featured products with Ribbon v2.3.4.1 CE   
    The class constructor has a syntax error which is why the Apps Marketplace did not accept the upload. Here is the class constructor of includes/modules/header_tags/ht_jcm_owl_carousel2_js.php:
    function __construct() { $this->title = MODULE_HEADER_TAGS_JCM_OWL_CAROUSEL2_JS_TITLE; $this->description = MODULE_HEADER_TAGS_JCM_OWL_CAROUSEL2_JS_DESCRIPTION; if ( defined('MODULE_HEADER_TAGS_JCM_OWL_CAROUSEL2_JS_STATUS') ) { $this->sort_order = MODULE_HEADER_TAGS_JCM_OWL_CAROUSEL2_JS_SORT_ORDER; $this->enabled = (MODULE_HEADER_TAGS_JCM_OWL_CAROUSEL2_JS_STATUS == 'True'); } } global $oscTemplate, $category_depth; if (basename($_SERVER['SCRIPT_NAME']) == 'index.php' && (isset($category_depth) && $category_depth == 'top') && ! isset($_GET['manufacturers_id'])) { $oscTemplate->addBlock( '<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/assets/owl.carousel.css">' . "\n", $this->group); $oscTemplate->addBlock( '<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/assets/owl.theme.default.css">' . "\n", $this->group); } } Either the constructor is closed early before the global statement, or a function name is missing.
    Either way, it's good now that the Apps Marketplace can detect such issues 👍
  17. Like
    ArtcoInc reacted to burt in Bootstrap Themes from WP or Opencart? Have someone try?   
    It's surprising how much can be achieved by amending user.css.   The idea of the tpl files is that shopowner will micro-adjust these - so (in my opinion) these files should be seen as is the user.css - core files but changeable.
    Back in 2015 when the bootstrap build was new, I tried to get other developers on board (seo, theming etc) - but there was little interest, so I did what I thought would make life easier.  It for sure aint perfect but it's not too bad.
  18. Sad
    ArtcoInc got a reaction from xina1 in Bootstrap Themes from WP or Opencart? Have someone try?   
    @Roman_SE
    http://www.oscommerce-templates.co.uk/
    M
  19. Like
    ArtcoInc reacted to Harald Ponce de Leon in Forum Changes   
    Hi All..
    The forum was down for maintenance today for backend work and to streamline the forum structure. Many of the support forums have been merged (eg, OSCOM v2.x support, installation, upgrades, tips and tricks, ..), and some have been vaulted (eg, OSCOM v3.x, development, ..). The encyclopedia sized forum rules have also been streamlined and now point to the policies on our main website.
    For a test run, the Clubs section is being shown more prominently on the front page of the forum, showing the last 3 active clubs. This may change again in the future where all discussions are held in Clubs to further streamline the forum structure, and to experiment with entirely new forum front page experiences.
    Announcements will soon be made regarding the following:
    v2.x Community Editions Apps Marketplace New Me Website OSCOM v3.x New channels for v3.x discussions will be added to the forum when the announcement is ready to be made.
    On a personal note, I apologize for my lack of presence in the forum - I have been focused entirely on coding. Many thanks to the moderator team keeping the community civilized. My resources now allow me to do both, so watch out 👀😃 and catch me in the Public Chat area again from this week on.
  20. Like
    ArtcoInc reacted to burt in Email queuing system   
    It's just a template so individual shopowners can easily set it up as they like and tweak it etc. 
    HTML Emails are actually quite difficult as email programs render the output markedly differently.
    Well, it's certainly close enough to get the updated system out to the two testers to try.  Tomorrow chaps.
  21. Like
    ArtcoInc reacted to burt in No Hooks in Bootstrap?   
    If you don't like what we're doing in the Community Edition (in your words, "shoving stuff down your throat")...then it is simple; stay on the official osCommerce version. 
    Official version is still useable, just nowhere near as useable as the Community Edition.  
  22. Like
    ArtcoInc got a reaction from burt in My idea for Blog in osCommerce   
    @vampirehunter
    Please be aware that this thread is 2-1/2 years old.
    That said, @burt did a Blog module in his 29 days bundle.
    HTH
    Malcolm
  23. Like
    ArtcoInc got a reaction from Dan Cole in Email queuing system   
    Thank you. And, I resemble that!
  24. Thanks
    ArtcoInc got a reaction from Onliny in General Questions about issues using Frozen   
    @Onliny
    The Community Edition of osCommerce has been in development for 4-5 years. It is an ever-changing, ever-evolving project. Two 'fixed' releases have been made: 'Gold' and 'Frozen'. Gold is very old, and should be ignored at this time. Frozen is the current version for use in a live shop. Yes, some bugs have been reported, and there is an entire thread here on that subject.
    Development still continues. The 'Current as of today' version is called 'Edge'. Do note that 'Edge' from last month will be different than 'Edge' from this month (like I said, it is constantly changing).
    When 'Frozen' was released, it was on BootStrap v3. Since then, in the continuing development of 'Edge', it has been upgraded to Bootstrap v4.
    So, as @MrPhil stated, if the version you are using uses Bootstrap v4, you are using either a newer version of 'Edge', or someone else's fork of this project.
    Yes, understanding the version status of this project is confusing.
    HTH
    M
  25. Like
    ArtcoInc reacted to burt in Email queuing system   
    I've now created a module for order_success to replace the standard order success email that osC sends.  If anyone wants to test it:
    https://template.me.uk/outgoing/
    and progress all the way through the checkout.  You'll get an email sent by this new system - so PLEASE use a real email address...
    This system is looking like another game-changer.
×