Explanation of the CMS Content Engine

Created by: spiderr, Last modification: 18 Dec 2008 (03:09 UTC) by Will
Liberty Package is the heart of bitweaver's content management system. Liberty provides fundamental functionality and utility to all content built on Liberty. Liberty provides both a universal database table that all Liberty derived content is stored in, as well as a collection of features all Liberty derived content can use.

The Liberty database table stores common data such as content Title, Description, and page Data, as well as Creation and Modification dates and authors for all content. By holding all the text data for various content in one column, bitweaver achieves super fast searching, as well as simplified data storage/retrieval & text processing. But Liberty goes a step further than that.

Liberty provides a number of useful enhancements to content. Liberty is a base class that various content (blogs, wiki pages, articles, map content, etc) is built on. Through this class all content has access to Liberty's various text parsers, its image attachment utilities, its commenting utility, and the storage of historical changes (all Liberty based content automatically has a history like wiki pages traditionally do!).

Here is a conceptual image that shows how Liberty and other btiweaver packages inter-relate:

Liberty Classes

The vast majority of content created with bitweaver is derived from these classes.


LibertyBase is a foundation class for other Liberty classes and is not something generally used by those looking to build other packages on top of Liberty.


LibertyContent is our basic content class, this provides access to storage and retrieval of basic universal content properties, like title, data, history, preferences, permissions, etc.


Deprecated in R2.0.3 in favor of LibertyMime


LibertyMime builds on LibertyContent, but adds handlers for enabling files to be attached to content. File attachments can be handled in different ways. FisheyePackage for example creates a one to one relationship between a single attachment and its LibertyContent object, a Photo. WikiPages on the other hand allow multiple attachments to be associated with its LibertyContent object, a Page.


LibertyComments are derived from LibertyContent and provide comments functionality to any LibertyContent derived objects, which opt in to using comments.


@todo explain


@todo explain

Liberty Features

Liberty Feature Description Availability
Google "nofollow"comment spam protectionBitweaver 1.0+
Inline DiffUses PEAR Text_Wiki for an inline diff, instead of the line-based tool. This is particularly useful when using a WYSIWYG editor.Bitweaver 2.0+
Format Pluginstikiwiki, HTML, BBCode, MediaWiki, etc.Bitweaver 1.0+

There is also a highly flexible mechanism for attaching *any* id driven mechanism to content - this is call TikiStorage. The storage types are handled completely through Liberty storage plugins. Tutorial - Liberty Plugins

Schema Diagram

Here is a diagram of how the Tables interface (note this diagram was prior to ReleaseOne and the names have changed in ReleaseTwo, however the ideas are largely still the same):


When will the design be locked down?

by Jan Lindåker, 07 Oct 2004 (15:43 UTC)
On the bitweaver Mailing list, there has been a lot of advertizing about that the Database scheme will be locked down. This is of course important for a specific release (should perhapps go inte the release process). But from a Plugin developper standpoint this is "totally" uninteresting. The developper is only interested in if the API's are locked down or not. How will this be facilated(:question:)

Class descriptions

by hiran, 28 Dec 2006 (00:36 UTC)
Liberty seems to be powerful, yet I don't know how to make use of it.

What I'd like to read about here is the Liberty data classes (LibertyAttachable, LibertyBase, LibertyComment, LibertyStructure, LibertySystem) and when to subclass which.
  Page 1 of 1  1