UAAS-756 - PreValues do not get resolved for dropdown (flexible) in DTGE during content transfer

Created by Jonas Pyfferoen 03 Jul 2018, 14:04:21 Updated by Tor Langlo 23 Aug 2018, 20:12:33

Tags: Gold partner

Duplicates: UAAS-739

Not sure which data types would be affected (all those using prevalues & id's I guess?), my case:

Local & DEV: Dropdownlist.Flexible: Alignment 2 possible values:

  • Left (id: 19)
  • Right (id: 20)

JSON value: { "dtgeContentTypeAlias":"imageAndTextBlock", "value":{
"name":"Image and Text Block", "intro":"

Lorem

", "body":"", "link":[

     ],
     "image":"umb://media/6772cf77e4e64ae2bbd7d744372fb6bc",
     "imageLarge":"umb://media/597816af53594a838848b08bdcb1703f",
     "imageAlignment":[  
        "20"
     ]

}

PRD: Left: id 8 Right: id 9

JSON value stays: "imageAlignment":[
"20" ]

Comments

Alan Mac Kenna 03 Jul 2018, 15:24:39

@jpyfferoen@reference.be would this be something to log over at the DTGE repo? https://github.com/umco/umbraco-doc-type-grid-editor/issues


Jonas Pyfferoen 03 Jul 2018, 17:34:14

@alan.mackenna Fix has to happen in https://github.com/umbraco/Umbraco.Deploy.Contrib it seems, which is in your hands? I asked Lee about it and he pointed me towards here.


Jonas Pyfferoen 04 Jul 2018, 08:44:39

I did some further testing with:

  • Nested Content with a document type which has the "Alignment" editor.
  • Document type with the "Alignment" editor

Values are not converted on transfer for any of those, so I guess this is a general issue on Umbraco Deploy. Sometimes cmsDataTypePreValues will have to be checked to make a mapping on the id's.


Claus Jensen 04 Jul 2018, 09:24:52

This is a bug with the prevalueconnector in general - most likely not a bug in DTGE.

It only handles dropdown editors using the alias: Umbraco.Dropdown and not the new Umbraco.Dropdown.Flexible.

There's a workaround here: http://issues.umbraco.org/issue/UAAS-739 and the issue is also fixed in the next release of Deploy :)


Jonas Pyfferoen 04 Jul 2018, 09:38:20

just to confirm, workaround helped indeed.


Claus Jensen 04 Jul 2018, 09:42:12

Great @jpyfferoen@reference.be ! Just fyi - version where this is fixed is 2.0.15 (and 1.0.22). Having used the workaround when the fix is applied should not make a difference so you can just remove it sometime later after the next release has been deployed.


Jonas Pyfferoen 04 Jul 2018, 10:34:29

Further info, the workaround seems to work fine for document types & nested content. Haven't got DTGE working yet.


Tor Langlo 23 Aug 2018, 20:12:33

@jpyfferoen@reference.be Same here, I'm unable to get workaround to work for DTGE.


Priority: Normal

Type: Bug

State: Duplicate

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: