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.
When you create a readme or readme.html file, its contents will only be displayed when you navigate to that part of your blog:
http://www.example/food/italian/
should display any readme or readme.html dropped into
$datadir/food/italian
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
Hurrah! Piers and I are giving a talk at OSCON, where the theme this year is “Embracing and Extending Proprietary Software”. Our talk is entitled “Integrating SAP R/3 and Open Source Software“.
I think it’s going to be a lot of fun.
… is a great way to describe, as Kevin Marks did, the fusion of Hogwarts and Molesworth by Alice Dryden, who describes it thus:
Wot hapen when nigel molesworth, the curse of st custards, find himself at hoggwarts skool for WITCHCRAFT and wizzardry? Read on!
A must-read. It brings back many happy memories for me [...]