Jul 13 2017 05:48 PM
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.
Jul 13 2017 10:55 PM
Jul 14 2017 05:48 AM
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?
Jul 14 2017 07:57 AM
Jul 14 2017 08:34 AM
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 ?
Jul 14 2017 12:47 PM
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').
Jul 19 2017 08:59 AM
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.
Nov 03 2017 05:24 AM
I have this same problem and MS Support has been incredibly unhelpful. Did you get it resolved?
Dec 06 2017 08:27 AM
I'm having this same issue. Any resolution on this?
Dec 06 2017 10:04 AM
I have a three-month-long ticket with Microsoft.
Mar 05 2021 08:15 AM
@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.