SOLVED

Go to classic results page link points to wrong URL and fails in GCC

%3CLINGO-SUB%20id%3D%22lingo-sub-859491%22%20slang%3D%22en-US%22%3EGo%20to%20classic%20results%20page%20link%20points%20to%20wrong%20URL%20and%20fails%20in%20GCC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-859491%22%20slang%3D%22en-US%22%3EThe%20%22Go%20to%20classic%20results%20page.%22%20link%20at%20the%20bottom%20of%20the%20Modern%20search%20results%20page%20points%20to%20TENANT.sharepoint.com%2Fsearch%2Fresults.aspx%3Fk%3Dxyz.%20It%20is%20missing%20%2Fpages%2F.%20Should%20be%20TENANT.sharepoint.com%2Fsearch%2Fpages%2Fresults.aspx%3Fk%3Dxyz.%20I%20also%20tried%20on%202%20different%20enterprise%20tenants.%20One%20of%20them%20has%20the%20same%20issue.%20The%20other%20points%20to%20%2F_layouts%2F15%2Fosssearchresults.aspx%3Fk%3Dxyz%20and%20works%20fine.%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-859491%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870334%22%20slang%3D%22en-US%22%3ERe%3A%20Go%20to%20classic%20results%20page%20link%20points%20to%20wrong%20URL%20and%20fails%20in%20GCC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870334%22%20slang%3D%22en-US%22%3EWe're%20aware%20of%20this%20issue%20and%20work%20to%20fix%20it%20has%20been%20queued%20up.%20Cannot%20promise%20when%20it%20will%20be%20fixed%20in%20production%2C%20but%20it%20will%20happen%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870336%22%20slang%3D%22en-US%22%3ERe%3A%20Go%20to%20classic%20results%20page%20link%20points%20to%20wrong%20URL%20and%20fails%20in%20GCC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870336%22%20slang%3D%22en-US%22%3EThanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1127198%22%20slang%3D%22en-US%22%3ERe%3A%20Go%20to%20classic%20results%20page%20link%20points%20to%20wrong%20URL%20and%20fails%20in%20GCC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1127198%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F410476%22%20target%3D%22_blank%22%3E%40ErkanCh%3C%2FA%3E%26nbsp%3BI%20see%20that%20%2Fpages%2F%20is%20fixed%20but%20in%20tenants%20not%20using%20the%20English%20language%20%22pages%22%20translates%20to%20something%20different.%20This%20is%20the%20case%20for%20us.%20The%20library%20%22pages%22%20does%20not%20exist%20but%20the%20%22Go%20to%20classic%20results%20page%22%20link%20still%20points%20to%20this.%20I've%20sent%20feedback%20to%20Microsoft%20asking%20to%20investigate%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor
The "Go to classic results page." link at the bottom of the Modern search results page points to TENANT.sharepoint.com/search/results.aspx?k=xyz. It is missing /pages/. Should be TENANT.sharepoint.com/search/pages/results.aspx?k=xyz. I also tried on 2 different enterprise tenants. One of them has the same issue. The other points to /_layouts/15/osssearchresults.aspx?k=xyz and works fine.
3 Replies
best response confirmed by ErkanCh (Occasional Contributor)
Solution
We're aware of this issue and work to fix it has been queued up. Cannot promise when it will be fixed in production, but it will happen :)

@ErkanCh I see that /pages/ is fixed but in tenants not using the English language "pages" translates to something different. This is the case for us. The library "pages" does not exist but the "Go to classic results page" link still points to this. I've sent feedback to Microsoft asking to investigate this.