Can't edit modern pages on upgraded instance of Sharepoint 2019 (from 2013, 2016); menus appear to be broken

Question

After a migration from Sharepoint 2013 to 2019 (via 2016), everything went smoothly and our classic sites work without any issues. We want to rebuild our intranet with the modern site templates but when we create a site that uses the new modern site template such as the new Team Site or the Communication Site, we aren't able to edit pages at all.

• The "Settings gear" sub-menu options "Site Information", "Site Permissions", and "Change the look" do nothing except generate javascript errors in the console with all browsers we've tested

• Adding a page results in a blank page with no features to edit. I'm not exactly sure what it's supposed to look like (first time using the modern template) but I'm assuming that due to javascript errors, the elements are maybe failing to load.

I've tried creating entirely new web applications and site collections with the same results. Any ideas?

Answer 1

Hi @Josh

Have you tried other browsers? For example chrome? Are other browsers in the same state?

There is no valid information from the error report in the console, please check whether there is any related error in the uls log.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

We have the same problem here. The problem occurs with Edge Chromium but not Chrome. The problem appeared only after installing April 2021 cumulative updates. We have not tried to replicate the issue by installing a new SharePoint farm and testing without and with cumulative updates, but there were very little other possible factors to my knowledge that could have affected this.

Is there going to be an update to this from Microsoft some time soon?

Answer 3

did anyone fix this? we've got the same problem.. :(

Answer 4

Open developer tools (f12) and Doing a "Empty cache and har refresh" resolve the issue for me.