Please create a skin that can be used by developers to aid in the creation of a brand new custom skinned CS-Cart store.

The current skins contain far too much presentation code to start off a new store with so this developer skin should contain just the very basic elements that are needed. For example the overall layout, blocks.

The number of divs, classes and spans should be dramatically reduced and the stylesheets should contain only essential rules.

This developer skin could be added to the current list of skins available upon install and should be upgraded to match new version of the cart.

CSS and JS requires lots of unique classes and id's in order to target different items. If there aren't enough, then it makes it difficult to only use CSS and JS to modify the html. It's a very simple thing to add extra classes to be able to target with CSS and JS, so it wouldn't be such a major task if one knows where the template files are called at different locations.

For starters a simple class to add would be the controller name to div#content, or even body so everything is covered. Specific classes on span's that have text that might need to be changed. Specific classes on particular buttons in different locations.

Currently for some items very long strings of CSS selectors to target them. It's not the easiest thing when you need to go:
div > table > td > span > a > img.cm-image { }
just to target something simply because there are other cm-image classes that you don't want to target.

Very simple idea that would be just as simple to implement, yet would provide huge benefits by allowing simple CSS selectors.

Simple, right?

The ways in which the Admin can influence the way in which Product Options are displayed are very limited, with options essentially limited to Default Template or a couple of templates which claim to support longer Option Labels. In reality, this simply changes whether the Option Field and Option Label are displayed on the same line or split onto different lines. The deficiency of the latter option being that the space allowed for the Option label remains limited instead of using the full width of the container.

I therefore propose that the following issues are addressed:
1. It should be Admin configurable whether Product Options are displayed above the Description or below - this is important where there are many Product Options
2. The table of Product Options when in all in the same line mode should be a consistent size - say 30% for Label, 70% for Field
3. Quantity and Vendor fields on Long Option name templates should be properly aligned
4. Text Area fields are a different size to there types of fields - this should be made consistent
5. The error messages that appear when Required Fields are not completed should be standardised to the 'normal' field width - they are wider at present
6. Select Box fields can currently grow or shrink to fit their contents - not too bad if smaller than the standard field width, but causes issues if wider

These are particularly important to me as I rely heavily on Product Options to collect data, but it feels like an area of the system that hasn't had quite enough attention

Why have the option to choose default language in store-front if it's not used all the time?

We have our shop in a non-enligsh language and want ALL our customers to enter our store with XXX language. We have both English and XXX language activated in back-end and set default to XXX.

Mostly our customers enters and English language is chosen by default, i don't want our store to work like this:

"- The language which is defined in the URL by using the parameter of your language code.
- The language which is set up as the most preferable in your browser settings.
- The language which is set up as default one on the "Appearance settings" page of your CS-Cart admin panel.
- The language which is saved in cookies."

as it is today. I want to be able to choose and force our non-enlish language to all customers, regardless where they come from or what language they use in their browser etc.

For now, we can't have English activated as we loose XXX customers by this, because they automatically get wrong language! We have been translating all products and pages etc to English to be able to expand selling to other conutries as soon as this i fixed.

We wan't both XXX and English activated, but to use XXX as default ALL THE TIME and let customers change language in store-front to English for example, if they want.