Seems that the ConfigRegistry code was not picking up on the right ontology
database object type. Added what I think is the right one and lets see
if it stops the website from warning so much.