Item9255: configure Checkers need a way to be plugged into
Current State: No Action Required
Released In: n/a
Target Release: n/a
Applies To: Engine
(for example) needs a way for extensions to add to it. LdapContrib
etc all should be able to add a checker that will be used to enable/disable PasswordManager
options in the SELECTCLASS depending on prereq's such as CPAN module, DbiContrib
being installed, compatible OS/web server, random other things..
ideally, the base checker should not need to be coded explicitly for this - so that any extension can add info to any possibly existing checker - such as adding an Error to an otherwise ok setting if its incompatible with that extension..
which copmlexifies things rather alot...
perhaps we need to do the same kind of thing as in the Plugins
dir - so that there is
Foswiki::Checkers::PassordManager in the core,
- and then one of
- 03 Jul 2010
Dependencies between settings are not well handled. I started some of this with the RCS sub dir. But the idea of enabling/disabling core config bits based on installed extensions is way beyond where I have been.
Currently you can plug in checkers, pluggables, and types, but making the configure architecture any more flexible fills me with dread. It's already as complicated as it should ever get, IMHO.
Note that extensions can
add to other sections in
, by simply declaring the section header in Config.spec. For example, to add settings to 'Security and Authentication' the extension can:
---+ Security and Authentication
You could also ship a new type for configure, e.g. SELECTCLASSPLUSPLUS, with the extension.
- 04 Jul 2010
what i'm after is more complex than than (or better said, more simple for the developer of extensions)
I'll do some looking when i read your docco...
- 04 Jul 2010
Since this was reported I added the ENHANCE feature, that I think addresses the requirement, so setting to "no action".
- 25 Nov 2013