I don't see a specific thread to report Smith Cart bugs, so I'd like to suggest opening one. Let me know if there is a place to report bugs.

Version: 4.56.0

Confirm Order Page:
There is a random tick box on that page with no description as to what it is for. When you Submit the order, the page refreshes and asks that you tick this box. Looking into the source, this looks like a checkbox to confirm the order (dnn_ctr459_Confirm_chkAgree). The tick box needs a description label telling the client what they need to do.

Solution:
If I may make a suggestion. If Checkbox is required, then upon saving the settings in Smith Cart, the person should be notified that they have not added a label which is required. (See attached)

Version: 4.56.0

Details Page:
We have tested this in our skinned version and the fresh install you sent us.

Procedure to recreate:

• Go to shop.
• Select a product to go to details page.
• Add ten as your quantity in text field.
• Select Add to Cart
• Click View Cart.
• There will be nothing in the cart.
   
• Click back button on browser.
• Click Add To Cart again with same amount.
• Click View Cart.
• You should now have ten items in your shopping cart.

Doing the same procedure does the same thing over and over.

Possible Solution:
It seems that the first click event to Add To Cart is not calling the method it should when the page first loads. Or the quantity is not being attached as it should when the link is clicked.

Here is a screencast of the procedure: http://screencast.com/t/vqntPzeyKo

Hi James,

First Post - The checkbox you are referring to is the "Show Checkbox" feature located in the Cart Settings under the Confirmation Page Setup section. The reason the Textbox Label is not required is some may want to have a label associated with the checkbox. If the Cart enforced this rule if would be less flexible and our goals is to make the product as flexible as possible to support as many different business requirements as possible.

2nd Post - I have confirmed when you are directed to MyGate and you click the back button in the browser you will be taken back to the Confirmation and if you click Submit Order the transaction will be processed without going to the Gateway. I have sent this into programming and will post back when an update is available.

3rd Post - I have also confirmed that when a quantity is enetered in the quantity box on the Product Details page and Add To Cart is clicked the quantity will not be added to the Cart on the first click. This has also been sent into programming and an update will be available shortly.

4th Post - The reason the Billing information is not being populated on the Conformation page is because you are using a Hosted Gateway where the Billing Information is not entered. After a successful transaction if you look in the Manage Orders section of the Admin Menu the Billing Information will be populated with the Shipping Info entered on Step 1 of the Checkout Process.

Regarding your first and 4th post, may I suggest reading some of the back traffic before posting doing a keyword search for words relating to your problem using the Search function above before you post. It may find you an answer, and save you time. More generally, imagine looking at the index of an archive of questions, with just the subject lines showing.

Thanks,

Hi James,

We appreciate the time an effort you have taken to point these items out to us. We will be providing an update as soon as possible. We do not typically offer beta versions however we do keep a record of all upcoming changes updates and fixes located to the left of the forum and if you would ever like to recieve or trial the Cart in between our releases, you are always welcome to email support@smith-consulting.com  to request a "beta" version from our programming dept.

As i'm sure you know, debugging is still a tedious task requiring considerable effort. Even with the aid of a debugger, locating what triggers certain scenarios is something of an art. It is not uncommon for a issue in one section as of a program to cause failures in a completely different section, thus making it especially difficult to track, in an apparently unrelated part of the system as it is common to change the code instead of the other parts, as the cost and time to change it is generally less. Often programmers spend more time and effort finding and fixing bugs than writing new code. Some instances are triggered by inputs to the program which may be difficult for the programmer to re-create. As our modules grow to be more complex with every release, issues become more difficult to fix. On some projects, more resources can be spent on testing than in developing the program. It is not always easy to reproduce issues, some are triggered by inputs to the program which may be difficult for the programmers to re-create. It is common practice for software to be released with known bugs that are considered non-critical, that is, that do not affect most users' main experience with the product. While software products may, by definition, contain any number of unknown bugs, measurements during testing can provide an estimate of the number of likely bugs remaining; this becomes more reliable the longer a product is tested and developed.

I understand that you guys have made extensive modifications to the styling and as always we are open to suggestions by posting in our Enhancement Requests forum and if you have made changes to the ascx pages and impoved the html/css please send your changes to support@smith-consulting.com and we'll review and add to the main cart build so you get those changes if you do any upgrades in the future.

Thanks again for your time and we appreciate your business,