Hi Julian,

The problem might be in your settings on the Tea Commerce: Variant Editor data type.

I managed to get the same error when I entered something invalid in the Variant group document types and Variant group name fields.

Can you share your settings?

Hi Brian,

Spot on, that was the issue I had the alias of the values doc Type in there, I can now select the variants, but I was expecting to be able to edit them as I have a doc type set in the "Variant document type" field on the editor. I only get the "edit variant types" or "delete" options, not the option to edit extended fields, sorry for all the questions but I couldn't find any docs telling me how to set this up.

No worries. Parts of the documentation could use some work :)

You should indeed be able to edit variant properties when a doc type is set in Variant document type.

Does the - Open all - button do anything? Do you get any errors in the console when you click on a variant?

Yes, I have the Variant Document Type set to the doc type alias of the document type that contains my extended properties. I don't get an error, but I don't get the "Fold Out" icon on the variant (like the one that appears on the example site), just the edit and delete icons

Hi, still can't get this working, can anybody shed any light? Tried emailing TeaCommerce and got an out of office for the next 4 weeks!

Ok, think I found the problem.

We are using version 7.11.0 of Umbraco, I think the "properties" tab on a doc type has now been removed. There is a line of code in the variant-editor-controller.js that removes the final tab (what it believes is the "properties" tab) from its array of tabs before iterating through all the properties on each remaining tab, as my doc type only had one tab it didn't think that my variant doc type had any properties.

the solution is to comment out the line that removes the final tab from the array, the final line below should be commented out

if ($scope.settings.docTypeAlias) {
  //There's a document type from the settings to load
  contentResource.getScaffold(-20, $scope.settings.docTypeAlias).then(function (data) {
    // Remove the last tab
    $scope.doctype = data.tabs.pop();

Hi Julian,

Nice work. That sounds correct. I think we need to figure out how to identify the Properties tabs, if it's there, and remove it only then.

Thanks for your insights.

/Rune

Thanks Rune, yes something like

    // Remove the last tab if it is the properties tab
    if (data.tabs[data.tabs.length - 1].alias === 'Properties') {
        $scope.doctype = data.tabs.pop();
    }

should work across all versions

Hmmm true, maybe check for a standard umbraco property on the tab such as "LastEdited" before removing

is working on a reply...