You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This happened when I was working on the https://www.healthtranslations.vic.gov.au/ site and this was not working in the production environment only (lagoon) where the URL is not using the origin URL.
The baseURL that is used for this https://github.com/dpc-sdp/ripple/blob/develop/packages/ripple-nuxt-tide/lib/core/search.js#L51 is using the request header to determine the URL. This is becoming an issue on production env where the production URL healthtranslations.vic.gov.au is not reachable (it throws 404 exceptions), whereas the origin domain is reachable (in my case it is https://app.production.healthtranslations-vic-gov-au.sdp3.sdp.vic.gov.au/)
Describe the bug
This happened when I was working on the https://www.healthtranslations.vic.gov.au/ site and this was not working in the production environment only (lagoon) where the URL is not using the origin URL.
The
baseURL
that is used for thishttps://github.com/dpc-sdp/ripple/blob/develop/packages/ripple-nuxt-tide/lib/core/search.js#L51
is using the request header to determine the URL. This is becoming an issue on production env where the production URL healthtranslations.vic.gov.au is not reachable (it throws 404 exceptions), whereas the origin domain is reachable (in my case it is https://app.production.healthtranslations-vic-gov-au.sdp3.sdp.vic.gov.au/)The code to set the
baseURL
is here, https://github.com/dpc-sdp/ripple/blob/develop/packages/ripple-nuxt-tide/lib/templates/plugin.js#L25I did a patch for this specific patch to fix the issue, by adding this code to the https://github.com/dpc-sdp/ripple/blob/develop/packages/ripple-nuxt-tide/lib/templates/plugin.js
within this condition block
and I added an environment variable to record the origin URL of production.
To Reproduce
Steps to reproduce the behavior:
Or without disabling JS, you can
view source
the pageExpected behavior
Without JS enabled, there should hundreds of result in there.
Actual behavior
At the moment it returns a standard no result message
The text was updated successfully, but these errors were encountered: