Modern Site Page search issue

%3CLINGO-SUB%20id%3D%22lingo-sub-87284%22%20slang%3D%22en-US%22%3EModern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87284%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20created%20a%20new%20modern%20site%20page%20and%20it%20looks%20great.%20I%20am%20having%20an%20issue%20using%20the%20search%20on%20the%20page%20though.%20When%20I%20start%20typing%20I%20get%20the%20suggested%20results%2C%20but%20if%20I%20click%20%22Show%20more%20results%22%2C%20I%20get%20directed%20to%20a%20blank%20page.%20Even%20more%20odd%2C%20the%20path%20is%20the%20full%20Site%20Page%20path%20including%20.aspx%20appended%20with%20%22search%2Fsitefiles%3Fq%3D%5Bquerystring%5D%26amp%3Bs%3D%5BSiteUrl%5D%22.%20The%20Tenant%20is%20still%20on%20classic%20if%20that%20matters%20at%20all.%20If%20anyone%20can%20point%20me%20in%20the%20right%20direction%20for%20this%20issue%2C%20it%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-87284%22%20slang%3D%22en-US%22%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-134704%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134704%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20three-month-long%20ticket%20with%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134664%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134664%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20this%20same%20issue.%26nbsp%3B%20Any%20resolution%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123895%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123895%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20this%20same%20problem%20and%20MS%20Support%20has%20been%20incredibly%20unhelpful.%20Did%20you%20get%20it%20resolved%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88559%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88559%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20going%20to%20get%20the%20go%20ahead%20to%20turn%20on%20the%20Modern%20Experience%20at%20the%20tenant%20soon.%20If%20that%20doesn't%20fix%20it%20then%20I%20will%20put%20a%20ticket%20in.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88254%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88254%22%20slang%3D%22en-US%22%3E%3CP%3Ecan%20you%20open%20a%20support%20ticket%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87514%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87514%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20what%20I%20get%20in%20the%20console%20(removed%20some%20information%20for%20security)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERefused%20to%20display%20'%3CA%20href%3D%22https%3A%2F%2Fportal.office.com%2FSuiteServiceProxy.aspx%3Fupn%3D%5BUser%5D%E2%80%A6%5BSiteUrl%5D%26amp%3BSilent%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.office.com%2FSuiteServiceProxy.aspx%3Fupn%3D%5BUser%5D%E2%80%A6%5BSiteUrl%5D%26amp%3BSilent%3D1%3C%2FA%3E'%20in%20a%20frame%20because%20it%20set%20'X-Frame-Options'%20to%20'sameorigin'.%3CBR%20%2F%3Eshellplusg2m_73d3a900.js%3A29%20GET%20%3CA%20href%3D%22https%3A%2F%2Fportal.office.com%2FSuiteServiceProxy.aspx%3Fupn%3D%5BUser%5D%E2%80%A6%5BSiteUrl%5D%26amp%3BSilent%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.office.com%2FSuiteServiceProxy.aspx%3Fupn%3D%5BUser%5D%E2%80%A6%5BSiteUrl%5D%26amp%3BSilent%3D1%3C%2FA%3E%20net%3A%3AERR_BLOCKED_BY_RESPONSE%3CBR%20%2F%3EO365SuiteServiceProxy.RequestExecutor.G%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Ep%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Ej%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Em%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Ea%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Ec%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3EGSAA%20%40%20shellplusg2m_73d3a900.js%3A32%3CBR%20%2F%3Eq%20%40%20shellplusg2m_73d3a900.js%3A34%3CBR%20%2F%3E(anonymous)%20%40%20shellplusg2m_73d3a900.js%3A34%3CBR%20%2F%3E(anonymous)%20%40%20shellplusg2m_73d3a900.js%3A34%3CBR%20%2F%3E(anonymous)%20%40%20shellplusg2m_73d3a900.js%3A32%3CBR%20%2F%3ES2Ss.a.Sv.SessionStorageRequest.u%20%40%20shellplusg2m_73d3a900.js%3A32%3CBR%20%2F%3ESessionStorageRequest.r.d%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3EO365SuiteServiceProxy.RequestExecutor.internalOnMessage%20%40%20shellplusg2m_73d3a900.js%3A29%3CBR%20%2F%3Eshellplusg2m_73d3a900.js%3A29%20Failed%20to%20execute%20'postMessage'%20on%20'DOMWindow'%3A%20The%20target%20origin%20provided%20('%3CA%20href%3D%22https%3A%2F%2Fportal.office.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.office.com%3C%2FA%3E')%20does%20not%20match%20the%20recipient%20window's%20origin%20('null').%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87439%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87439%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20wasn%C2%B4t%20understanding%20if%20the%20blank%20was%20only%20for%20part%20of%20the%20page%2C%20or%20if%20the%20browser%20would%20just%20be%20totally%20blank%20without%20any%20menu.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat%20url%20is%20the%20url%20when%20searching%20on%20the%20site%20for%20example%20on%20modern%20ui%20but%20i%20see%20results%20.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20fiddler%20return%20anything%26nbsp%3B%3F%20Also%20if%20you%20press%20f12%20do%20you%20see%20any%20errors%20on%20the%20Console%20%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87426%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87426%22%20slang%3D%22en-US%22%3EA%20screen%20shot%20of%20the%20blank%20page%3F%20The%20url%20is%20as%20stated%20%5BFullPath%5D%2Fsearch%2Fsitefiles%3Fq%3D%5BqueryString%5D%26amp%3Bs%3D%5BSiteUrl%5D.%20I%20am%20looking%20into%20turning%20the%20modern%20experience%20on%20for%20the%20site%20collection%20and%20seeing%20if%20that%20will%20work.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87424%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87424%22%20slang%3D%22en-US%22%3E%3CP%3Edo%20you%20have%20a%20screenshot%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87394%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87394%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20to%20replicate%20the%20issue%20on%20my%20dev%20tenant%20and%20it%20seems%20to%20work%20just%20fine.%20It%20even%20uses%20the%20same%20URL%20construct%20which%20I%20suppose%20is%20normal%20now%2C%20I%20am%20just%20unfamiliar%20with%20it.%20Does%20anyone%20know%20if%20the%20Tenant%20has%20to%20be%20using%20the%20modern%20experience%20for%20the%20search%20to%20work%20properly%20from%20the%20modern%20site%20pages%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87314%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87314%22%20slang%3D%22en-US%22%3EStrange%2C%20I'm%20not%20having%20this%20blank%20experience%20when%20trying%20to%20reproduce%20your%20problem...I%20get%20the%20new%20search%20results%20page%20and%20I%20can%20from%20there%20also%20go%20to%20the%20classic%20search%20results%20page%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2188246%22%20slang%3D%22en-US%22%3ERe%3A%20Modern%20Site%20Page%20search%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2188246%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66403%22%20target%3D%22_blank%22%3E%40Timothy%20Willis%3C%2FA%3E%26nbsp%3BI%20don't%20know%20if%20this%20has%20been%20answered%2C%20but%20I%20had%20the%20same%20problem%20and%20there%20is%20a%20simple%20answer.%26nbsp%3B%20For%20example%3A%20If%20you%20type%20%22624%22%20in%20the%20%22Search%20this%20Site%22%20box%26nbsp%3B%20files%20will%20appear%20in%20the%20drop%20down%20list.%20Make%20sure%20you%20append%20a%20%22*%22%20changing%20to%20%22624*%22%20before%20clicking%20on%20%22Show%20More%20Results%22.%20All%20the%20files%20in%20the%20library%26nbsp%3B%20with%20%22624%22%20in%20the%20name%20will%20then%20appear.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I have created a new modern site page and it looks great. I am having an issue using the search on the page though. When I start typing I get the suggested results, but if I click "Show more results", I get directed to a blank page. Even more odd, the path is the full Site Page path including .aspx appended with "search/sitefiles?q=[querystring]&s=[SiteUrl]". The Tenant is still on classic if that matters at all. If anyone can point me in the right direction for this issue, it would be greatly appreciated.

