[dokuwiki] Re: Farm support for plugin manager

  • From: sf-dev <sf-dev@xxxxxxxxxxxxx>
  • To: dokuwiki@xxxxxxxxxxxxx
  • Date: Thu, 16 Jun 2011 16:46:33 +0200

On 06/14/2011 11:09 PM, Christopher Smith wrote:
> On 14 Jun 2011, at 20:24, Michael Hamann wrote:
>> What about simply using the existing configuration files and just add a
>> enabled/disabled boolean setting for each plugin?
> I like this idea.

I also think this makes a lot of sense. plugins can be uninstalled and
reinstalled and the state will be kept. plugins can be packaged with
default off ...

Maybe cascade can be used to
For templates I m using a getConfigPath function[1] to handle cascade
path for non overriding files. For dokuwiki templates those are css and
php include files. For plugins that might be also include files, like
templates for blogtng or default config or also the disabled file.

on pluginlist the plugin action/syntax -file and the defaultconfig are
seperatly looked up in protected, local and default path in this order.
First occurence is loaded. plugins can make use of getConfigPath for
includes to allow overwriting further down cascade.

Plugins could be installed per animal, inherited, not inherited, force
disabled (not force enabled though). Maybe a restriction like only load
files for plugins that are present in the local dir to keep the
implications more limited.

[1]  https://github.com/samfisch/dokuwiki-plugin-templateconfhelper

DokuWiki mailing list - more info at

Other related posts: