Home

Adding custom page metadata on existing modern sites?

%3CLINGO-SUB%20id%3D%22lingo-sub-269872%22%20slang%3D%22en-US%22%3EAdding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269872%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20page%20metadata%20on%20newly%20created%20sites%2C%20however%20it%20does%20not%20seem%20to%20work%20with%20modern%20sites%20created%20prior%20to%20this%20functionality%20being%20released.%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EWhen%20I%20add%20columns%20they%20do%20not%20get%20added%20to%20the%20%22Site%20Page%22%20content%20type%20even%20though%20%22Add%20to%20all%20content%20types%22%20is%20set%20to%20Yes.%20It%20also%20appears%20the%20contact%20type%20is%20sealed%20so%20I%20cannot%20manually%20add%20the%20column%20to%20the%20content%20type.%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EIs%20this%20expected%3F%20Is%20there%20anyone%20else%20experiencing%20similar%20results%3F%20Any%20workarounds%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3ETim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-269872%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetadata%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPages%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286219%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286219%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F35204%22%20target%3D%22_blank%22%3E%40Matthew%20Mason%3C%2FA%3EI%20also%20tried%20to%20create%20a%20new%20site%20content%20type%20which%20inherent%20from%20the%20built-in%20%22Site%20Page%22%20content%20type.%20and%20then%20i%20added%20the%20custom%20columns%20to%20the%20custom%20content%20type.%20after%20that%20i%20added%20the%20custom%20content%20type%20to%20the%20%22Site%20Pages%22%20library.%20but%20the%20problem%20i%20faced%20is%20that%20i%20were%20not%20able%20to%20force%20any%20new%20modern%20page%20to%20be%20created%20using%20the%20custom%20content%20type.%20as%20when%20users%20click%20on%20the%20%22Add%20a%20Page%22%20link%2C%20as%20follow%3A-%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20234px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F59696i2B95E2D973709D4C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22addapage.png%22%20title%3D%22addapage.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20built-in%20%22Site%20Page%22%20content%20type%20will%20still%20be%20used..%20and%20i%20did%20not%20find%20a%20way%20to%20force%20any%20new%20modern%20page%20to%20use%20the%20custom%20content%20type%20by%20default%3F%3F%20any%20advice%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286173%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286173%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20seen%20this%20exact%20behavior%20on%20multiple%20site%20collections%2C%20including%20the%20root.%20I%20haven't%20seen%20any%20formal%20documentation%20from%20MSFT%20on%20this%2C%20but%20it%20would%20appear%20the%20Site%20Page%20content%20type%20is%20%22special%22%20in%20some%20way.%20Additionally%2C%20we've%20added%20columns%20in%20the%20Site%20Pages%20library%20and%20saw%20they%20were%20not%20indexed%20properly.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20fix%20for%20all%20our%20issues%20on%20customizing%20the%20Site%20Pages%20was%20to%20create%20a%20custom%20content%20type%20inheriting%20from%20Site%20Page.%20If%20you're%20doing%20basic%20stuff%20with%20the%20new%20Page%20Properties%20model%20used%20in%20News%20and%20Highlighted%20Content%20web%20parts%2C%20this%20also%20works%20fine%20in%20that%20scenario.%20Oddly%20enough%2C%20while%20those%20custom%20columns%20don't%20show%20up%20in%20the%20search%20index%2C%20they%20worked%20fine%20when%20used%20as%20Page%20Properties.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20choose%20not%20to%20complain%20to%20much%20because%20modern%20is%20so%20vastly%20superior%20an%20experience%20to%20classic%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286054%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286054%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11521%22%20target%3D%22_blank%22%3E%40Tim%20Gagne%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F233354%22%20target%3D%22_blank%22%3E%40john%20john%3C%2FA%3Ejust%20a%20heads%20up%20I%20posted%20the%20same%20info%20to%20the%20comments%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FStructure-your-intranet-page-metadata-coming-to-SharePoint-in%2Fbc-p%2F267508%2Fhighlight%2Ftrue%23M2825%22%20target%3D%22_blank%22%3EStructure%20your%20intranet%20page...%3C%2FA%3E%20post%20and%20it%20has%20more%20traction%20and%20discussion%20than%20this%20separate%20post.%20I%20would%20recommend%20using%20that%20post%20and%2For%20reposting%20there%20since%20more%20people%20are%20looking%20at%20it.%20Basically%20others%20are%20seeing%20the%20same%20thing%20and%20we%20have%20not%20seen%20any%20official%20response%20yet.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11521%22%20target%3D%22_blank%22%3E%40Tim%20Gagne%3C%2FA%3EThanks%20for%20the%20info%2C%20will%20keep%20my%20eyes%20on%20this...%20But%20in%20my%20case%20i%20am%20working%20on%20a%20classic%20team%20site%2C%20and%20seems%20the%20%22Site%20Page%22%20content%20type%20is%20disabled%20only%20at%20the%20root%20site%20collection%2C%20and%20as%20a%20result%20we%20can%20not%20add%20custom%20columns%20to%20it.%3C%2FP%3E%3CP%3EBut%20if%20i%20create%20a%20new%20site%20collection%2C%20also%20of%20type%20classic%20team%20site%20then%20i%20can%20add%20cusotm%20columns%20to%20the%20%22Site%20Page%22%20content%20type%20and%20hence%20to%20the%20modern%20pages...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286024%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286024%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F233354%22%20target%3D%22_blank%22%3E%40john%20john%3C%2FA%3Ejust%20a%20heads%20up%20I%20posted%20the%20same%20info%20to%20the%20comments%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FStructure-your-intranet-page-metadata-coming-to-SharePoint-in%2Fbc-p%2F267508%2Fhighlight%2Ftrue%23M2825%22%20target%3D%22_blank%22%3EStructure%20your%20intranet%20page...%3C%2FA%3E%20post%20and%20it%20has%20more%20traction%20and%20discussion%20than%20this%20separate%20post.%20I%20would%20recommend%20using%20that%20post%20and%2For%20reposting%20there%20since%20more%20people%20are%20looking%20at%20it.%20Basically%20others%20are%20seeing%20the%20same%20thing%20and%20we%20have%20not%20seen%20any%20official%20response%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285441%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20custom%20page%20metadata%20on%20existing%20modern%20sites%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285441%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20am%20facing%20this%20exact%20problem%20on%20our%20classic%20team%20site%20..%20i%20am%20unable%20to%20add%20custom%20properties%20to%20our%20modern%20pages%20..%20and%20any%20custom%20column%20is%20not%20going%20to%20be%20added%20to%20the%20%22Site%20Page%22%20content%20type.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Tim Gagne
Occasional Contributor

We are using page metadata on newly created sites, however it does not seem to work with modern sites created prior to this functionality being released.
 
When I add columns they do not get added to the "Site Page" content type even though "Add to all content types" is set to Yes. It also appears the contact type is sealed so I cannot manually add the column to the content type.
 
Is this expected? Is there anyone else experiencing similar results? Any workarounds?

 

Thanks!

Tim

5 Replies

i am facing this exact problem on our classic team site .. i am unable to add custom properties to our modern pages .. and any custom column is not going to be added to the "Site Page" content type.

@john johnjust a heads up I posted the same info to the comments of the Structure your intranet page... post and it has more traction and discussion than this separate post. I would recommend using that post and/or reposting there since more people are looking at it. Basically others are seeing the same thing and we have not seen any official response yet.


@Tim Gagne wrote:

@john johnjust a heads up I posted the same info to the comments of the Structure your intranet page... post and it has more traction and discussion than this separate post. I would recommend using that post and/or reposting there since more people are looking at it. Basically others are seeing the same thing and we have not seen any official response yet.


@Tim GagneThanks for the info, will keep my eyes on this... But in my case i am working on a classic team site, and seems the "Site Page" content type is disabled only at the root site collection, and as a result we can not add custom columns to it.

But if i create a new site collection, also of type classic team site then i can add cusotm columns to the "Site Page" content type and hence to the modern pages...

We've seen this exact behavior on multiple site collections, including the root. I haven't seen any formal documentation from MSFT on this, but it would appear the Site Page content type is "special" in some way. Additionally, we've added columns in the Site Pages library and saw they were not indexed properly. 

 

The fix for all our issues on customizing the Site Pages was to create a custom content type inheriting from Site Page. If you're doing basic stuff with the new Page Properties model used in News and Highlighted Content web parts, this also works fine in that scenario. Oddly enough, while those custom columns don't show up in the search index, they worked fine when used as Page Properties. 

 

I choose not to complain to much because modern is so vastly superior an experience to classic :)

@Matthew MasonI also tried to create a new site content type which inherent from the built-in "Site Page" content type. and then i added the custom columns to the custom content type. after that i added the custom content type to the "Site Pages" library. but the problem i faced is that i were not able to force any new modern page to be created using the custom content type. as when users click on the "Add a Page" link, as follow:-

addapage.png

 

the built-in "Site Page" content type will still be used.. and i did not find a way to force any new modern page to use the custom content type by default?? any advice?

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies