Most of the time this extra level of configurability using twiki topics isn't worth it, and just sucks performance. Once the plugin is configured, it stays that way for the lifetime of a TWiki. No need to extract this information again and again on every click: "oh lock mum, I've just found the same configuration once again" .

Best is to

• either move options to a cfg file and define a Config.spec, or even
• rethink if less isn't more, that is: remove config options all together, and
• move SHORTDESCRIPTION to perl

All this to be able to set

$NO_PREFS_IN_TOPIC = 1;

in the plugin code.

MD

What is the compatibility of this for older installations? Since when does TWiki support Config.spec?

-- TWiki:Main.ArthurClemens - 13 Nov 2007

Ou, good question. Don't know for sure, for how long we are able to have plugin settings in configure. However, you are able to have plugin settings in cfg for as long as we have LocalSite.cfg ...

-- TWiki:Main.MichaelDaum - 13 Nov 2007