You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to point out that there is a mismatch in displayoption values when upgrading from Optimizely CMS 11 to 12. In the old project EpiBootstrapArea was used and the display option values were set in the following way:
options.Add(new DisplayOption { Id = mode.Tag, Name = translatedName, Tag = mode.Tag, IconClass = mode.Icon }); (found in the branch epi10 - assuming this is similar to the Epibootraparea version 5.3.3 used in our older project)
In the latest version the options are added in the following way:
The list of addon displayoptions didn't have the id property in the past and the Tag-property was passed for the Id property of the displayoption. The new list of addon display options have the id field and that value does not derive from the CmsContentAreaTags, but is set statically as full, half etc.
This issue causes the new version to be incompatible as is to replace the old version. Work around to fix the issue is to set up a list of displayoptions in your project locally and replace the initialisation to use those values that match the old version instead.
Not an issue if this is being used for the first time, but can cause issues with migration projects where previous default values were used.
The text was updated successfully, but these errors were encountered:
Just wanted to point out that there is a mismatch in displayoption values when upgrading from Optimizely CMS 11 to 12. In the old project EpiBootstrapArea was used and the display option values were set in the following way:
options.Add(new DisplayOption { Id = mode.Tag, Name = translatedName, Tag = mode.Tag, IconClass = mode.Icon });
(found in the branch epi10 - assuming this is similar to the Epibootraparea version 5.3.3 used in our older project)In the latest version the options are added in the following way:
displayOption.Add(displayOption.Id, displayOption.Name, displayOption.Tag, "", displayOption.Icon);
The list of addon displayoptions didn't have the id property in the past and the Tag-property was passed for the Id property of the displayoption. The new list of addon display options have the id field and that value does not derive from the CmsContentAreaTags, but is set statically as full, half etc.
This issue causes the new version to be incompatible as is to replace the old version. Work around to fix the issue is to set up a list of displayoptions in your project locally and replace the initialisation to use those values that match the old version instead.
Not an issue if this is being used for the first time, but can cause issues with migration projects where previous default values were used.
The text was updated successfully, but these errors were encountered: