Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
None
Description
I just re-checked... I have the property css.additional=grouperExternal/public/assets/css/umt_grouper_overrides.css so that's good... the html source that comes up has this ref:
<link href="grouperExternal/public/assets/css/umt_grouper_overrides.css" rel="stylesheet" type="text/css" />
... shouldn't that look like "../../grouperExternal/public/assets/css/umt...css"?
Chris Hyzer 5:01 PM
see my comment above at 3:49
New
Josh O'Dowd 5:08 PM
sorry, I didn't put that together, because grouper had auto-prefixed the "../.." on my previous URI values.
5:10
so for instance, on the image file property I did not include the "../.." but grouper prefixes it and voila! my image shows and the page source is:
src="../../grouperExternal/public/assets/images/um-logo.png"
Josh O'Dowd 5:20 PM
There we go:
image.png
image.png
5:23
so for the image file, I put the file in grouperExternal/public/assets/images and set the image.organisation-logo=grouperExternal/public/assets/images/um-logo.png
... but for the css file, in grouperExternal/public/assets/css, I had to prefix the css.addtional with '../../'
ultimately both URI refs in the page source were prefixed with '../../'
Josh O'Dowd 5:35 PM
Last part on this look-n-feel part is that in v2.4 we were overriding the property "grouperAppName" in the grouper.text.en.us.properties file. That one doesn't seem to be part of database config yet... unless I'm mistaken?