/ 
CGI-Wiki-0.30
River stage zero No dependents
/ CGI::Wiki

NAME

CGI::Wiki - A toolkit for building Wikis.

DESCRIPTION

Helps you develop Wikis quickly by taking care of the boring bits for you. The aim is to allow different types of backend storage and search without you having to worry about the details.

NOTE WHEN UPGRADING FROM PRE-0.24 VERSIONS

There was a small interface change to list_recent_changes between versions 0.23 and 0.24 - see the 'Changes' file for details.

IMPORTANT NOTE WHEN UPGRADING FROM PRE-0.20 VERSIONS

The database schema changed between versions 0.14 and 0.15, and again between versions 0.16 and 0.20 - see the 'Changes' file for details. This is really kinda important, please do check this out or your code will die when it tries to use any existing databases.

SYNOPSIS

  # Set up a wiki object with an SQLite storage backend, and an
  # inverted index/DB_File search backend.  This store/search
  # combination can be used on systems with no access to an actual
  # database server.

  my $store     = CGI::Wiki::Store::SQLite->new(
      dbname => "/home/wiki/store.db" );
  my $indexdb   = Search::InvertedIndex::DB::DB_File_SplitHash->new(
      -map_name  => "/home/wiki/indexes.db",
      -lock_mode => "EX" );
  my $search    = CGI::Wiki::Search::SII->new(
      indexdb => $indexdb );

  my $wiki      = CGI::Wiki->new( store     => $store,
                                  search    => $search );

  # Do all the CGI stuff.
  my $q      = CGI->new;
  my $action = $q->param("action");
  my $node   = $q->param("node");

  if ($action eq 'display') {
      my $raw    = $wiki->retrieve_node($node);
      my $cooked = $wiki->format($raw);
      print_page(node    => $node,
		 content => $cooked);
  } elsif ($action eq 'preview') {
      my $submitted_content = $q->param("content");
      my $preview_html      = $wiki->format($submitted_content);
      print_editform(node    => $node,
	             content => $submitted_content,
	             preview => $preview_html);
  } elsif ($action eq 'commit') {
      my $submitted_content = $q->param("content");
      my $cksum = $q->param("checksum");
      my $written = $wiki->write_node($node, $submitted_content, $cksum);
      if ($written) {
          print_success($node);
      } else {
          handle_conflict($node, $submitted_content);
      }
  }

METHODS

new
# Set up store, search and formatter objects.
my $store     = CGI::Wiki::Store::SQLite->new(
    dbname => "/home/wiki/store.db" );
my $indexdb   = Search::InvertedIndex::DB::DB_File_SplitHash->new(
    -map_name  => "/home/wiki/indexes.db",
    -lock_mode => "EX" );
my $search    = CGI::Wiki::Search::SII->new(
    indexdb => $indexdb );
my $formatter = My::HomeMade::Formatter->new;

my $wiki = CGI::Wiki->new(
    store     => $store,     # mandatory
    search    => $search,    # defaults to undef
    formatter => $formatter  # defaults to something suitable
);

