X-Cart forums

[James.Schoaf]

Originally Posted by hoosierglass

For many of us the initial price was $99. I think looking for major beta help from the x-cart community is not too much to ask.

$99!? Who did you sleep with for that steal of a deal?

Also my beta test comment was based on a comment I have received from Qualiteam in the help desk where I had told them to hire more programmers (when they bumped the 4.3 release to October) and they responded with something along the lines of "Programmers would not help us find bugs".

[xplorer]

Originally Posted by James.Schoaf

You guys are killing me... I have 5 sites that want to start but won't until you launch 4.3 (because it is going to be the PCI compliant version).

Just to clarify. The only difference between 4.2 and 4.3 (within the scope of PCI-DSS requirements) is that you will be able to use 4.3 with X-Payments without modifications to its source code. When used in connection to X-Payments, 4.3 will process credit card payments in a PCI-DSS compliant manner. 4.1 and 4.2 users will be able connect their stores to X-Payments, but it may require custom modifications to their X-Cart installations.

Originally Posted by amy2203

I'm not arguing about offering a beta, but the roadmap is pretty useless if it depends on the level of testing done by the community.

We had moved the 4.3 release date not because we are not testing it and just waiting until you find all bugs. Beta testing is a great help from community (thank you!), but most of bugs are found by our testers. The new date is not caused by bugs in 4.3 at all.

[amy2203]

Originally Posted by xplorer

We had moved the 4.3 release date not because we are not testing it and just waiting until you find all bugs. Beta testing is a great help from community (thank you!), but most of bugs are found by our testers. The new date is not caused by bugs in 4.3 at all.

Good to know, Thanks for clarifying,

[cflsystems]

Originally Posted by xplorer

Just to clarify. The only difference between 4.2 and 4.3 (within the scope of PCI-DSS requirements) is that you will be able to use 4.3 with X-Payments without modifications to its source code. When used in connection to X-Payments, 4.3 will process credit card payments in a PCI-DSS compliant manner. 4.1 and 4.2 users will be able connect their stores to X-Payments, but it may require custom modifications to their X-Cart installations.

I was under the impression that for 4.1 and 4.2 you will provide installation scripts free of charge with what and how to modify the code. Or we will have to pay for this modification?

[xplorer]

Originally Posted by cflsystems

I was under the impression that for 4.1 and 4.2 you will provide installation scripts free of charge with what and how to modify the code. Or we will have to pay for this modification?

It depends on how complex the changes will be. I can't provide more info on this because development is not completed yet. It may turn out that the add-on will work without any modifications to 4.1 and 4.2.

[alarmsellout]

Does anyone know when is the final release for X-Cart 4.3.0 going to be released? I'd really like to upgrade my X-Cart as it's a pretty old version, but I'd rather wait until this version is released and then just re-install it.

[RichieRich]

Originally Posted by alarmsellout

Does anyone know when is the final release for X-Cart 4.3.0 going to be released? I'd really like to upgrade my X-Cart as it's a pretty old version, but I'd rather wait until this version is released and then just re-install it.

http://www.x-cart.com/roadmap.html

[alarmsellout]

Thanks!

[Serginfor.com]

An idea for future updates:

On orders management enter more orders Status
-Queued-order received (unpaid)
-Waits dispatch-order paid, but not sent
-Processed/dispatched-order processed and dispatched
-Complete-order delivered

[amy2203]

Originally Posted by Serginfor.com

An idea for future updates:

On orders management enter more orders Status
-Queued-order received (unpaid)
-Waits dispatch-order paid, but not sent
-Processed/dispatched-order processed and dispatched
-Complete-order delivered

Also, different language strings or something for downloadable products. We sell both downloadable and physical products, and it confuses customers to get a 'your order has shipped' email when it was a download, or to get a 'your order is complete' if it is being shipped - they don't get that that means shipped.

possibly a 'downloaded' status could be applied that is similar to Complete, but is auto set once they use their download key?