This post was most recently updated on May 14th, 2019.2 min read.
This article describes an error situation that you might run into in Modern SharePoint, where you cannot take a page into edit mode anymore. You only get a strangely generic error message with a kinda weird failed request in the console. But, of course, there’s a fix – and an easy one at that!
Huh – so here’s a weird one for you!
Take a modern communication site, create a new beautiful page, produce some high quality content, and even go to great extents to have the right content type and all metadata filled out, hit publish and be happy. All good?
Sure! Until you want to edit the page the next time. Then you might run into this error:
You cannot edit this page
We’re sorry, we encountered an unexpected error. Please try again, if the problem persists please contact your Administrator.
Okay, that’s very non-descriptive. What exactly is happening? Let’s take a closer look into the console on the page in question…
Okay – the throttling aside, this (or similar) line is what’s interesting:
sp-pages-assembly_en-us_3a44851ceb440353702787c2ed227287.js:1189 POST https://contoso.sharepoint.com/sites/CommsSite190304/_api/sitepages/pages(3)/checkoutpage 406
For whatever reason, the request to check out the page before editing it fails, and the error message presented to the end user is less than helpful.
So far, we’ve found 2 different solutions. They might actually come down to the same technical solution behind the scenes, but the steps for the end-user are a bit different.
Solution 1: Restore an earlier version
In one case, we figured the latest, saved but not published, version of the page was somehow corrupted. The page looked like it was working but editing it just doesn’t work.
Not too surprisingly, restoring an earlier version might work in a case like this. In one case for us, it did.
Solution 2: Change the content type
Another option – maybe editing whatever page layout you have selected doesn’t work in Modern SharePoint? That was another case we encountered.
In this case, you should be good by changing the content type and your page layout to Site Page. See below for an illustration!
The first step is to select the item to access it’s Properties:
Then you need to take the Properties into edit mode:
Then you can change the Content Type (to Site Page, usually) – and that should remove the error:
All good? Not good? Let me know if it didn’t help and let’s fix it!
- Using role claims to target WebSockets - May 24, 2022
- The simplest fixes to “500 (Internal Server Error)” from Azurite - May 17, 2022
- How to solve “Npgsql: 42883: function create_hypertable(…) does not exist”? - May 10, 2022