Context:

Smith Cart 3.98

DotNetNuke 5.6.1

SQL Server 2008

Problem:

I'm setting up the cart for the first time. In Settings > Tax Setup, I select the Charge Tax in Taxable Status List radio button, then I select a state in the States box. I then select the ">>" button to add the state to the Taxable States box. The page does a postback, but does not add the state. Any ideas?

Thanks,

Steve

I uninstalled the prior version, in installed the current version. Problem persists. Strange that the same kind of control used in DNN Admin works fine, but doesn't work for this product. Anyway, I decided to just enter the state into the database directly, as a work-around.

Can someone who is charging state tax take a look at their Smith_Tax table and let me know if the data I entered seems correct? Here is what I entered:

TaxStateId: 1

StateText: California

State: California

CountryCode: US

PortalID: 0

(TaxStateID was auto-generated, so I guess that's not configurable. I don't know if my guess of "California" for StateText is right, or if it needs something else in there.)

At least "California" is now selected in the cart setup. I just need to make sure it's the right information that I've entered. Anyone?

Steve

Okay, I've solved it -- and I can't believe I'm the first one to encounter the issue.

It turns out that, before the control would allow me to add states to the state tax field, I first had to populate the required fields (those fields that have form validation invoked, and that are marked with a red "*"), THEN SAVE THE CONFIGURATION FORM, then RETURN to add states to the state tax field. Obviously this was not duplicated on the test site because the cart has already been configured there and, presumably, all required fields previously populated. Make sense?

I respectfully suggest that is a bit of a design flaw, and one that unfortunately targets newbies setting up the cart for the first time (such as me).

IMHO, that control should either not be presented until the configuration is saved with the required fields, or the control itself should permit population of the data without having first to submit the form with the required fields populated. (Maybe it's an AJAX issue, dunno.) At the very least, this should be documented in the manual if it is not changed in a future build, IMHO.

Anyway, I hope this is useful feedback. :-)

Steve