This is how BOLTconfig is designed to work: local config.php files
first (config.php, 1 hierarchical, like config.forum.php, then
skin.php in skin folder), site.config second, default value third.
To set in config.php:
$BOLTconfig['field'] = 'value';
$BOLTconfig['test']['one'] = 'value2';
Which will override In site.config
field: value
test:one: value2
And you call in a function like tis
$field = BOLTconfig('BOLTfield', 'default');
$test['one'] = BOLTconfig('BOLTtest:one', 'default2');
By "backward", I only meant you had the purpose of BOLTconfig and
BOLTdefault reversed. If my suggested fix does not work well enough
we can try other approaches, but I would prefer to avoid anything that
disrupts existing functionality. That is, it's easier to add on to
BOLTconfig than to rework all the lines of code (and plugins) that use
BOLTconfig to use something different (BOLTdefault).
Your suggestions are very much appreciated and respected. Happy to
continue working on this till we have something acceptable.
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
