Well, both are good arguments to keep that behaviour out of code, and in the config file, such as:
in one file: loadplugin MyAvPlugin add_header all X-Virus-Status __MYAVPLUGINSTATUS__
in the other: loadplugin MyOtherAvPlugin add_header all X-Virus-Status __MYOTHERAVPLUGINSTATUS__
that way it's pretty clear to someone looking at the config file, that those two are going to collide; and it's pretty clear how to fix it (twiddle one of the add_header lines).
Basically, the idea is: the plugin can set whatever name for a template-tag it likes -- and the config file then dictates what the name of the header will be.
- --j.
OK, that makes conflicts obvious enough. I think the only thing missing is plugin documentation on how to add a custom template tag.
Daryl
