steerCMSCorePlugin
This plugin is a quite complex, and being only a very early documentation entry, only a very simple overview will be provided. It's used for managing general content and files, as well as implementing a hierarchal storage system and publishing workflow. It should also be noted that it is the most likely candidate for large change between this version and the next. But on with some details...
Core Models
First, it should be noted that everything used in steerCMSCorePlugin, starts as a steerCMSCoreNode. There a five types of steerCMSCoreNode used by this plugin:
- system_folder: base ontainer for file system items.
- site_folder: base container for CMS virtual items.
- folder: container.
- cms_page: a virtual page item.
- cms_link: a virtual link item.
- file_resource: a real life file.
All steerCMSCoreNodes carry a status:
- new: brand new item - never been published.
- edited: has been published, but also carries unpublished changes.
- delete: has been marked for deletion - still available in a published state.
- published: has been published and is up-to-date in the public state.
Extended Features
By default, base steerCMSCorePlugin is extended by the following plugins:
- Search by steerCMSSearchPlugin - from which columns title and body are scanned.
- Cache Contracts by steerCMSCachedBehaviorPlugin
- Properties by steerCMSPropertiesBehaviorPlugin
- Versioning by sfPropelVersionableBehaviorPlugin
Modules
Three modules make up this plugin: steerCMSCoreNode, steerCMSCoreNodeQueue and steerCMSCoreFrontend.
