I'm not really clear on the actual utility of this class. How would I go about echoing, for example, a config option called "site_name"?

Also is there any scope for adding in hierarchical configurations?

There is no scope for hierarchy for the configurations. Why?

__________________
VillageIdiot can have my babbies ;d

What do you mean with "scope for hierarchy for the configurations" ?
Just wondering

__________________

It just seems odd to me to have every single configuration option in a single layer. I'm not sure of VI's plans for this particular part of the project, perhaps a hierarchy simply isn't necessary. What sort of options is this intended to hold?

I think it's meant to hold site's configuration. Such as what layout(if we create more than 1 template), the site's name, how many images allowed per gallery, etc. Those kinds of options.

__________________

Tanax hit the nail on the head. The purpose is to hold configs for the script to use, users will be able to manage custom ones. So if you want the site name, it will be something like:
Never really though of that, is there any particular reason it would be necessary?

Note: I already have a file for configs that the system will not be allowed to edit in core/hard_configs.php (stuff like DB details and system admins).

__________________

Is the php code in your post above really correct? You can't know what the current value is of the site name, so how would that work if you change the site name and you hardcode a specific name into there?

__________________

What do you mean? The site name would not be a hard coded setting.

__________________

Okey, but why:
['value'] ?
Would there be any other things with the site name? Or am I missing the point?

__________________

That was going by older code, I missed his changes to that. There will be an ID and status with each config, but I may make that separate.

__________________

Ah, I see!

__________________