One of the great things about working with mojoPortal is the pace at which enhancements and improvements are added to this already-excellent content management system. Joe Audette, the chief architect, is very responsive to enhancement requests, and other members of the community also contribute improvements in features and functionality.
The downside can come when the improvements or enhancements implemented in a particular release include changes in how mojoPortal handles the UI, including alterations in the skins. The included skins are always updated, and periodically, new ones added to demonstrate the increased functionality. However, if you’ve created a custom skin for yourself, or a client, it can create some moments of extreme hair-pulling, and words best not shared with polite company.
To save yourself heartache and aggravation about fixing a custom skin after an upgrade, save this link: Important Skin Changes. At every release that impacts the UI, any changes that need to be made to custom-created skins will be added here. Usually, the two files that you’ll touch are the style.config and the theme.skin files contained in your skin’s folder. Remember that you’ll want to update the skin in the /data/sites/[your site number]/[your skin name folder] to be able to see the changes live.