Jump to content



Member Since 30 Sep 2015
Offline Last Active May 05 2020 02:56 PM

Posts I've Made

In Topic: A Cs-Cart Developer's Dilemma.

22 May 2018 - 08:18 AM

@mazter, thank you! :)


I am pretty optimist about our future as e-commerce web developers, but not necessarily as CS-Cart developers. That's pretty rough with little return.

However, we'll be around for a while longer for sure. As long as our long-term customers still use CS-Cart, which is a great platform nevertheless, we'll never turn our back on them.


In Topic: A Cs-Cart Developer's Dilemma.

06 April 2018 - 01:43 PM

We checked your Help desk account and you are already in this group

Oh, you mean the "Beta Testing" section we have in our HelpDesk > File Area?
I even forgot about that, and that's because I think your system is not functioning properly. In HelpDesk we only received access to 1 "beta testing release" once, which was back in 21 June 2017 (CS-Cart 4.6.1.Beta1dev). I just assume that feature is defunct.
Even now, in Beta Testing we can only see that "CS-Cart 4.6.1.Beta1dev" from mid-2017.
@CS-Cart Team, If you could fix that "Beta Testing" feature such that we can see all future beta releases, now that would be pretty useful.
I could even build an API around that, and automate the testing process, as per our initial plan!

In Topic: A Cs-Cart Developer's Dilemma.

04 April 2018 - 04:56 PM

@CS-Cart team, that would be great. Can you please add us to the Beta Testing group? Our HelpDesk account email is sales at helostore.com. Same email on Slack. Thank you!

In Topic: A Cs-Cart Developer's Dilemma.

29 March 2018 - 08:44 AM

@martfox, thank you for your suggestion. I might try to do that too.



@tbirnseth, thanks for the detailed answer, describing your process. It's true, following certain practices yields better results. And we do follow these practices. Personally, I've been developing with CS-Cart for the last 8-9 years (not with HELOstore, but with another company). 


"I keep an archive of every version/edition of cs-cart since V2.2.2.  On the rare occasion where I really need to validate against a specific version, I can always simply create a test sub-domain built with a specific version/edition for testing/validation."



That's great if you already have an archive to keep. And we do keep an archive from our CS-Cart clients too, but we do not have every version/edition. So we have big testing gaps. 


@CS-Cart team, it's true, HelpDesk did give us access to 7 versions in December 2017 and we are grateful for it.
And if you look further into the HelpDesk communication history, you can see that in our last ticket our request for a few more versions was declined: "I am afraid, we cannot provide you with all the mentioned distributives. Our partner relationship manager will contact you shortly regarding the details." (ticket: "Access to CS-Cart versions for development/testing purposes", March 2018).
No explanation whatsoever. 
Do we need to renew our license? Do we need to get into the reseller program and THEN will get access to new versions? Or what?
These are the versions we have access to, thanks to HelpDesk:
multivendor_v4.4.1.tgz   80446 kb Igor Oryol Jan 27, 2017, 14:16 Download
multivendor_v4.3.1.tgz   68347 kb Igor Oryol Jan 27, 2017, 13:34 Download
multivendor_v4.2.1.tgz   68368 kb Igor Oryol Jan 27, 2017, 13:26 Download
multivendor_v4.1.1.tgz   63954 kb Igor Oryol Jan 27, 2017, 12:21 Download
multivendor_v4.0.1.tgz   62622 kb Igor Oryol Jan 27, 2017, 12:15 Download
cscart_v4.4.1.tgz   80567 kb Alexey Maisuradze Jan 24, 2017, 14:11 Download
cscart_v4.3.1.tgz   68282 kb Alexey Maisuradze Jan 24, 2017, 14:10 Download
cscart_v4.2.1.tgz   68334 kb Alexey Maisuradze Jan 24, 2017, 14:08 Download
cscart_v4.1.1.tgz   63929 kb Alexey Maisuradze Jan 24, 2017, 14:07 Download
cscart_v4.0.1.tgz   62646 kb Alexey Maisuradze Jan 24, 2017, 14:06 Download
cscart_v3.0.6-professional.tgz   45989 kb Evgeniy Tyulenev Dec 27, 2017, 16:13 Download
cscart_v3.0.5-multivendor_100076156.tgz   67906 kb Svetlana Tolpegina Jun 24, 2016, 09:59
It's basically 7 versions in two editions. It helps, but it's not nearly enough.
We have asked access to these versions:
CS-Cart 4.6.2 (2017-08-09)
CS-Cart 4.6.1 (2017-06-27)
CS-Cart 4.5.2-SP2 (2017-04-11)
CS-Cart 4.5.2-SP1 (2017-04-08)
CS-Cart 4.5.2 (2017-04-06)
CS-Cart 4.5.1-SP1 (2017-03-06)
CS-Cart 4.5.1 (2017-02-28)
CS-Cart 4.4.3 (2017-01-26)
CS-Cart 4.4.2 (2016-11-29)
CS-Cart 4.4.1 (2016-11-14) OK
CS-Cart 4.3.9 (2016-07-15)
CS-Cart 4.3.8 (2016-06-08)
CS-Cart 4.3.7 (2016-05-10)
CS-Cart 4.3.6 (2016-03-02)
CS-Cart 4.3.5 (2015-12-15)
CS-Cart 4.3.4 (2015-09-09)
CS-Cart 4.3.3 (2015-06-25)
CS-Cart 4.3.2 (2015-06-09)
CS-Cart 4.3.10 (2016-10-18)
CS-Cart 4.3.1 (2015-04-29) OK
CS-Cart 4.2.4 (2014-11-27)
CS-Cart 4.2.3 (2014-10-16)
CS-Cart 4.2.2 (2014-08-28)
CS-Cart 4.2.1 (2014-07-22) OK
CS-Cart 4.1.5 (2014-05-20)
CS-Cart 4.1.4 (2014-04-23)
CS-Cart 4.1.3 (2014-03-18)
CS-Cart 4.1.2 (2014-01-28)
CS-Cart 4.1.1 (2014-01-15) OK
CS-Cart 4.0.3 (2013-11-06)
CS-Cart 4.0.2 (2013-09-26)
CS-Cart 4.0.1 (2013-06-26)
CS-Cart 3.0.6 (2013-02-14) OK
CS-Cart 3.0.5 (2013-01-16) OK
CS-Cart 3.0.4 (2012-11-07)
Meanwhile, there have been 2 or 3 more releases to which we don't have access.
"I am afraid we cannot upload all the CS-Cart versions to your account."
Care to explain why not? Don't you keep a version of your own releases? :))
And in the ticket we said "access to ALL versions via an API would be great", BUT we would be happy with access to only a few (the 2nd list above). And you have declined.
Or do you mean that you cannot provide us with ALL THE PATCH versions (*.*.X) for some technical reason, and can only provide the minor releases? Great. That's fine, if you follow semantic versioning. But be specific in your communication. Don't worry, we can understand.
Or do we need to hire a person just to hunt down the moment when you release a new version, so that he can order a trial and then download that version, and archive it for us for further use?
I think a more modern solution would be to have a Developer's Program. If you need to take a fee for that from every developer, okay, do it. And this program should give you access to all CS-Cart releases (including early access!), not only through a web page, but also through a tiny API (can be coded in hours!).
That way, you can automate things like: deploy new testing environment with a cli tool (we already have this, eg. dev deploy cscart 4.4.1) of ANY CS-Cart version (we don't have this). 
Wouldn't that be great for the CS-Cart developer?
And why early access? Here's a real case: CS-Cart 4.7.2 is released on day X, on day X+1 customers buys from us an add-on ignoring the mention that "the add-on is compatible only up to CS-Cart 4.7.1, and installs it on his store which he updated to 4.7.2 on that same day; his store crashes.
Sure, mistakes have been made (overlooking incompatibility, installing directly in production, etc), but it's developer's responsibility to make this better & easier for the customer, if the community is to grow. Isn't it?
So what can be done is that you could offer early access to add-on/theme developers to future releases, so that the developer has the chance to test their products on those releases.
And this is important especially for custom add-ons / themes that are ALREADY installed in stores. Usually, when CS-Cart releases a new version, and the customer upgrades to it, ALL THE CUSTOM ADD-ONS that are already installed are virtually UNTESTED with the new CS-Cart version. It's a landmine. 
So early access would translate in better CS-Cart customer experience, and would make developers happy too (no need for extra hours on support, more time to focus on new & cool features and add-ons).
What do you think, is there a middle way?
Should we expect a solution? Or should we move on?