Only Works from the Document Root

[jgkim]

It seems like some templates use absolute paths to resources instead of relative ones, so it makes Indivo X UI Server only work in a root-URI, not in a sub-URI. For example, if you install Indivo X UI Server to http://example.com/indivo, it won't work as you expect.

[p2]

Yes, that's correct, this is a known limitation.

[jgkim]

If there is any place I can find other known limitations, it would be great to know. :)

[p2]

I trust you already found our documentation at http://docs.indivohealth.org/ and the installation instructions on our wiki at http://wiki.chip.org/indivo/index.php/HOWTO:_install_Indivo_X. I did not find this limitation mentioned there however, I hope it's the only one not documented. There is also a mailing list, see http://indivohealth.org/developer-community for more details.

[thisisdhaas]

This seems a bit worse than a 'known limitation'--it sounds like something we should work towards fixing. @jgkim, can you be more specific about which paths break when you configure the UI to run with a prefixed path?

[jgkim]

@thisisdhaas, when I configured the UI with a sub-URI, all the images, javascripts, and stylesheets referenced with absolute paths couldn't be loaded. Also, in the case of template/ui/login.html, the action of the login form was /login so I couldn't login to the system at all. If you run a simple command line such as grep -l -r "\(href\|src\|action\)=\\?['\"]/" * | uniq, I guess you can find some suspicious files to investigate further.