Forum Discussion
New "Site Pages" feature in O365 Team Sites conflicting with Publishing feature
Hi guys, I don't know if this is the appropriate channel to post something like this. If not, please redirect me to the right one. Between yesterday and today we've noticed a new behavior in ...
Matt Mooty
Microsoft
MicrosoftHi Enric,
We have reverted the code which causes the two features to fail activation if the other is already active. You should now be able to activate the SharePoint Server Publishing feature when the Site Pages feature is already active and vice versa. Please let us know if it does not work.
Also, just to clear a couple things up: this Site Pages feature has been active on most Team sites and all new Team sites for months now, but it has not been visible. We made it visible and added the feature non-coexistence check recently, but it is unrelated to the SPFx rollout.
My apologies for any frustration this caused, and thank you for using SharePoint.
--Matt Mooty
Hi Matt, many thanks for your reply. We will try in our tenants.
Hi Matt,
I've tested this and it seems to be fixed.
I do have some mixed feelings about this. Your response time is great, apperantly fixing it in a couple fo days. But why is adding such a non-coexistence check not communicated, tested properly and rolled out gradually to first release tenants first? This seems to be a big breaking change that hurts a lot of people and causes serious issues. And especially when we're using a Microsoft recommended approach using remote provisioning.
- Matt Mooty
Hi Martijn,
Glad it's working for you now, and sorry for the inconvenience. We didn't fully understand the impact of this change because we were not aware of how widespread the practice of remotely activating the Publishing feature on a Team site is. Once it was reported, we were able to revert the change. We are actively discussing ways to better support coexistence of the Site Pages feature with classic Publishing on existing sites, and will be proactive communicating with the community as we roll out. Thanks again for the feedback.
--Matt
