Forum Discussion
New "Site Pages" feature in O365 Team Sites conflicting with Publishing feature
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 MootyMicrosoft
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
- On a similar note to this. My root site collection had publishing enabled, but I have disabled it. I do not have modern Site Pages yet (been a day). Should I expect it to just show up? What can I do here? Thanks.
- Matt Mooty
Hi Joe,
You should be able to fix yourself by going to the site in question, and then going to Site Settings > Manage Site Features. On that page, you should see the Site Pages feature, and you can activate it from there. This will give you Site Pages in that site. If you don't see the feature, I'd be interested to know more details about that site.
We don't have any kind of automatic mechanism that activates Site Pages if you deactivate Publishing. When we added Site Pages (in the background) to existing team sites, we specifically avoided sites that had Publishing enabled, in order to proactively avoid the worst of any conflicts between the two features. That was a one-time operation, though, and won't fix you now if you "missed" it.
Hope this helps,
Matt
Matt, thanks for being open on this.
We also tested it and we can confirmed it is fixed.
As Martijn said, thanks for the short response time.
It is true that it works since yesterday :) Great stuff.
