This post was most recently updated on December 27th, 2018.Reading Time: 2 minutes.
Can’t access a web part page because of a broken web part? Yeah, that’s a classic issue – and it’s nicely ported into Modern world, too! In these cases, web part page maintenance mode comes in handy!
There’s a query parameter available for accessing it. For whatever reasons, it’s different for Classic and Modern mode, though. Why make things easy if you can make them dificult, right? :)
Instructions for Modern Mode
Modern SharePoint is a whole new user experience. It’s more than a fresh look, it’s designed from the ground up to work on mobile devices, and it addresses dozens of nagging usability issues. So far, modern SharePoint exists only in SharePoint Online. (See more)
Even though I’m going to claim that it’s less likely to encounter complete and total meltdowns as it’s more Classic cousin, you can still break a page completely by messing up with ADAL authentication, for example.
So, looking a the urls, this is the parameter you’ll need to add to the url: ?maintenancemode=true
Just like shown below:
At the very least Microsoft has made the maintenance mode a lot better in Modern experience – compare the screenshots and see the difference!
Instructions for Classic Mode
Classic is a term for the publishing-based SharePoint user experience and infrastructure, that existed before the Modern experience. And well, while it continues to exist for the foreseeable future, it’s slowly turning into an old-school solution. Still required for a lot of different workloads and use cases, and relevant for a long time – but compared with Modern, it often acts, looks and feels old.
To access the web part maintenance page in Classic SharePoint, you’ll need to add “Contents=1” to the url. See below:
The maintenance page for classic SharePoint publishing pages is useful, but not as polished as with Modern. See screenshot below.
And that’s it! Good luck fixing the issue that required you to google this solution in the first place! ;)
- How to fix “System.IO.FileSystem: Could not find a part of the path \AppData\Local\AzureFunctionsTools\Releases\3.17.0\workers. Value cannot be null. (Parameter ‘provider’)” when running Azure Functions locally? - January 12, 2021
- How to nuke the Identity Cache in Visual Studio? - January 11, 2021
- Fixing unexpected Microsoft.AspNetCore package errors after a dependency update - January 6, 2021