Jump to content



Member Since 11 Jan 2013
Offline Last Active May 14 2018 06:14 AM

Topics I've Started

Cscart Themes Using Vue.js, Sass And Other Goodies

10 May 2018 - 03:16 AM



I am developing a new theme for our storefront using vue.js and SASS for frontend components and brunch as the build system.. Thought I would keep people posted in case anyone else is doing something similar. 


I have my configuration setup pretty nicely now.   And I am confident that it will at least result in an operational website with scoped modules, simpler TPL files and a much more clearly defined components with single responsibility. 


I have not had to modify any core controllers and my original TPL files become a simple portal into vue.js land.  E.g. my views/checkout/checkout.tpl file now looks like this


<checkout :cart="{$cart|json_encode}"></checkout>
And my checkout component looks like this (bootstrap 4.1 is part of my setup):
  <div class="row">
    <div class="col-12 offset-2">
      <div class="row">
        <div class="col-12">
          <step-one class="mb-4"></step-one>
          <step-two class="mb-4"></step-two>
        <div class="col-4">

Of course I have other vue.js components "step-one" that all do their job... so far so good. 


Other considerations I am making are:


- What to do with core CS-CART modules.   E.g. "core.js" ... Since the original CS-CART javascript is not modular, it makes it a little trickier to figure out how to get the core CS-CART javascript into my theme.   For now, I haven't included it at all as part of me is thinking that I might just roll my own functions to hook into CS-CART...but I have to trade this off against any headaches I might encounter when it comes time to upgrade CS-CART.    I am currently steering in the direction of rolling my own (using axios library to make calls) as we don't have a lot of backend AJAX calls from our front end and I think I will end up with a smaller library this way.


- I am using brunch as my build system and of course webpack would work nicely too.  This is just personal prefernce as I always struggled to get a clean setup with webpack and always found it hard to come back to my config files later on and figure out why I was doing what..   Our requirements are quite simple, so brunch hasn't fallen short yet.


Benefits I have noticed:


- Loading time of theme.  Previously we have used a store bought theme and these themes come with a lot of baggage that you don't always use.  By developing our own cut down theme, site load times are much faster


- Cleaner template files and much more self explanatory components.  I am not sure about you, but I always found Smarty template files (no matter what syntax highlighter you have enabled) hard to read.  This is no longer the case


What do you think?  Anyone else been down this path and hit any roadblocks after the honeymoon period?  i would be interested to hear your thoughts. 


Either way, I hope that the CS-CART team will start to integrate more contemporary best practice javascript loading future releases of CS-CART.  The core CSCART javascript is doing the job, but surely at some point it is going to be difficult to maintain... 


Cheers... Apologies for any typos / grammar errors in this post.  I better get back to work!

Theme Parent Relationship

10 May 2018 - 02:57 AM



I am developing a new CS-CART theme for our business and when defining the theme, I am curious about the relationship in the manifest file when the parent theme is specified. 


Most of the themes I have seen use "responsive" as the parent theme.   However, I am pretty sure this relationship isn't the same as something as a child theme in wordpress where you can override templates of the parent theme inside the child theme. 


Assuming I am correct (that the relationship isn't the same) - can anyone tell me when this relationship gets called upon and why it is important?




Currencies And Editing Orders

27 April 2018 - 02:45 AM



We have a master currency in Australian dollars and a secondary storefront running New Zealand dollars.


All is working ok until we edit an order on our New Zealand storefront.  When we change products, all prices are entered into the invoice in Australian dollars and customer receives email with Australian dollar values. 


Is there any way we can get around this?  




Override Quantity In Different Storefront For Shared Product

17 November 2017 - 04:04 AM

Hi, we have a storefront for Australia and New Zealand. 


All products on our site are owned by our Australian storefront and shared to the NZ storefront. 


We recently sold out of a product in Australia and updated the inventory to zero, but this also updates our NZ inventory to 0 and you can't override it. 


This is a problem also for our custom logic that excludes any products with an inventory of 0 from our Google Shopping data feeds. 


Anyone know a way around this without having a separate copy of the product in the NZ storefront?



When Are We Expecting To New Product Feature Variations To Be Out Of Beta?

13 November 2017 - 12:36 AM



I am glad to hear that product feature variations have been added to CS-CART, however I don't like that they are still in BETA but part of the current release of CS-CART. 


I am worried about upgrading to the latest version of CS-CART and having it effect our product catalog.  Should I be?


Any idea when the new features will be considered "complete"?