Installing Liquid Wiki Engine Project

Last modified: May 9, 2007 - 02:50

Important: Please download the current development release (HEAD). Some important changes have been applied.

Note: The 4.7 branch is no longer being developed. It contains heaps of bugs and should not be used.

  1. From a command line, download the *.tar.gz file to your "/sites/all/modules/" directory. (wget http://ftp.osuosl.org/pub/drupal/files/projects/%filename%)
  2. Expand the archive file using the tar command. (tar -xzvf %filename%)
  3. Navigate to your site's module administration page. (Typically http://www.mysite.com/?q=admin/build/modules)
  4. Enable each of the four Liquid modules according to your needs. If uncertain, enable them all.
    • Liquid Base - Allows wiki name-binding for nodes
    • Liquid Access - Allows more detailed access control
    • Liquid Wiki-Filter Framework - Will become a wiki-filter framework. However, at present it just delivers Mediawiki markup...
    • Liquid MoveRef - Move reference add-on for Liquid. Keeps track of what pages have been moved and redirect/refer to the new locations.
  5. You're now ready to begin configuring Liquid by navigating to your site's admin by module page. (Typically http://www.mysite.com/?q=admin/by-module)

Upgrading: Liquid 0.2 (5.x-0.x) is not backward compatible with Liquid 0.1 (the heavily patched 4.7.x-0.x version). Thus, upgrading can cause a nightmare of problems. One thing to note is that the wikipage module has been removed. You must therefore add a new content type (Administer -> Content management -> Content types-> Add content type) with id "wikipage" in order for your site to work. There are also other problems since the database isn't backward compatible. Be sure to uninstall the old version of liquid before upgrading to the new version. You might want to check that the install scripts doesn't remove the wiki_name and wiki_moveref tables before uninstalling. However, make sure that the wiki_access table is dropped ( if not, do it manually before reinstalling). If you have set the access level of some of your pages to "protected" or "none" these settings will have to be reset after the upgrade.

A note on upgrading: Basically, upgrading isn't supported. If you attempt to upgrade you are pretty much on your own.

 
 

Drupal is a registered trademark of Dries Buytaert.