Jump to content

 

jjtrottier

Member Since 25 Jan 2011
Offline Last Active Jun 10 2017 07:39 PM
-----

Posts I've Made

In Topic: Twig Templater Support To Be Implemented?

27 June 2016 - 12:55 AM

It's a nice idea but I think CS-Cart should focus on features that add more value for store owners to help drive sales/conversions. Platforms such as Shopify abstract technical issues like this away from the store owner, so that the store owner can focus on growing their business, and not worry about the technology stack underneath it.

 

I still believe CS-Cart is a good solution for customizable ecommerce, but CS-Cart needs to build stability and growth opportunities for merchants to excel on this platform. If you focus on non-essential things underneath the hood like the Twig template engine, or more "object-oriented" code design, you are shaking up the core foundation of the app and risking its stability (and your customer's trust).

 

As a reseller/partner, I can't go back to my customers and tell them we need to bill 10 hours to rebuild the site in Twig if/when you decide to phase out Smarty. That would make me look at other platforms if it were the case.

 

Sure, maybe Twig templating will be cleaner, and 'prettier' to work with, but it will create work for existing store owners to convert their website instead of growing their business. I understand you could offer to run both template engines simultaneously but I can't see how that will be a smooth implementation without introducing several new bugs.

 

My point, overall, is that I think you should review your roadmap, look at the wishlist of features not yet implemented in CS-Cart, and focus on the ones that will help people sell more. If store owners can get more sales/value from your product and its features than the competition, then it's win-win for everyone.


In Topic: Paypal Standard Not Working Correctly

11 March 2016 - 03:52 AM

We're also still getting this with two of our customers' stores


In Topic: 1-Year Licenses Discontinued

05 August 2015 - 01:57 PM

We are not raising any prices, where did you get this?

Please do not read between the lines, read the text.
CS-Cart and Merhium are different products. having full access under your store files and data is not the same as Saas subscription when you do not have ability to change a simple file.


I think I am reading between the lines quite clearly. By eliminating 1 year subscriptions, you are effectively raising the initial price tag or the "barrier to entry" to use CS-Cart as self-hosted.

I see this as a necessary move for CS-Cart because I'm sure that supporting self-hosted clients is probably a time consuming and expensive task. So in setting a higher "initial price" you are weeding out those customers who many not be 100% serious or capable of properly running self-hosted software.

For me, however, I have been reselling your product to customers using the annual model. The lower upfront cost helps me close more deals and keep my prices down. With this increase, it really pushes me towards finding a pure SaaS partner or other hosted cart. The unpredictability of your licensing model leaves me worried about whether I should continue my efforts with CS-Cart.

In Topic: 1-Year Licenses Discontinued

04 August 2015 - 10:55 PM

Don't be fooled by this. This is a strategic play to get smaller companies onboard their SaaS (aka Merchium) product. By raising the initial price tag, they're hoping people will just go straight to Merchium. However, people may just go to Shopify or Bigcommerce instead.

It will be interesting to see how this affects CS-Cart.

In Topic: Amazon Cdn S3 Nothing More Than Outsourcing Of Webspace For Images ?

30 June 2015 - 09:04 PM

With Amazon S3, you can setup a CNAME and use your own domain name to serve content. I'm not sure how that works when you're in SSL mode with CS-Cart, but you don't need to use Amazon's URL/domain to reference your static assets. You can brand it your own.

Also, as stated on the AWS website, the benefit of S3 is that "Amazon S3 redundantly stores your objects on multiple devices across multiple facilities in an Amazon S3 Region." So you are getting redundancy, along with an optimized file system built for serving your files at a pretty low price. It is not akin to spinning up a cloud server and dropping your files there. The service offers more than just a dropbox.

The benefit of using Amazon or other object storages in this type of setting is that you can also move your CS-Cart codebase from one server to another, without affecting your catalog images, and other static assets. If you're a big website that load balances 3 or 4 NGINX instances (servers) to run CS-Cart, you no longer need to worry about replicating your catalog images to each server node individually. Amazon will retain all of those files, essentially providing a shared filesystem for the static assets. Visitors can't tell the difference.

This is also good for developers in the sense that they only need to worry about synchronizing their codebase with their GIT repo, and the database. Not having to transport a catalog and all its images definitely makes it easier on developers running CS-Cart in a development sandbox. As others have mentioned, however, with a CDN, you most certainly need to flush your cache when changes are being made, and it can take up to 10-15 minutes for changes to propagate to other edge locations.

It depends on the size, scale and goals of your website, but Amazon S3 is a no-brainer if you run a very busy site with high-volume. For smaller e-commerce operations, a sole VPS might do the job fine, without the need to add these layers of complexity. It depends on how elastic your website needs to be in order to scale with increased visitors.