12 Replies
Strange, I'm not having this blank experience when trying to reproduce your problem...I get the new search results page and I can from there also go to the classic search results page

I tried to replicate the issue on my dev tenant and it seems to work just fine. It even uses the same URL construct which I suppose is normal now, I am just unfamiliar with it. Does anyone know if the Tenant has to be using the modern experience for the search to work properly from the modern site pages?

do you have a screenshot ?

A screen shot of the blank page? The url is as stated [FullPath]/search/sitefiles?q=[queryString]&s=[SiteUrl]. I am looking into turning the modern experience on for the site collection and seeing if that will work.

i wasn´t understanding if the blank was only for part of the page, or if the browser would just be totally blank without any menu.

 

That url is the url when searching on the site for example on modern ui but i see results .

 

Does fiddler return anything ? Also if you press f12 do you see any errors on the Console ?

 

This is what I get in the console (removed some information for security):

 

Refused to display 'https://portal.office.com/SuiteServiceProxy.aspx?upn=[User]…[SiteUrl]&Silent=1' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
shellplusg2m_73d3a900.js:29 GET https://portal.office.com/SuiteServiceProxy.aspx?upn=[User]…[SiteUrl]&Silent=1 net::ERR_BLOCKED_BY_RESPONSE
O365SuiteServiceProxy.RequestExecutor.G @ shellplusg2m_73d3a900.js:29
p @ shellplusg2m_73d3a900.js:29
j @ shellplusg2m_73d3a900.js:29
m @ shellplusg2m_73d3a900.js:29
a @ shellplusg2m_73d3a900.js:29
c @ shellplusg2m_73d3a900.js:29
GSAA @ shellplusg2m_73d3a900.js:32
q @ shellplusg2m_73d3a900.js:34
(anonymous) @ shellplusg2m_73d3a900.js:34
(anonymous) @ shellplusg2m_73d3a900.js:34
(anonymous) @ shellplusg2m_73d3a900.js:32
S2Ss.a.Sv.SessionStorageRequest.u @ shellplusg2m_73d3a900.js:32
SessionStorageRequest.r.d @ shellplusg2m_73d3a900.js:29
O365SuiteServiceProxy.RequestExecutor.internalOnMessage @ shellplusg2m_73d3a900.js:29
shellplusg2m_73d3a900.js:29 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://portal.office.com') does not match the recipient window's origin ('null').

can you open a support ticket ?

I am going to get the go ahead to turn on the Modern Experience at the tenant soon. If that doesn't fix it then I will put a ticket in.

I have this same problem and MS Support has been incredibly unhelpful. Did you get it resolved?

I'm having this same issue.  Any resolution on this?

I have a three-month-long ticket with Microsoft.

@Timothy Willis I don't know if this has been answered, but I had the same problem and there is a simple answer.  For example: If you type "624" in the "Search this Site" box  files will appear in the drop down list. Make sure you append a "*" changing to "624*" before clicking on "Show More Results". All the files in the library  with "624" in the name will then appear.