Forum Discussion
New "Site Pages" feature in O365 Team Sites conflicting with Publishing feature
You got the right channel; a perfect use of the MS Tech Community - SharePoint. :-)
The new, modern publishing pages don't use the classic publishing infrastructure, and the team is aware of the conflict and is working on a plan to mitigate how modern & classic interact when used in the same site. I'll loop back with the team that was working on this fix, but for the mean time, if a site has the publishing infra turned on already, then you would not see modern pages yet; and if you have modern team site, you cannot activate the publishing infra (as you experienced).
A current method you could employ is to create a site collection from within the SPO admin center. This will create a classic site, of which you then should be able to activate the classic publishing feature. And for sites that do not require classic publishing, you can continue to use "Create site' from SharePoint home, Outlook, Planner - wherever you can create an Office 365 Group, that group gets a modern team site.
Hope that helps, and know the team is working on a way to resolve the classic and modern publishing side by side.
Thanks,
Mark
I want to use audience targeting of Quick Links menu item on a Modern Team Site. Audience targeting is dependant on the Publishing feature.
I can activate the Publishing feature on Modern Team Sites, but this article says it's "not supported" ...
https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations-customize-sites
So where are we up to with this, please?
Can we activate the Publishing feature in Modern Team Sites but it's not supported? Or is it supported now and the article is out of date?
Matt MootyMicrosoft
Hey Lawrence,
That article is still up to date. Unfortunately, activating Publishing is all-or-nothing, and while it gives you audience targeting it also creates some undesirable behaviors in other parts of the site, so we are not supporting customers getting into this state. We haven't made a hard block in code, largely due to feedback in this thread, and we are still considering options to better communicate our support while avoiding any customer pain.
I would suggest requesting an Audience Targeting feature for Quick Links in UserVoice, where we can evaluate adding such a feature to the modern sites in a way that doesn't drag along all of the Publishing feature.
I hope this helps!
--Matt
Thank you for the speedy response.
I might have introduced some confusion, btw, when I said "Quick Links" when I meant "Quick Launch" menu, Quick Links being a new modern page web part and Quick Launch being the classic left menu.
But I'm guessing your reply might as well equally to both?
What I'm after is a general means of conditionally displaying on-the-page constructs, both page by page and where required on all pages, to supercede the Audience Targeting functionality (if Audience Targeting is going to disappear with the "classic" Publishing feature). SPFX might do this for developers being able to get hold of and conditional info and then fiddle with the page model, but I'm thinking more for power users and site admins.
I'll mark it up in uservoice, if it doesn't already exist there.
Thank you for the detailed explanation, Mark.
However, we are experiencing incompatibility in site collections already created with the SPO admin center.
When we create new subsites in these site collections, the feature "Site Pages" is activated by default, which prevents enabling the Publishing one. Our application automates the process of subsite creation + Publishing activation, and this process is now failing because before activating Publishing, first we need to deactivate the "Site Pages" feature.
How could we avoid generating a critical patch for all the environments? Do you know any other workaround?
Let me pull in Tejas Mehta who can dig a little more into it... Tejas?
Hi,
I'm using a site collection that I've created a couple of months ago. I use remote provisioning to create subsites and with that remote provisioning it enables the Publishing feature. However this doesn't do what's expected. E.g. the pages library isn't created. Als both the new feature and the publishing feature seem to be enabled on these sites, where you can't do this through the interface.
This is a serious break in functionality and causes issues in production environments where I used MS best practices for remote provisioning.
