Jump to content

cDGo IT Consultancy

  • Content count

  • Joined

  • Last visited

Reputation Activity

  1. Thanks
    cDGo IT Consultancy reacted to MrPhil in Forum Changes   
    Harald, I have said it before, and I'll say it again:
    You cannot leave a product unattended for more than 12 months, or the ecommerce market declares it dead. You must have a major refresh or release at least annually, to stay in the public mind as a "current" product. The official product (currently is the one that "one button" installers will pick up. That's the one that all newcomers will be using. It must be kept current. It doesn't matter if @burt's dazzling BS4 responsive PHP 7.3-ready plutonium-powered incredible edible edition is "available" on the main page -- that's not the one installers will pick. It would be best to take Frozen + patches and rebrand it as osC 2.5 (since 2.4 is already taken), and make it the official release. At least that will buy some time for a newer edition to be developed. If your work isn't ready by early 2020, Gary's BS4 edition could be 2.5.1, buying another year's grace. It's a very bad habit to not keep the current release updated, on the expectation that your work will be ready (Gold) Any Day Now -- history has shown that never happens, and these things slip for years. It doesn't matter how wonderful whatever you're working on will be -- it may well be the greatest thing since sliced bread, but if it's been more than a year since the last update, it will be starting from scratch in the public marketplace. In fact, it's worse than that -- it will have to first dig itself out of the "osCommerce is dead, dead, dead" hole before it's even in the race. Please declare everything earlier than (official) to be immediate End of Life, and bar any further support discussion, except for how to migrate to the current version. and Gary's CE works should go EOL in a year or so. Let's clear the decks of all the ancient stuff, and get everyone to the new 2.5 (a.k.a. Frozen) and eventually to whatever you release. Yes, tools are needed to make migrations less painful. If this feels like a bucket of ice water poured over your head, it's meant to be. Time to wake up!
  2. Like
    cDGo IT Consultancy got a reaction from Fredi in Frozen   
    My biggest problem with the versions above 2.2 is the incompatibility with all of the plugins from the past.
    Ofcourse one could rewrite them so it will fit 2.3.4 methods.
    But not everything can be get into modular design.
    Well actually it could but than it would be nice to agree to some standard way of doing this.
    The idea of a Wordpress method of working is very appealing to me.
    Have one core installation, and plugins just interact with it.
    Also finding the latest info on development is quite difficult for non daily visitors.
    It would be nice to have a read only topic maintained by developers, which lists the latest news on the actively developed version, and where to download it.
    Stage 1,
    1) I'm still on whilst converting from 2.2, the most frustrating thing with that, is that it gets structure and core files changes, which than needs to be run against all the migrated shops again.
    And although the changes are easy to make, it's just timeconsuming to do these for multiple shops again and again.

    2) I've made an desktop solution for my own customers.
    With that I can easily convert old data to the new database structure.
    But it also has some limitations.

    If there are custom tables introduced, this data can be copied in total.
    If custom fields are introduced the can be created in the new structure.
    So that doesn't need to be a show stopper.
    But at this point it can't copy data from one field to a other different existing field (cross fields)
    In general it still takes me between 30 - 60 mins to do migrations/moving data.
    The more custom work is involved, the more time it takes.

    And although it's just some clicks to operate the tool, it's no something that I would let my customers do themselves.
    3) sounds nice

    Stage 2,
    1) I did that now with 2.3.4 Edge
    2) Yes please
    3) Unfortunatly I think thats is impossible as it is against the license model and how would one make this work?
    4) I would say the biggest available, as it would probbaly be there for a while.
    5) That sounds nice (but where was the time that others took features from osC?)
    6) Great
    7) Great
    8) See above.

    I also made a simple template system for which basically lets the user uploads a template set to the server, and have them choose it from the backoffice side.
    The issue with it is that you'll need to change the location where the template files are now stored to the new location for each frontend file.
    And than the core files are changed, making updating more time consuming because you need to verify all the root files always, as they have this difference.

  3. Like
    cDGo IT Consultancy got a reaction from Demitry in Mailchimp newsletter Everywhere add on   
    This is just a simplified version, but install the plugin as supposed and than add this:

      if (isset($_POST['action']) && ($_POST['action'] == 'process') && isset($_POST['formid']) && ($_POST['formid'] == $sessiontoken)) {
        $process = true;

     if (MODULE_FOOTER_MAILCHIMP_STATUS == 'True' && isset($_POST['newsletter']) && $_POST['newsletter'] == 1) {
      $key = [your api key];
      $list_id = [your email list id];
      $array = array('email_address' => $_POST['email_address'],
            'merge_fields'  => array('FNAME' => $_POST['firstname'],
                'LNAME' => $_POST['lastname']),
            'status'        => 'subscribed');
      $MailChimp = new MailChimp($key);
      $result = $MailChimp->post('/lists/' . $list_id . '/members', $array);

    [your api key]            with your api key like '123456789'
    [your email list id]   with your email list id like '98765'
  4. Like
    cDGo IT Consultancy got a reaction from kymation in Tabbed Product Admin   
    This is a nice addon, thank you for sharing.
    The SEO section isn't divided into the languages, all fields for both Dutch and English (in my situation) are on the same page.
        for ($i=0, $n=sizeof($languages); $i<$n; $i++) {
          echo '<li><a href="' . substr(tep_href_link('categories.php', tep_get_all_get_params()), strlen($base_url)) . '#section_general_content_' . $languages[$i]['directory'] . '">' . $languages[$i]['name'] . '</a></li>';

    and replace the word section_general_content for section_seo_content.
    So it will read like this:
    echo '<li><a href="' . substr(tep_href_link('categories.php', tep_get_all_get_params()), strlen($base_url)) . '#section_seo_content_' . $languages[$i]['directory'] . '">' . $languages[$i]['name'] . '</a></li>';