Error message when navigating to /Explore page

[jamieu]

Page flashes to error message, before moving onto 'Explore' page when navigating from /search/group

Also make 'visit our Explore page to see all topic and themes' underlined in CSS

[evancp87]

@jamieu I think the issue is down to the state management setup of the search component, and clashes between client-side routing with Page.JS vs server side routing.

A similar issue is found when navigating back from the search page to the homepage, resulting in a not found page. This is due to use of sessionStorage, which adds entries to the navigation history by saving the previous path, but only starts from /search, and doesn't include the homepage route.

With the explore page, there is likely a race condition between Page.js trying to render new content on the client side, and the browser trying to navigate to the new page (/explore). Page.js attempts to load /search/explore, before the browser navigates to the correct page, as sessionStorage still contains the old path (/search), resulting in a not found page as there is not a /search/explore page.

To fix this, there will need to be a change in the state management to align with the browser's navigation state, or a way for the explore page to be better integrated into the flow, as apart from the records that the user navigates to, I don't think there's anywhere else that the user is taken away from search page.