Closed mtesopt closed 3 days ago
Hi!
Had similar issue. Try using
PUBLIC_URL=/ohif/
in your build script (/platform/app/package.json) and
routerBasename: '/ohif'
in your config file (/platform/app/public/config/yourConfig.js)
hope it helps, cheers!
Describe the Bug
I’m embedding OHIF V3.7 inside a React app via an iframe. When I run the application, the iframe is empty.
Steps to Reproduce
The React app is hosted at e.g. https://www.example.com/med/study-images routerBaseName is /med/study-images/ohif and PUBLIC_URL is /med/study-images/ohif/
I'm following the documentation from https://docs.ohif.org/deployment/custom-url-access
The current behavior
The iframe is empty.
In the network panel, I see the request to ohif/ succeed with a 200 but I don’t see subsequent calls to app-config, js bundles, and assets etc…
What is the correct configuration for routerBaseName and PUBLIC_URL when app is hosted at non-root path?
The expected behavior
OHIF loads & shows the study list
OS
Windows 10
Node version
18.20.3
Browser
Chrome v126