I reported various issues in the bug tracker. What disappoints me: answers are given very late, often only on request. In most cases there is even no answer at all:
It is one of cs-cart's shortcomings. They will pay attention if you make a report against the most recently released version (maybe - new features get higher attention because they are more fun to work on). But if you report an issue that is for any prior release, it can take months. Cs-cart is not effective in evaluating newly reported defects to even get to confirmed/unconfirmed in a reasonable period of time. The only solution is to contact helpdesk. But then the answer may be that "it will be fixed in a future release or looked at in 45 days".
This has been "normal" for the more than 10 years I've been working with cs-cart.
It is one of cs-cart's shortcomings. They will pay attention if you make a report against the most recently released version (maybe - new features get higher attention because they are more fun to work on). But if you report an issue that is for any prior release, it can take months. Cs-cart is not effective in evaluating newly reported defects to even get to confirmed/unconfirmed in a reasonable period of time. The only solution is to contact helpdesk. But then the answer may be that "it will be fixed in a future release or looked at in 45 days".
This has been "normal" for the more than 10 years I've been working with cs-cart.
Good luck.
Then you should also know that as a developer you can submit patches for bugs.
Yeah if I want to spend my time researching, debugging, testing and submitting. Sorry, that's their job, not mine and why we all pay "prolongation license fees". If they start paying me as a developer, I'm happy to do their work for them.
Unfortunately in some cases cs-carts bug trackers team act more like a bunch of people with baseball bats trying to hit back the bugs it's being thrown while telling everyone the behaviour is normal.
I kinda gave up some years ago, although I'm afraid I'll have to dive back in when we upgrade our store again.
You also have to understand that they might not have time because of their 2 week sprints. Bugs take most of the time at least 2 weeks to fix, because they first have to acknowledge it, and then they have to put it on their schedule to be fixed. Its not that hard to understand really.
You also have to understand that they might not have time because of their 2 week sprints. Bugs take most of the time at least 2 weeks to fix, because they first have to acknowledge it, and then they have to put it on their schedule to be fixed. Its not that hard to understand really.
In our company we also work with sprints. And two things are clear for us:
- a maximum of 80% of the available time may be used in the sprint
- investigating a supposed bug or fixing a confirmed bug is also a task in the sprint
If you want quality assurance and customer satisfaction to be given a higher priority, you can do this within a sprint system too. That's my belief.
You also have to understand that they might not have time because of their 2 week sprints. Bugs take most of the time at least 2 weeks to fix, because they first have to acknowledge it, and then they have to put it on their schedule to be fixed. Its not that hard to understand really.
The sprint should address all reported defects from prior releases (and include validity). Then after you get over that 1st hurdle, the situation becomes more manageable. Submitting a bug and not hearing confirm/unconfirmed for months is unacceptable.
Maybe a 2week sprint is too short for the problems at hand?
Classic. Design issues become "too difficult" because the original developer did not understand the problem. They could defer tax calculation until after subtotals and discounts have been established. But they compute tax per item as they are added to the cart. This should have had the highest priority since it's a legal issue (and most likely is a legal issue in Russia as well).
Classic. Design issues become "too difficult" because the original developer did not understand the problem. They could defer tax calculation until after subtotals and discounts have been established. But they compute tax per item as they are added to the cart. This should have had the highest priority since it's a legal issue (and most likely is a legal issue in Russia as well).
Exactly. I just don't understand how cs-cart doesn't see it's loosing what probably is quite an amount of customers who test, see stuff like this, and are like what?! If they can't get calculations right, then how am I going to run a store with this software?
Submitting a bug and not hearing confirm / unconfirmed for months is unacceptable.
This shouldn't actually happen:
I kinda gave up some years ago
Basically you can hear a lot of dissatisfaction in some of the posts.
Can someone from the official side of the development team make a statement here? How can the situation be improved? How can the satisfaction of the CS-Cart users be increased?
Have any cs-cart developer think of making a YouTube cs-cart coding channel about how to fix common errors in php, create simple addons or even more advance later… debug…
I think cs-cart is the only community that apart the cs-cart docs for developers is hard to find any info about it even if you know php JavaScript takes so much time to make simple additions.
If anyone decides to do it and have a support account like Patreon for example I am willing to be supporter.
To be clear I am not willing to see there big projects and addons that the pro cs cart devs make now. Just small common coding about cs cart that even devs now seems they don’t have the time to fix to everyone
In my mind if we have this we can speed up common issue fixes and devs will have more time for creating useful addons and not spend all day for bug fixes
Have any cs-cart developer think of making a YouTube cs-cart coding channel about how to fix common errors in php, create simple addons or even more advance later... debug... I think cs-cart is the only community that apart the cs-cart docs for developers is hard to find any info about it even if you know php JavaScript takes so much time to make simple additions. If anyone decides to do it and have a support account like Patreon for example I am willing to be supporter. To be clear I am not willing to see there big projects and addons that the pro cs cart devs make now. Just small common coding about cs cart that even devs now seems they don’t have the time to fix to everyone In my mind if we have this we can speed up common issue fixes and devs will have more time for creating useful addons and not spend all day for bug fixes Sent from my iPhone using Tapatalk
Yeah but the thing is, nobody would really seed the competition would they?
And watching videos for development is hugely time consuming and usually doesn't penetrate with the needed detail. Good technical documentation that can be searched is the most efficient for an experienced developer who is not familiar with cs-cart. Just MHO.
And watching videos for development is hugely time consuming and usually doesn't penetrate with the needed detail. Good technical documentation that can be searched is the most efficient for an experienced developer who is not familiar with cs-cart. Just MHO.
Luckily CsCart documentation is pretty good. If you don't know something or can't find out something, just create an issue on the documentation repository on github.
You all don't get it, new features and more features is the priority for cs-cart. Their mentality revolves around more and more bells and whistles so they can say our cart is capable of 1,2,3 and a.b.c and also x.y.z. Quality of product, good design decisions is not something they are interested in, and classic example is lite checkout. They tried to reinvent something as critical as checkout and messed it up big time. I am still running old checkout.
You all don't get it, new features and more features is the priority for cs-cart. Their mentality revolves around more and more bells and whistles so they can say our cart is capable of 1,2,3 and a.b.c and also x.y.z. Quality of product, good design decisions is not something they are interested in, and classic example is lite checkout. They tried to reinvent something as critical as checkout and messed it up big time. I am still running old checkout.
This is exactly what I get... and why I started to have bugs / weird things / things store owners actually need fixed and improved myself.