History of LibertyAttachments
LibertyAttachments is a mechanism for attaching *any* id based mechanism to any LibertyPackage-derived content (wiki, blogs).
The liberty_attachments table is an abstraction to the actual file location. This permits one to use the local file system (liberty_files) or database binary objects (liberty_blobs), tables from other 3rd party application ( like a g_id from [http://gallery.sourceforge.net|gallery2] ), or even links to other websites such as [http://www.pbase.com|pbase]. LibertyAttachable extended objects use the public methods to have a "black box" for attaching data, and the actual location is dependent on the attachment plugin.
All functionality is in the LibertyPackage package. There is a LibertyAttachable class that handles all storing and retrieving of attachment data. Currently, there are plugins for Lulu, PBase and uploads via bit_files. Future support (blobs, gallery2, etc.) will depend on community support and developer interest.
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):
{attachment id=561 size=large href=/storage/users/2/2/images/561/tiki_content.png}
The liberty_attachments table is an abstraction to the actual file location. This permits one to use the local file system (liberty_files) or database binary objects (liberty_blobs), tables from other 3rd party application ( like a g_id from [http://gallery.sourceforge.net|gallery2] ), or even links to other websites such as [http://www.pbase.com|pbase]. LibertyAttachable extended objects use the public methods to have a "black box" for attaching data, and the actual location is dependent on the attachment plugin.
All functionality is in the LibertyPackage package. There is a LibertyAttachable class that handles all storing and retrieving of attachment data. Currently, there are plugins for Lulu, PBase and uploads via bit_files. Future support (blobs, gallery2, etc.) will depend on community support and developer interest.
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):
{attachment id=561 size=large href=/storage/users/2/2/images/561/tiki_content.png}