Futhermore, if it's the case you can group the countries into multiple levels then the second level is missing "Default currency" incl. in the dialog:

Jamaica:

Test:

Hi Bjarne

Thanks for your great feedback!!

Regarding the default curreny - this is by design. A country region (like a state) dont have a different currency thatn its parent country (USA). So that is why :)

Kind regards
Anders

Hi Anders

Okay, so the structure is intended to be like:

• USA
• AL
• AK
• AZ
• ...
• ...
• ...

Hi Anders

I noticed a minor issue in the "Search criteria" area in Tea Commerce 2.3.2 - it might also be an issue in previously versions.
The for attribute refers to a different id and I think you just forgot to change it to a different field.

<divclass="umb-el-wrap ">
<labelclass="control-label"for="inputPassword">Order number</label>
<divclass="controls controls-row">
    <inputname="ctl00$ctl00$body$TxtOrderNumber"type="text"id="body_TxtOrderNumber"class="guiInputText guiInputStandardSize">
</div>
</div>

The for attribute with value inputPassword is on all fields in the search area. In the example above it should refer to body_TxtOrderNumber. If the textbox have ID="TxtOrderNumber" you could use ClientIDMode="static" or in for attribute write to ensure you get the right ID.

I also think it still is an issue that Tea Commerce 2.3.2 override the assembly Newtonsoft.Json.dll in /bin during install on e.g. Umbraco 7.1.4. and when you uninstall Tea Commerce it also removes the assembly unless you uncheck it from the uninstall. Perhaps it should be excluded from the build a just use the one in Umbraco? see more on this in this post.

Thanks.
/Bjarne

Hi Bjarne

That is Umbraco that does that. We just use their controls. So they properly has that error in the internals of Umbraco :)

Hi Anders

yeah, it seems there is an issue with how Umbraco transform the PropertyPanel, where the label always seems to have added for="inputPassword" ... at least when using loading .aspx page in Umbraco 7.

When the page is in a view (a html page) it could be written with the use of an alias attribute:

<umb-control-group label="Email" description="Persons email" alias="email">
    <input type="email" id="email" class="umb-editor umb-textstring" ng-model="person.email" />
</umb-control-group>

<umb-control-group label="Biography" description="Personal life details" alias="biography">
    <textarea type="text" id="biography" class="umb-editor umb-textarea" ng-model="person.biography"></textarea>
</umb-control-group>

Like Umbraco some places in the backoffice load .aspx pages (which I think will be rewritten in AngularJS at some point), these pages in .aspx for Tea Commerce will in future be rewritten in AngularJS?

/Bjarne

is working on a reply...