There are changes between 3.1 and 3.2 for example that generally require some tweaking of the skin and theme. Essentially what we do is look at the diff between our customized 3.x portal and then apply those changes to our new 3.y portal. It is a little work but generally a good idea because then you can really take advantage of new features in the themes and skins that would not work if you just whole-sale copied your old files over.
-Eric On 12/20/10 4:21 PM, Jerry Shipman wrote:
Hello, I am fairly new to uPortal - I apologize if this is too dumb of a question. I've been working on a custom "theme" and "skin". We started by taking the "universality" theme and I think the "ivy" skin, and making changes from there. My question is as we upgrade through minor revisions in uPortal (3.2.x), will I have to edit the theme and skin at all? If so, how will I be able to figure out what I have to change? We've avoided changing any skin javascript, which I think will help a lot. I've just been changing theme XSL files, and skin CSS files. (and a few peripheral things like skinList.xml.) For a bonus round, how much would I have to worry about upgrades that aren't classed as minor (e.g. from 3.2.x to 3.3.x)? I did notice that from 3.2.1 to 3.2.2 there was a change in the javascript for the skin (related to "channelID" changing from a string to an integer in some "preferences"-related ajax call). So, I am a little worried because of that. But, maybe changes to the javascript are more common than changes to the XSL or CSS? Thank you, Jerry
smime.p7s
Description: S/MIME Cryptographic Signature
