uCommerce 1.5 prerelease 1 is now available for those who wish to test it.
Major new features include social commerce with product ratings, reviews, and comments with optional moderation workflow in the backend. Moderation is configured on the store level to either require approval of reviews and comments or not.
New reviews requiring attention are displayed on the store level while reviews in general are display in a new tab on individual products.
ProductReviewPipeline and ProductReviewComment pipelines control to processing logic when reviews and comments are submitted, approved, disapproved, and reported as abuse.
uCommerce Store features UI for customers to add new reviews, ratings, and comments. Also included is the ability to report abuse on the frontend which will resubmit a review to the moderation workflow while still keeping it online.
Category definitions enable custom properties on categories as is the case for products in previous versions. Available in the uCommerce backend under Product Catalog / Definitions / Category Definitions. Also included are new interfaces for supporting dynamic entities on your own objects: IDynamicEntity, IDefinition, IDefinitionField.
Nice url support out of the box. Use CommerceLibrary: GetNiceUrlForCatalog(), GetNiceUrlForCategory(), GetNiceUrlForProduct(), GetNiceUrlForVariant(). Url generation can be overridden by implementing the IUrlService interface and registering it in /umbraco/ucommerce/config/components.config.
Change log for 1.5.0.0:
NEW: Nice URLs for catalog, categories, and products.
NEW: Category definitions: Add custom properties to categories.
NEW: Social commerce with product reviews, ratings, and comments.
NEW: ProductReview and ProductReviewComment pipelines extension point to override default behavior.
NEW: Optional moderation of new reviews and comments (configure setting on individual product catalog groups).
FIX: Related products picker buttons would be placed far down the dialog when picking from a long category list.
Known issues which will be fixed before final release:
Frontend: Star rating UI not working in Chrome.
Frontend: New reviews don't appear until the browser is refreshed.
Frontend: GetNiceUrl is not used by uCommerce Store.
Frontend: Category definitions are lazy loaded thus incurring a performance penalty.
Backend: Category definition properties are displayed with name instead of their localized display name.
Backend: Empty review lists for stores and products are display an empty div.
Please note that prereleases should be used to testing only. Please report any issue with PR1 on this thread.
Custom product image UI renders with textbox instead of content picker.
Add product definition dialog not registered properly which caused an error when right clicking on product definition and selecting the "Create" menu item.
SKU when you add a product but you add a sku that has to many characters in it you get a Server Error message of String or binary data would be truncated. The statement has been terminated.
Not expected behaviour (Maybe a Bug) :Pricing and Saving
If you enter into a new product and for example you have two pricing structures in it Euro and GBP you add prices and forgot to check a box your pricing will not be saved but wiped. If you check a box then the pricing will be saved for all. I would expect if I hit Save for those fields to be saved even if I had not checked the box.
Ucommerce Demo Store: Images ...;( Still do not display. For first time user you get the feel that your ucommerce store is broken! Please Please fix. It is off putting.
Ucommerce Store: Update Cart Still looks to fail still because you have spacing in your <xsl:attribute name="name">quantityInput_</xsl:attribute> please fix.
Ucommerce Store: Add comment to you code especially you XSLT .. Would really help dev intergrate the new feature easily into there code base. Virtually none of the xslt has any comments on it. Drives me slight into insanity have to work out how demo code works.
When creating a new product definition propery we get the error:
The create dialog for "settings_catalog_productdefinition" does not match anything defined in the "~/umbraco/config/create/UI.xml". This could mean an incorrectly installed package or a corrupt UI file
There's a problem with product definition fields, when saving a product definition field with the same "Name" it complains: The item could not be saved. Ensure that all mandatory fields have been entered, and that the name of the item is unique. *
There are a few problems:
No stars are shown in the UI
There is a case to have the same name on two different product definitions i.e. "SKU" might be needed on both products
If they need to be unique then the user should be prompted this when creating the field
** Update **
You can ignore this one, I missed the star on the "Display Name" -please can you make this more obvious :)
When creating a new Data Type of "enum" the menu doesn't refresh to include the drop down list so you have to reload the nodes before being able to add the variations
Although only a minor
interface issue, please could you make the number boxes thinner (or at
least specify another CSS class so we can set it manually). In the
majority of cases they won't need to be entering numbers into the
nonillion's -though you never know ;)
Personally I think something
no wider than the SKU box (50px) will be fine but at least by setting
it in CSS you can easily override it if needs be
Variation "name" not brought through in the product XML. A lot of the time the user won't want/remember to complete the localised description fields as they're hidden away under the button so pulling through the name is important as it will mean we can fall back to their internal description where a proper name hasn't been supplied.
I've fixed the issues you reported save for the last one. Not quite sure what to make of it.
Tim: "Variation "name" not brought through in the product XML. A lot of the time the user won't want/remember to complete the localised description fields as they're hidden away under the button so pulling through the name is important as it will mean we can fall back to their internal description where a proper name hasn't been supplied."
Are we talking "display name" or "name"? Variants can't be saved without the "name" property so there shouldn't be a reason for a fallback there. For display names the XSLT could be constructed to pick up the parent value if it isn't present on the variants.
In regards Name/Display Name: "Name" is not brought through to the XML (which is what I would suggest falling back to in the absence of any "Display Name").
uCommerce 1.5 Prerelease 1 Available for Testing
uCommerce 1.5 prerelease 1 is now available for those who wish to test it.
Major new features include social commerce with product ratings, reviews, and comments with optional moderation workflow in the backend. Moderation is configured on the store level to either require approval of reviews and comments or not.
New reviews requiring attention are displayed on the store level while reviews in general are display in a new tab on individual products.
ProductReviewPipeline and ProductReviewComment pipelines control to processing logic when reviews and comments are submitted, approved, disapproved, and reported as abuse.
uCommerce Store features UI for customers to add new reviews, ratings, and comments. Also included is the ability to report abuse on the frontend which will resubmit a review to the moderation workflow while still keeping it online.
Category definitions enable custom properties on categories as is the case for products in previous versions. Available in the uCommerce backend under Product Catalog / Definitions / Category Definitions. Also included are new interfaces for supporting dynamic entities on your own objects: IDynamicEntity, IDefinition, IDefinitionField.
Nice url support out of the box. Use CommerceLibrary: GetNiceUrlForCatalog(), GetNiceUrlForCategory(), GetNiceUrlForProduct(), GetNiceUrlForVariant(). Url generation can be overridden by implementing the IUrlService interface and registering it in /umbraco/ucommerce/config/components.config.
Change log for 1.5.0.0:
Known issues which will be fixed before final release:
Please note that prereleases should be used to testing only. Please report any issue with PR1 on this thread.
Download uCommerce 1.5.0.0 PR 1
Download uCommerce Store 1.1.0.0 PR1
Very exciting thanks for allowing us a sneak peak. I will have a play on the dev machine on Sunday. ;)
Updated PR1 release with fixes for:
Custom product image UI renders with textbox instead of content picker.
Add product definition dialog not registered properly which caused an error when right clicking on product definition and selecting the "Create" menu item.
BUG: Add new Product.
SKU when you add a product but you add a sku that has to many characters in it you get a Server Error message of String or binary data would be truncated. The statement has been terminated.
Not expected behaviour (Maybe a Bug) :Pricing and Saving
If you enter into a new product and for example you have two pricing structures in it Euro and GBP you add prices and forgot to check a box your pricing will not be saved but wiped. If you check a box then the pricing will be saved for all. I would expect if I hit Save for those fields to be saved even if I had not checked the box.
Not Expected Behaviour :
Images still display with a fixed size and width on the product page. Why not just display the size they represent.
Ucommerce Demo Store: Images ...;( Still do not display. For first time user you get the feel that your ucommerce store is broken! Please Please fix. It is off putting.
Ucommerce Store: Update Cart Still looks to fail still because you have spacing in your <xsl:attribute name="name">quantityInput_</xsl:attribute> please fix.
Versioning on Store Demo: Don't version the store package! Arrragh which one to uninstall.. ;)
Store Demo: You need to make it obivous that if you are upgrading a store you need to remove the old one..
Ucommerce Store: Add comment to you code especially you XSLT .. Would really help dev intergrate the new feature easily into there code base. Virtually none of the xslt has any comments on it. Drives me slight into insanity have to work out how demo code works.
Maybe a Bug : Orders - > Shipping Methods -> Download I get a Javascript error.
Hi James,
Thanks for your feedback. We're working on revamping the uCommerce Store completely. I've implemented fixes for your reports on uCommerce itself.
Any ideas on how to fix this one Soren?
When creating a new product definition propery we get the error:
The create dialog for "settings_catalog_productdefinition" does not match anything defined in the "~/umbraco/config/create/UI.xml". This could mean an incorrectly installed package or a corrupt UI file
For others with the same error btw, edit ~/umbraco/config/create/UI.xml and change
<nodeType alias="settings_catalog_productdefinition_field">
<header>Commerce</header>
<usercontrol>/UCommerce/Settings/Catalog/CreateProductDefinitionField.ascx</usercontrol>
<tasks>
<delete assembly="UCommerce.Umbraco" type="Menu.Tasks.ProductDefinitionFieldTask" />
</tasks>
</nodeType>
To:
<nodeType alias="settings_catalog_productdefinition">
<header>Commerce</header>
<usercontrol>/UCommerce/Settings/Catalog/CreateProductDefinitionField.ascx</usercontrol>
<tasks>
<delete assembly="UCommerce.Umbraco" type="Menu.Tasks.ProductDefinitionFieldTask" />
</tasks>
</nodeType>
There's a problem with product definition fields, when saving a product definition field with the same "Name" it complains: The item could not be saved. Ensure that all mandatory fields have been entered, and that the name of the item is unique. *
There are a few problems:
** Update **
You can ignore this one, I missed the star on the "Display Name" -please can you make this more obvious :)
When creating a new Data Type of "enum" the menu doesn't refresh to include the drop down list so you have to reload the nodes before being able to add the variations
We can't delete a product definition field error message:
Error handling action
Object reference not set to an instance of an object.
Number fields are huuuge.
Although only a minor interface issue, please could you make the number boxes thinner (or at least specify another CSS class so we can set it manually). In the majority of cases they won't need to be entering numbers into the nonillion's -though you never know ;)
Personally I think something no wider than the SKU box (50px) will be fine but at least by setting it in CSS you can easily override it if needs be
Variation "name" not brought through in the product XML. A lot of the time the user won't want/remember to complete the localised description fields as they're hidden away under the button so pulling through the name is important as it will mean we can fall back to their internal description where a proper name hasn't been supplied.
Hi Tim,
Thanks for the feedback. I'll be plowing through it tomorrow and Friday.
Hi Tim,
I've fixed the issues you reported save for the last one. Not quite sure what to make of it.
Tim: "Variation "name" not brought through in the product XML. A lot of the time the user won't want/remember to complete the localised description fields as they're hidden away under the button so pulling through the name is important as it will mean we can fall back to their internal description where a proper name hasn't been supplied."
Are we talking "display name" or "name"? Variants can't be saved without the "name" property so there shouldn't be a reason for a fallback there. For display names the XSLT could be constructed to pick up the parent value if it isn't present on the variants.
That's great news thanks Soren.
In regards Name/Display Name: "Name" is not brought through to the XML (which is what I would suggest falling back to in the absence of any "Display Name").
HTH
Gotcha.
is working on a reply...