SOLVED
Home

Site Contents doesn't load in Chrome

%3CLINGO-SUB%20id%3D%22lingo-sub-59227%22%20slang%3D%22en-US%22%3ESite%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59227%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20else%20had%20an%20issue%20with%20SharePoint%20Site%20Contents%20not%20loading%20in%20Chrome%20lately%3F%20All%20other%20modern%20apps%20work%20fine%2C%20Site%20Contents%20seems%20to%20be%20the%20only%20page%20affected%20in%20all%20of%20my%20org's%20SharePoint%20sites.%20Nobody's%20on%20first%20release%2C%20Chrome's%20up%20to%20date%20and%20SharePoint's%20trusted.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-59227%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59644%22%20slang%3D%22en-US%22%3ERe%3A%20Site%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59644%22%20slang%3D%22en-US%22%3ETo%20clarify%20for%20anyone%20else%20that%20experiences%20this%20issue%2C%20it%20was%20specifically%20uBlock%20that%20caused%20the%20Site%20Contents%20loading%20issue--turning%20it%20off%20for%20SharePoint%20resolves%20the%20issue.%20AdBlock%20doesn't%20seem%20to%20share%20this%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59634%22%20slang%3D%22en-US%22%3ERe%3A%20Site%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59634%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20was%20the%20problem%20after%20all--thanks%2C%20Scott!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59625%22%20slang%3D%22en-US%22%3ERe%3A%20Site%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59625%22%20slang%3D%22en-US%22%3E%3CP%3EI%20experienced%20this%20starting%20yesterday%20on%20both%20Chrome%20and%20Firefox%2C%20but%20not%20IE.%20I%20disabled%20my%20ad%20blocker%20(uBlock%20Origin)%20and%20the%20page%20loaded%20successfully.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59237%22%20slang%3D%22en-US%22%3ERe%3A%20Site%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59237%22%20slang%3D%22en-US%22%3ENo%20problems%20here!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1236092%22%20slang%3D%22en-US%22%3ERe%3A%20Site%20Contents%20doesn't%20load%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1236092%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32928%22%20target%3D%22_blank%22%3E%40Matt%20Coats%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20The%20tenant%20admin%20should%20login%20to%20either%20%3CSTRONG%3E(XYZ%20as%20sample)%3C%2FSTRONG%3E%3A%3CBR%20%2F%3E-%20https%3A%2F%2F%3CSTRONG%3EXYZ%3C%2FSTRONG%3E-admin.sharepoint.com%2F%20and%20navigate%20to%20a%20classic%20page%20in%20the%20tenant-admin%3CBR%20%2F%3E-%20https%3A%2F%2F%3CSTRONG%3EXYZ%3C%2FSTRONG%3E-admin.sharepoint.com%2F_layouts%2F15%2Fonline%2FTenantSettings.aspx%3CBR%20%2F%3E-%20https%3A%2F%2F%3CSTRONG%3EXYZ%3C%2FSTRONG%3E-admin.sharepoint.com%2F_layouts%2F15%2FTermStoreManager.aspx%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Open%20browser%20console%20by%20F12%20or%20Ctrl%2BShift%2BJ%20(Cmd%2BShift%2BJ%20on%20Mac)%20and%20run%20a%20small%20script%20to%20clear%20corporate%20catalog.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20following%20is%20the%20Java%20Script%20they%20need%20to%20run%20from%20console%3A%3C%2FP%3E%3CUL%3E%3CLI%3Evar%20postBody%20%3D%20JSON.stringify(%7B%7D)%3B%3CBR%20%2F%3Evar%20req%20%3D%20new%20XMLHttpRequest()%3B%3CBR%20%2F%3Evar%20digest%20%3D%20document.forms%5BMSOWebPartPageFormName%5D%5B%22__REQUESTDIGEST%22%5D.value%3CBR%20%2F%3Evar%20serviceUrl%20%3D%20%22https%3A%2F%2F%3CSTRONG%3EXYZ%3C%2FSTRONG%3E-admin.sharepoint.com%2F_api%2FSP_TenantSettings_Current%2FClearCorporateCatalog%22%3B%3CBR%20%2F%3Ereq.open(%22POST%22%2C%20serviceUrl%2C%20false)%3B%3CBR%20%2F%3Ereq.setRequestHeader(%22Content-Type%22%2C%20%22application%2Fjson%22)%3B%3CBR%20%2F%3Ereq.setRequestHeader(%22x-requestdigest%22%2C%20digest)%3B%3CBR%20%2F%3Ereq.send(postBody)%3B%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

Has anyone else had an issue with SharePoint Site Contents not loading in Chrome lately? All other modern apps work fine, Site Contents seems to be the only page affected in all of my org's SharePoint sites. Nobody's on first release, Chrome's up to date and SharePoint's trusted.

5 Replies
Highlighted
No problems here!
Highlighted
Solution

I experienced this starting yesterday on both Chrome and Firefox, but not IE. I disabled my ad blocker (uBlock Origin) and the page loaded successfully.

Highlighted

That was the problem after all--thanks, Scott!

Highlighted
To clarify for anyone else that experiences this issue, it was specifically uBlock that caused the Site Contents loading issue--turning it off for SharePoint resolves the issue. AdBlock doesn't seem to share this problem.
Highlighted

@Matt Coats 

 

1. The tenant admin should login to either (XYZ as sample):
- https://XYZ-admin.sharepoint.com/ and navigate to a classic page in the tenant-admin
- https://XYZ-admin.sharepoint.com/_layouts/15/online/TenantSettings.aspx
- https://XYZ-admin.sharepoint.com/_layouts/15/TermStoreManager.aspx

 

2. Open browser console by F12 or Ctrl+Shift+J (Cmd+Shift+J on Mac) and run a small script to clear corporate catalog.


The following is the Java Script they need to run from console:

  • var postBody = JSON.stringify({});
    var req = new XMLHttpRequest();
    var digest = document.forms[MSOWebPartPageFormName]["__REQUESTDIGEST"].value
    var serviceUrl = "https://XYZ-admin.sharepoint.com/_api/SP_TenantSettings_Current/ClearCorporateCatalog";
    req.open("POST", serviceUrl, false);
    req.setRequestHeader("Content-Type", "application/json");
    req.setRequestHeader("x-requestdigest", digest);
    req.send(postBody);