Meet Cs-Cart And Multi-Vendor 4.9.1
Rate Topic

We have released CS-Cart and Multi-Vendor 4.9.1. As usual, our blog describes the most important changes in detail, and the changelog has the list of all changes. That's why below we'll simply mention the most important improvements of the new version.

Only in Multi-Vendor:

• The ability to set flat transaction fees in addition to percentages in vendor plans.

I do see that the template editor double scroll bar has finally been fixed, I wonder however why it took such a long time, I submitted this bug at 28 February 2018 - 07:39 PM. Please do fix these insanely long times to respond to such simple issues.

I do see that the template editor double scroll bar has finally been fixed, I wonder however why it took such a long time, I submitted this bug at 28 February 2018 - 07:39 PM. Please do fix these insanely long times to respond to such simple issues.

i strugle also, to get a simple issue fixed,,, and they are busy developing new stuff i love it, but wait, let resolve old problems

I do see that the template editor double scroll bar has finally been fixed, I wonder however why it took such a long time, I submitted this bug at 28 February 2018 - 07:39 PM. Please do fix these insanely long times to respond to such simple issues.

We actively use offline payment methods a lot like the check template and business check methods.

Is this the complete list?

Will our data be lost form the orders using those methods.

We use the Offline payment methods for customers purchasing products on Amazon and Ebay. I can convert them to a different offline payment method. I just need to know all of the ones that are being deleted.

We actively use offline payment methods a lot like the check template and business check methods.

Is this the complete list?

Will our data be lost form the orders using those methods.

We use the Offline payment methods for customers purchasing products on Amazon and Ebay. I can convert them to a different offline payment method. I just need to know all of the ones that are being deleted.

Thanks

Ken

These templates are removed from the distribution package only. They will not be removed from the existing installations during the upgrade.

I do see that the template editor double scroll bar has finally been fixed, I wonder however why it took such a long time, I submitted this bug at 28 February 2018 - 07:39 PM. Please do fix these insanely long times to respond to such simple issues.

We searched the bug tracker but couldn't find the bug report you were referring to. Could you please give a link to the bug report (or, if you reported the issue via Help Desk, the ID of the ticket)? Then I'd be able to comment more on this matter.

I assume you're referring to this entry:

[!] Responsive admin panel: Design: Templates: One of the scroll bars was next to the wrong area. Fixed.

As far as I can see, that bug was fixed on September 5th after a report made by another person on August 21st.

I'm thinking when they say "under investigation" that it fits (and allieviates) the timeframe!

Yes, the 45-day countdown begins since the moment the bug receives the Confirmed status. We now have a page on our site that explains where the timeframe comes from. The Under Review status is supposed to be reserved for cases that require a longer and more thorough investigation. It is supposed to be used sparsely, and only when a situation calls for it. We've taken some steps to that end, and as I can see, in the past few months there were fewer and fewer bug reports to get this status.

We searched the bug tracker but couldn't find the bug report you were referring to. Could you please give a link to the bug report (or, if you reported the issue via Help Desk, the ID of the ticket)? Then I'd be able to comment more on this matter.

I assume you're referring to this entry:

[!] Responsive admin panel: Design: Templates: One of the scroll bars was next to the wrong area. Fixed.

As far as I can see, that bug was fixed on September 5th after a report made by another person on August 21st.

Yes, the 45-day countdown begins since the moment the bug receives the Confirmed status. We now have a page on our site that explains where the timeframe comes from. The Under Review status is supposed to be reserved for cases that require a longer and more thorough investigation. It is supposed to be used sparsely, and only when a situation calls for it. We've taken some steps to that end, and as I can see, in the past few months there were fewer and fewer bug reports to get this status.

I first mentioned this directly in the thread of the responsive admin panel on february:

Thank you for providing the links. However, I couldn't find any mention of that particular problem in those posts:

[!] Responsive admin panel: Design: Templates: One of the scroll bars was next to the wrong area. Fixed.

Basically, the scroll bar of the file tree wasn't next to the file tree, but in another block, next to the file contents and its own scroll bar.

Still, your point about the bug tracker is valid. As I mentioned, a couple of months ago we've addressed the issue of bug confirmation taking too long. There shouldn't be such issues for newly-reported bugs (or at least they should be very rare). However, there are a couple of things I'd like to point out:

1. A bug posted on the forum can easily be overlooked. It is vital that a bug is posted on the bug tracker or sent to us via Help Desk (that is mentioned in our bug fixing policy).

2. It's best to post one issue per bug report (we might add that rule in the future). That way people would easily see what has been fixed already, and it'd be easier for us to check, confirm, and fix individual bugs.

The countdown should begin when the bug is reported. Sometimes a bug sits in "under investigation" for months before it's looked at and confirmed.

I see your point. But the bug fixing policy explains why the countdown works as it does. It is exactly for the reason that making the bug occur again (which is a vital part of fixing it) can take an undetermined amount of time and may depend on an untold number of circumstances. But once the bug is confirmed, we know how soon we can fix it.

I see your point. But the bug fixing policy explains why the countdown works as it does. It is exactly for the reason that making the bug occur again (which is a vital part of fixing it) can take an undetermined amount of time and may depend on an untold number of circumstances. But once the bug is confirmed, we know how soon we can fix it.

But that would assume that it's actively being looked at. There is no communication of any test results or replication problems. It only sits there with no response.

Suggest you take the customer/developer perspective and ensure that all reported bugs are assessed in a timely manner (less than a week) and if there are issues reproducing it, tot communicate with the submitter so they can clarify if need be.

Leaving them in "under investigation" for months on end only goes to add to your backlog and to frustrate your customers.

It is about the release contents. Arguably, this should probably have been in a 4.7.x thread but since the defect wasn't addressed (and they couldn't even find it afterward) it seems fine to bring it up as a topic in this thread. The goal is to have cs-cart recognize the need to stay on top of reported defects and to confirm/address them in a timely manner. New features are great. But if they come at the expense of an unstable and buggy platform, then their value is dramatically diminished.