I installed ExternalTiddlersPlugin and couldn't get it to work. Then I
noticed that it had this additional tag: "systemConfigDisable".
When I removed this tag, it worked fine. But I'm puzzled why its in
there. I couldn't find any mention of it in the ETP documentation. I
can see how it would be useful to turn off a plugin without deleting
it. Is that a tag that would work with all plugins?
On Jul 6, 3:13 am, "Mark S." <throa...@yahoo.com> wrote:
> I installed ExternalTiddlersPlugin and couldn't get it to work. Then I
> noticed that it had this additional tag: "systemConfigDisable".
Generally the systemConfigDisable tag is implemented through the
Manage plugins tab in backstage. It may have been saved that way by
who ever saved it last from where you got it.
> Is that a tag that would work with all plugins?
Any addition or change to the systemConfig tag will disable it.
Sometimes I temporarily disable a plugin be just adding an X to it
like e.g. systemConfigX
Morris
On Jul 6, 3:13 am, "Mark S." <throa...@yahoo.com> wrote:
> I installed ExternalTiddlersPlugin and couldn't get it to work. Then I
> noticed that it had this additional tag: "systemConfigDisable".
> When I removed this tag, it worked fine. But I'm puzzled why its in
> there. I couldn't find any mention of it in the ETP documentation. I
> can see how it would be useful to turn off a plugin without deleting
> it. Is that a tag that would work with all plugins?
> Any addition or change to the systemConfig tag will disable it.
> Sometimes I temporarily disable a plugin be just adding an X to it
> like e.g. systemConfigX
'systemConfigDisable' is a standard core-recognized tag value.
Although you can always disable a plugin by hand-editing a specific
plugin tiddler to delete or change an existing 'systemConfig' tag,
this also removes the plugin from the list shown by PluginManager.
Instead, if you *add* the special 'systemConfigDisable' tag to a
plugin tiddler (while leaving the 'systemConfig' tag intact), it
instructs the TW core's plugin loader to skip over that plugin at
startup, while still permitting you to easily enable/disable each
installed plugin as desired by using the PluginManger's "[x]disable"
checkboxes to toggle the corresponding 'systemConfigDisable' tag on
the respective plugin tiddlers.
Thanks everyone. I see how useful this tag might be, but what I'm
wondering now is, why would a plugin import with the
'systemConfigDisable' tag already in place?
|
