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
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.
Just to be sure, I did a check if this was a first release tenant issue. It isn't.
I have a site collection that's more than a year old and when I create a new subsite, this feature is turned on by default, and you cannot turn on the classic publishing feature without disabling this feature.
It breaks my code. This should be done in First release first, with proper communication and the option to turn of this change if you don't want it.
I'm relying on the publishing feature and there's no replacement yet. Please don't break existing stuff.