New skins cause metacat to fail if all configuration files do not exist
When a skin is added to the code and to the skins list in metacat.properties, it will cause metacat to fail at startup if the configuration files are not exactly right.
It should throw an error message and bypass the skin, and allow metacat to start up.
Updated by Michael Daigle about 14 years ago
Changed SkinsAdmin to allow Metacat to start up even if certain skins are in metacat.properties but not structured correctly in the skins directory.
Metacat will only allow for configuration of skins that are structured correctly.
Updated by Redmine Admin about 10 years ago
Original Bugzilla ID was 3752