Hello,
I apologize if this is a dumb question...
I am working on a "theme" and "skin" for uPortal 3.2. Following some of the
advice from earlier in this list, I have disabled various different kinds of
caching and am using someone's "css.directInject" and "xsl.directInject" build
targets to help me along.
However, I am now running into a problem that is related to CSS aggregation. I
think the short form of my question is: how can I get it to refresh the
'aggregated' css file (e.g.
...\media\skins\{theme}\{skin}\uportal3_4_A1EE8CC33EF9FD029156F29D9870130E.aggr.min.css
) for a given skin?
The behavior I am seeing is: when css/js aggregation is enabled, I am seeing
"old", out-of-date CSS. When I disable it, I see my current CSS. This persists
through server restarts and everything. I think that I need to get it to
rebuild the aggregated file, but I don't know how to do that. I think I tried
re-enabling the caching and restarting, but it didn't do the trick.
Any ideas? I notice that the aggregated file is named "uportal3_...", which is
not the name of my skin. Is that a hint that I have something configured
incorrectly?
Thank you very much!
Jerry
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
