Project

General

Profile

Bug #3752

New skins cause metacat to fail if all configuration files do not exist

Added by Michael Daigle about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Immediate
Category:
metacat
Target version:
Start date:
01/14/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3752

Description

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.

History

#1 Updated by Michael Daigle about 11 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.

#2 Updated by Redmine Admin almost 7 years ago

Original Bugzilla ID was 3752

Also available in: Atom PDF