I'm working on our vendor branch merge for 3.1 and ran into what I
consider a blocker of an issue. What has been recommended in the past
when doing local skinning work for uPortal is to create a copy of the
default uportal3 skin with a new name. When doing so I realized that the
new theme uses the skin name as part of the base CSS class name. This
means the skin name is hardcoded in the skin CSS files ... 251 times. I
realize a search and replace can be used but this seems like a
high-burden to place on deployers doing skinning. I was already talking
with folks about having the main css file named for the skin as well. It
would seem to make sense that the skin name is only part of the path and
beyond that is not used to avoid problems like this.
Is there a strong technical reason that the root CSS class name for a
skin contains the skin name? Can we find an alternate solution that
doesn't require as much work for the deployer to create a new skin?
-Eric
smime.p7s
Description: S/MIME Cryptographic Signature
