History of LibertyAttachments
Version 2 | Current version | |
---|---|---|
Technical OverviewLibertyAttachments 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 gallery2), or even links to other websites such as 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): FeaturesAjax AttachmentsAjax Attachments lets you upload files without refreshing the whole form. When you enabled Enforce Content Status you can even upload files when you are first creating a new content item.For DevelopersAjax Attachments Process TreesThese two sketches show the basics of how the various ajax attachment templates are called and what key javascript and form elements they contain that make up the entire process. This is handy for debugging or modifying the code.Starting at inclusion of edit_storage.tpl from a content edit form
Starting at the ajax upload handler file
|