store must be an object of type CGI::Wiki::Store::* and search if supplied must be of type CGI::Wiki::Search::* (though this isn't checked yet - FIXME). If formatter isn't supplied, it defaults to an object of class CGI::Wiki::Formatter::Default.

You can get a searchable Wiki up and running on a system without an actual database server by using the SQLite storage backend with the SII/DB_File search backend - cut and paste the lines above for a quick start, and see CGI::Wiki::Store::SQLite, CGI::Wiki::Search::SII, and Search::InvertedIndex::DB::DB_File_SplitHash when you want to learn the details.

formatter can be any object that behaves in the right way; this essentially means that it needs to provide a format method which takes in raw text and returns the formatted version. See CGI::Wiki::Formatter::Default for an example. Note that you can create a suitable object from a sub very quickly by using Test::MockObject like so:

my $formatter = Test::MockObject->new();
$formatter->mock( 'format', sub { my ($self, $raw) = @_;
                                  return uc( $raw );
                                } );

I'm not sure whether to put this in the module or not - it'd let you just supply a sub instead of an object as the formatter, but it feels wrong to be using a Test::* module in actual code.

write_node
my $written = $wiki->write_node($node, $content, $checksum, \%metadata);
if ($written) {
    display_node($node);
} else {
    handle_conflict();
}

Writes the specified content into the specified node in the backend storage, and indexes/reindexes the node in the search indexes, if a search is set up. Note that you can blank out a node without deleting it by passing the empty string as $content, if you want to.

If you expect the node to already exist, you must supply a checksum, and the node is write-locked until either your checksum has been proved old, or your checksum has been accepted and your change committed. If no checksum is supplied, and the node is found to already exist and be nonempty, a conflict will be raised.

The first three parameters are mandatory. The metadata hashref is optional, but if it is supplied then each of its keys must be either a scalar or a reference to an array of scalars.

(If you want to supply metadata but have no checksum (for a newly-created node), supply a checksum of undef.)

Returns 1 on success, 0 on conflict, croaks on error.

format
my $cooked = $wiki->format($raw);

Passed straight through to your chosen formatter object.

store
my $store  = $wiki->store;
my $dbname = eval { $wiki->store->dbname; }
  or warn "Not a DB backend";

Returns the storage backend object.

search_obj
my $search_obj = $wiki->search_obj;

Returns the search backend object.

formatter
my $formatter = $wiki->formatter;

Returns the formatter backend object.

Methods provided by storage backend

See the docs for your chosen storage backend to see how these work.

  • delete_node (also calls the delete_node method in the search backend, if any)

  • list_all_nodes

  • list_backlinks

  • list_nodes_by_metadata

  • list_recent_changes

  • node_exists

  • retrieve_node

  • verify_checksum

Methods provided by search backend

See the docs for your chosen search backend to see how these work.

  • search_nodes

  • supports_phrase_searches

Methods provided by formatter backend

See the docs for your chosen formatter backend to see how these work.

  • format

SEE ALSO

For a very quick Wiki startup without any of that icky programming stuff, see Max Maischein's CGI::Wiki::Simple, which uses CGI::Wiki with CGI::Application to get you up and running in one or two minutes.

CGI::Wiki allows you to use different formatting modules. Text::WikiFormat might be useful for anyone wanting to write a custom formatter. Existing formatters include:

There's currently a choice of three storage backends - all database-backed, but flat file storage coming soon, once Ingy writes CGI::Kwiki and I can steal his code :)

A search backend is optional:

Standalone plugins can also be written - currently they should only read from the backend storage, but write access guidelines are coming soon. I've only written one plugin so far:

If writing a plugin you might want an easy way to run tests for it on all possible backends:

Other ways to implement Wikis in Perl include:

AUTHOR

Kake Pugh (kake@earth.li).

COPYRIGHT

Copyright (C) 2002-2003 Kake Pugh.  All Rights Reserved.

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

FEEDBACK

Please send me mail and tell me what you think of this. It's my first CPAN module, so stuff probably sucks. Tell me what sucks, send me patches, send me tests. Or if it doesn't suck, tell me that too. I love getting mail, even if all it says is "I used your thing and I like it", or "I didn't use your thing because of X".

blair christensen, Clint Moore and Max Maischein won the beer.

CREDITS

Various London.pm types helped out with code review, encouragement, JFDI, style advice, code snippets, module recommendations, and so on; far too many to name individually, but particularly Richard Clamp, Tony Fisher, Mark Fowler, and Chris Ball.

blair christensen sent patches and gave me some good ideas. chromatic continues to patiently apply my patches to Text::WikiFormat. Paul Makepeace helped me add support for connecting to non-local databases. The grubstreet team keep me well-supplied with encouragement and bug reports.

CGI::WIKI IN ACTION!

Max Maischein has set up a CGI::Wiki-based wiki describing various file formats, at http://www.corion.net/cgi-bin/wiki.cgi

I've set up a clone of grubstreet, a usemod wiki, at http://the.earth.li/~kake/cgi-bin/cgi-wiki/wiki.cgi -- it's not yet feature complete, but it's pure CGI::Wiki, using the new CGI::Wiki::Formatter::UseMod formatter. Code is at http://the.earth.li/~kake/code/cgi-wiki-usemod-emulator/

GRATUITOUS PLUG

I'm only obsessed with Wikis because of grubstreet, the Open Community Guide to London -- http://grault.net/grubstreet/