Once you have the defined a content type for your system, you can use the generic interface defined by the content management system for creating, editing and browsing items of that type. If the generic interface does not meet your requirements, you can customize part or all it to suit your needs.
The generic interface for content items includes three general types of templates, all located under /cms/modules/items:
Forms for all item-related transactions.
Information pages for displaying information about the items. The page templates themselves may display little or no information directly, instead relying on included components.
Information components for providing access to specific types information (and associated actions) in the information page. Components are designed for inclusion in a page (either the generic information page or a custom one), not for standalone display.
The following generic data entry forms are generated by the system for any content type:
| Page | Description |
|---|---|
| create-1 | Form to enter attributes for a new content item. The widgets
displayed on the generic form are determined by the form metadata
the developer has associated with attributes of the content type.
Includes a radio selection allowing the user to pick a method for
adding the body of the content item.
|
| content-add-1 | Form to upload or enter the body of a content item. Displays
either a file upload widget or text area depending on user
selection
|
| revision-add-1 | Form to edit attributes of an existing content item. The
widgets displayed on the generic form are determined by the form
metadata the developer has associated with attributes of the
content type. Includes a radio selection allowing the user to pick
a method for editing the body of the content item.
|
| attributes-edit | Form to edit the attributes of an existing content item. Copies
the content from the latest revision to the new revision.
|
If a custom form is required, you may define it in /cms/modules/items/custom/<content_type>/ with the same name as specified above. If a custom implementation of the form exists, the system will redirect to it. Once the user has been redirected to your custom form, you may choose to implement any page flow desired before ultimately redirecting to the item information page.
See also the documentation on auto-generated forms.
| Component | Description |
|---|---|
| children | List of links to child items of the current item. Includes a select widget to add a new child item of an appropriate type. |
| templates | Lists templates currently associated with this item by user context. Includes a link to register-template to change template assignments. |
| permissions | Lists permissions currently associated with this item. Includes a link to permission-add to add a new permission record. |
| related-links | Lists offsite links related to this item. Includes a link to add marked offsite links (from anywhere in the Bookmarks tree) to the list. |
| related-items | Lists other items related to this item. Includes a link to add marked links (from anywhere in the Site Map tree) to the list. |
| workflow |
|
| keywords | Lists subject headings assigned to the content item. Includes a link to add marked subject headings (from anywhere in the Subject Headings tree) to the list. |
| revisions | Lists the n most recent revisions to the item. Includes controls to change the sort order and number of revisions to be displayed, as well as links to view a revision in context. |
| journal | Lists all comments made on the item to date. |
| wizards | List of special tasks associated with a content item (defined by a custom component under custom/<content_type>/wizards). |
Any of these components may be incorporated into a custom information page using the include tag in the page template:
<include src="../../workflow" item_id=@item_id@>
Note that item_id is the only parameter required by the standard information components.
Last revised: $Id: custom-interface.html,v 1.1 2001/04/20 20:51:09 donb Exp $