descriptionPlugins for the Blosxom Blog Script
homepage URLhttp://blosxom.sf.net/
ownergitrepo@deb.at
last changeSun, 30 Dec 2007 21:12:44 +0000 (30 21:12 +0000)
content tags
add:
README
Blosxom Plugins README
======================

This is a collection of plugins for blosxom version 2.x. 

Installation
------------

The traditional install method is to unpack this collection 
somewhere temporary and then to copy the individual plugins you 
are interested in to your blosxom.cgi $plugin_dir directory (or
symlink on platforms that support it).

If you are using a blosxom newer than 2.0.2, you also have the
option of installing the entire collection in your $plugin_dir
directory (or another directory in your $plugin_path), and 
selecting the plugins to activate by using a blosxom.cgi 
$plugin_list file (a simple list of plugins, one per line).


Configuration
-------------

You should also check the top of the plugins you use for a 
configuration section, and configure to taste.

Configuration has traditionally involved updating any 
configuration variables within the plugin itself. In addition,
there are a couple of methods that allow you to configure 
plugins externally to the plugin itself, which simplifies
upgrades.

External configuration options:

1. If configuration variables are global/package variables, 
they can be configured outside of the plugin in 'blosxom.conf',
or in 'config' or 'prefs' files if using those plugins, using
fully-qualified variable names. For example, to configure the
'atomfeed' plugin, you might add the following variables to 
your blosxom.conf:

  $atomfeed::default_author = "author@example.com";
  $atomfeed::feed_yr = 2005;

If you want to use this configuration method you should run
the 'scripts/globalise-config-variables' script within your 
plugins directory, which will update all your plugins to be 
compatible with this method.


2. Alternatively, you can install the Blosxom::Include perl
module from CPAN, which does not require that configuration
variables are globals. It looks for per-plugin configuration 
files in your blosxom.conf directory, and includes those files
after the standard configuration section. So for example, to
configure the 'atomfeed' plugin you would create an 'atomfeed'
configuration file in your /etc/blosxom directory (or whatever)
containing your customised configuration entries from the 
plugin e.g.

  # In /etc/blosxom/atomfeed, for example
  $default_author = "author@example.com";
  $feed_yr = 2005;

If you want to use this configuration method you should run 
the 'scripts/activate-blosxom-include' script from your plugins 
directory, which will add the necessary 'use Blosxom::Include' 
instruction to the top of all your plugins.
shortlog
2007-12-30 Gavin CarrAdd georss support to atomfeed.master
2007-12-27 Gavin CarrConvert remaining gavinc plugins to %config versions.
2007-12-19 Barijaona RamaholimihasoFixed extraneous <updated>...</updated> tags for feed...
2007-12-19 Barijaona RamaholimihasoFix how the date/time of the feed is determined from...
2007-12-18 Gavin CarrAdd initial activate-blosxom-include and globalise...
2007-12-18 Gavin CarrAdd special scripts directory handling to make-dist.
2007-12-18 Gavin CarrAdd initial georss support to rss20 plugin.
2007-12-18 Gavin CarrUpdates to README and MANIFEST files.
2007-12-18 Gavin CarrUpdates to blosxom-plugins-medium.spec.
2007-12-18 Gavin CarrAdd initial geo plugin.
2007-12-17 Gavin CarrReplace atomfeed $feed_url with $path_info_full, for...
2007-12-17 Gavin CarrConvert tagcloud and uf plugins to multi-line %config...
2007-12-17 Gavin CarrConvert entries_timestamp to %config version.
2007-12-17 Gavin CarrConvert rss20 to use $path_info_full instead of $ENV...
2007-12-04 Gavin CarrAdd new gavinc plugins to MANIFEST.medium.
2007-12-04 Gavin CarrUpdate rss20 test cases.
...
heads
11 years ago master