It might be the case that you want plugin Y to run before plugin X, because of what X does with what Y is supposed to have already done. Blosxom loads plugins in filename order, so make sure the alphanumerical order of your plugin filenames reflects the order you want your plugins to run.
A common [...]
It could be that the name of the plugin (from unpacking it) contains dashes or things like that. Blosxom only loads plugins whose names contain alphanumeric or underscore characters (i.e. A-Z, 0-9, and _).
Check the filename and remove any offending characters.
Use the CGI.pm module in the plugin:
use CGI qw/:standard/;
$url = url();
$path_info = path_info()
You, unfortunately, can’t get to the #entry bit since that’s never sent to the Web server. That’s handled by the browser alone.
All installed plug-ins:
keys %blosxom::plugins
All “on” plug-ins:
grep {$blosxom::plugins{$_} > 0} keys %blosxom::plugins
And if you’re interested in the order:
print join ‘, ‘, @blosxom::plugins
The tiki plugin assumes you’ve placed Tiki.pm in a Text subdirectory of your $plugin_dir…
$plugin_dir/lib/Text/Tiki.pm
Use the config plugin and create a config.flavour (for the flavour you’d like it off) containing:
$blosxom::plugins{’smartypants’} = 0;
I’ve just written a plugin ‘submission‘ which provides Blosxom with a mechanism for accepting content POSTed to it. I wrote it initially as a mechanism for people to submit plugin information to the plugin registry, but made it a bit more generic.
The idea is that you can have Blosxom accept submitted entries and treat [...]