ContentReference Properties in SystemTabNames.PageHeader no longe

November Happy Hour will be moved to Thursday December 5th.

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / Problems and bugs /

ContentReference Properties in SystemTabNames.PageHeader no longer editable

Matthew Jimenez

Vote:

In CMS 11, we used a ContentRefernce as a PageHeader property. After upgrading to CMS 12, we found that we could attempt to change the value, but the new value would not be saved.

Changing the GroupName fixes the issue, but of course moves the location of the property

[Display(Name = "Header", GroupName = SystemTabNames.PageHeader, Order = 10)]
[AllowedTypes(typeof(MainHeaderBlock))]
public virtual ContentReference Header { get; set; }

#290929

Nov 01, 2022 22:08

Anil Patel

Vote:

Hi Matthew,

If this is still an issue, one option could be to create a new ContentReference property with a similar name as the old property on the PageHeader tab for this. Then look to remove the old property so all references in code and in the CMS link to the new property.

#295572

Jan 29, 2023 23:38

Matthew Jimenez

Vote:

There's nothing broken with the property itself - simply moving it to a new groupname, which we chose as "Layout", put it down in a tab that allowed edits to work.

This is specifically a problem with the CMS editor, but I've not verified if that has been fixed as we won't be returning these properties to PageHeader.

#295660

Jan 31, 2023 14:59

Eric Herlitz

Vote:

Which version of CMS do you have? It works just fine in 12.16.0

[Display(
    Name = "Contact",
    GroupName = SystemTabNames.PageHeader,
    Order = 20)]
[AllowedTypes(AllowedTypes = new[] { typeof(ContactBlockType) })]
[CultureSpecific(true)]
public virtual ContentReference ContactTest { get; set; }

Screen recording of dropping a block in the property shown in code above. It is still present after a reload and is saved to the DB.

I have also verified so the property can be replaced, removed or changed.

#295671

Edited, Jan 31, 2023 15:55

Matthew Jimenez

Vote:

It seems it was a problem in CMS 12.13. Just tested in 12.15.1, and it appears to be working properly now.

#295674

Jan 31, 2023 16:39

This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.