dashCommerce

Hey Guys

 I have a couple of questions, that I hope you might be able to help me with.

I'm using Danish language in DashCommerce, and I can see that everything is translated very nicely. However, the "Add to Cart" button still displays the English text, as the only thing I noticed so far. Is there a way to fix this?

I have made some test products to learn the way to use this software, and I have a problem with the Attributes. I have made four single-list attributes, and made three of the "Is Required". The idea was that the fourth option was optional, and if the user took no action here, and left it on "-- Select --", you could still add your product to the cart. However, this isn't the case.
Eventhough it's optional, the user is still required to select something. Until the user selects something the "Add to Cart" button is greyed out.
So far I've made a "none" value in the single-list which adds no additional cost, but I would prefer it if the user had the option of not using this attribute at all.

I have deleted some of my test products, but they don't get removed from the Admin site, they just have the value "Is Deleted = True". Does one have to edit the database to remove this from the list?

Thanks in advance.

The attributes thing sounds like a bug. I'd have to try some different use cases to be sure, but please feel free to log it at CodePlex.

We do "soft deletes" of products because we want to preserve the sales history associated with a product. We can look at hard deletes, so you can add this into the issue tracker as well.

Thanks for your answer. I will try to manage a workaround to avoid being bothered by the bug.

I have logged the problem on CodePlex as well.

Regards,
Steffen Danstrup

It popped into my head this morning why this is working the way it is - sometimes I forget

The attributes for a product map to the sku created for the product. So, if the user has not selected the last dropdown, then the sku is incomplete. There is an ajax call that takes the resultant attribute choices and marries them to the base sku. That ajax call either finds that sku or not. If it finds it, then the inventory linked to that sku is displayed. If it is not found, then the "Add to Cart" button remains disabled.

You could enable "Negative Inventory", which would enable the Add to Cart button all the time and then rely on the validation tied to the attributes to catch the required ones and let the non-required ones to fall through, but I am struggling a bit with a use case for the one you describe, so if you have any insight I'd love to hear it.