This is to report two bugs:
- On a fresh local installation, the "Take the tour" button appears but is not clickable unless the
brand is set to HEAL, so if the default brand (catalyst) is left on, you end up with a non-functional "Take the tour" button.
- On a fresh local installation, the "Take the tour" button will start working, but won't go past the first step. This appears to be because on a fresh local install, clicking on the "Take the tour" button will take you to
http://localhost:3000/, which is expected to be the search home page (i.e. showing the search bar without an active search), but on a local install this defaults to showing the support content instead.
Steps to reproduce:
- Clone from
[email protected]:helxplatform/helx-ui.git
- Run
cp .env.sample .env
- Run
set -a && source .env && bin/populate_env public/env.json
- Run
npm install
- Run
npm start
- Note that the "Take a tour" button is visible but can't be clicked in Firefox on macOS.
- Edit
public/env.json to set "brand": "heal"
- Run
npm start
- Navigate to http://localhost:3000/search
- Note that the "Take a tour" button is now colored HEAL pink, and clicking it starts the tour.
- Click on the "Take a tour" button.
- Note that the URL changes to
http://localhost:3000/ and displays the content of the HEAL Support page (see screenshot 1).
- Click "Next".
- Note that a React error appears (see screenshot 2).
Screenshot 1
Screenshot 2

This is to report two bugs:
brandis set toHEAL, so if the defaultbrand(catalyst) is left on, you end up with a non-functional "Take the tour" button.http://localhost:3000/, which is expected to be the search home page (i.e. showing the search bar without an active search), but on a local install this defaults to showing the support content instead.Steps to reproduce:
[email protected]:helxplatform/helx-ui.gitcp .env.sample .envset -a && source .env && bin/populate_env public/env.jsonnpm installnpm startpublic/env.jsonto set"brand": "heal"npm starthttp://localhost:3000/and displays the content of the HEAL Support page (see screenshot 1).Screenshot 1
Screenshot 2