|Overview • Features • Configuration • FAQ • Special pages|
The Wikilog extension enhances MediaWiki with some common blogging features, making it a wiki-blog hybrid. There are many names that are used to represent this concept: wikilog, wikiblog, bliki, etc. (refer to the Bliki article on Wikipedia).
Wiki pages are configured to act as blogs, which are called "wikilogs". Just like blogs, each wikilog contains a number of published articles, with the most recent ones displayed on the wikilog main page in reverse chronological order.
One or more custom namespaces are configured as Wikilog namespaces; pages created directly in these namespaces become wikilogs, while subpages to these pages become wikilog articles (blog posts) and are listed automatically on that wikilog's main page.
The extension provides the extra functionality for wikilogs and wikilog articles. Wikilog articles inherit all the usual wiki functionality, like wiki syntax, edit history, page categories, talk pages, etc. Among the features added by the extension are: automatic listing of articles, setting of article authors, handling of article comments, generation of syndication feeds (Atom and RSS) for individual wikilogs and for all wikilogs of the wiki, etc. For more information, see the full list of features.
The philosophy of Wikilog is not to just make a blog out of a wiki, but to combine both concepts. Unlike most blogs, wikilog articles can be collaboratively written and published by multiple users. Talk pages of wikilog articles provide a simpler interface for commenting than standard MediaWiki talk pages. It is similar to most blog software, with the addition of discussion threading.
In order to use Wikilog, the following components are required:
- MediaWiki 1.19 or higher.
- A MySQL or PostgreSQL database backend.
The following components are recommended:
- Download the extension and install it as
./extensions/Wikilog, relative to your MediaWiki installation directory. You may download the tarball from GitHub or clone using Git.
- Warning: Use the github download to get the most current version. The other download link points to old versions.
- Note: The directory name must either have that name, or
$wgWikilogStylePathmust be set to the proper path in order for the extension to reference stylesheets and images from the extension directory.
100, with the first even-numbered namespace greater than or equal to 100 available in your wiki):
require_once( 'extensions/Wikilog/Wikilog.php' ); Wikilog::setupBlogNamespace( 100 );
- Note: This script needs to be executed every time the extension (or MediaWiki) is upgraded.
WARNING: User documentation is slightly outdated, it was written for the original Juliano's version. Send pull requests on github if you want to make it actual :)
User documentation is included in the extension package in the
documentation directory. The documentation is released under a Creative Commons license, and can be imported to the wiki, so that users may access it directly from the wiki. Currently the documentation is available only in English.
You must run the
./extensions/Wikilog/maintenance/wikilogImportDocumentation.php PHP script from a command-line shell in order to import the documentation to your wiki. Example:
$ cd /path/to/mediawiki $ php extensions/Wikilog/maintenance/wikilogImportDocumentation.php
This will import the documentation pages and images to your wiki, and it can be accessed from
The documentation is maintained online; you are welcome to contribute!
Examples of use
Older version (Juliano's):
- Elena & Fabrice's Blogs
- I ask questions - Blog: Observations (since March 2009)
- pika - Blog: Recipes
- Create a Blog:My_blog_name page, with any introductory text for your blog
(if you used another namespace above instead Blog: use that one)
- On your blog front page you will see a new "wikilog" tab to start interacting with
- There you can find the field: "Create new wikilog article" (see 1st picture below)
- Create with that a post on your blog (see 2nd + 3rd picture)
(don't forget to sign (--~~~~), otherwise it will not be published and stays as draft)
Note: It is strongly advised to refer to the detailed documentation too.