Hi,
Is there a way to fit this need now or is it a new feature?
This would be a great feaure indeed.
For now, on my farm (of the so called
htaccess kind), animal admins can configure almost everything but not the extensions. I slightly patched dokuwiki (Don't know if this is the best way to do it, but it works.)
1) In inc/preload.php,
* define constant DOKU_ANIMAL
* optionnaly add a protected file to the config cascade.
at the end of inc/preload.php :
if(isset($_REQUEST['animal'])) define( 'DOKU_ANIMAL', $_REQUEST['animal'] );
elseif('cli' == php_sapi_name() && isset($_SERVER['animal'])) define('DOKU_ANIMAL', $_SERVER['animal']);
if(defined('DOKU_ANIMAL')) {
$config_cascade['main']['protected'][] = DOKU_INC . 'conf/animal/'.DOKU_ANIMAL.'.protected.php';
}
2) Optional, in the farmer, in conf/animal/foo.protected.php
force whatever settings animal admin of the foo wiki should not be allowed to override.
note that animal admins cannot access this file.
$conf['foobar']=true;
...
3) And finally, in lib/plugins/extension/admin.php, modify the html function so it reads
public function html() {
if(defined('DOKU_ANIMAL')) return;
//.... rest of the function unchanged
With these settings, animal admin get a blank page instead of the extension manager.