|
|
| (One intermediate revision by one user not shown) |
| Line 5: |
Line 5: |
| | The Virtual file system cannot be normally accessed on the operating system level. There are OpenCms extensions for making it available, e.g. through an FTP service. From version 7 on, OpenCms will support WebDAV out of the box. | | The Virtual file system cannot be normally accessed on the operating system level. There are OpenCms extensions for making it available, e.g. through an FTP service. From version 7 on, OpenCms will support WebDAV out of the box. |
| | | | |
| − | '''See also''': [[Real File System]] | + | '''See also''': [[Real File System]], [[Resource |Resources]] |
| − | | + | |
| − | ==Resources==
| + | |
| − | Files and folders in the VFS are stored in the same hierarchical manner known from other file systems. They are called resources.
| + | |
| − | Each resource is associated with a resource type, the publication attribute (<em>datereleased</em>), the expiration attribute (<em>dateexpired</em>) and a set of properties.
| + | |
| − | | + | |
| − | === Resource Types ===
| + | |
| − | A resource type in OpenCms identifies a certain type of file or folder along with the special methods required to work with these files or folders.
| + | |
| − | | + | |
| − | OpenCms includes a set of default resource types. They support the most common file types such as simple text and HTML files, images, PDF, MS Word and MS Excel, and XML files. OpenCms also knows special folder types, such as image galleries and link galleries which are handled in a special way. Image galleries are automatically made available to image selection dialogs anywhere in OpenCms.
| + | |
| − | | + | |
| − | Resource types are also responsible to extract links to other resources from a resource. It is possible to add new resource types. They are configured in <tt>/WEB-INF/config/[[Opencms-vfs.xml]]</tt>.
| + | |
| − | | + | |
| − | A resource type can be associated with a set of default properties which all resources of this type share unless a resource overrides the default value.
| + | |
| − | | + | |
| − | === Resource Properties ===
| + | |
| − | A property is a named string literal value attached to the resource.
| + | |
| − | | + | |
| − | There are several standard properties with predefined semantics evaluated by OpenCms during work with the resource. Most prominent is the <em>Title</em> property which is used to display the user-defined title for a resource in the explorer. You can access property values from JSP templates via the [[cms_property|cms:property]] tag.
| + | |
| − | | + | |
| − | Resource properties are an important part of OpenCms and widely used. You can define your own properties and map elements of your XML content to properties.
| + | |
| − | | + | |
| − | The list below was taken from the class <tt>org.opencms.file.CmsPropertyDefinition</tt>. It is not complete yet.
| + | |
| − | | + | |
| − | <dl>
| + | |
| − | <dt>activemethod
| + | |
| − | <dd>the active method in the administration view
| + | |
| − | <dt>locale-available
| + | |
| − | <dd>the allowed set of locales
| + | |
| − | <dt>templateclass
| + | |
| − | <dd>control the Java class for body.
| + | |
| − | <dt>cache
| + | |
| − | <dd>controls the caching
| + | |
| − | <dt>ChannelId
| + | |
| − | <dd>probably deprecated because the concept of channels in version 5.x seems to have been dropped
| + | |
| − | <dt>content-conversion
| + | |
| − | <dd>
| + | |
| − | <dt>content-encoding
| + | |
| − | <dd>content encoding
| + | |
| − | <dt>default-file
| + | |
| − | <dd>default file in folders
| + | |
| − | <dt>Description
| + | |
| − | <dd>resource description
| + | |
| − | <dt>enable-notification
| + | |
| − | <dd>
| + | |
| − | <dt>export
| + | |
| − | <dd>boolean indicating inclusion or exclusion from static export
| + | |
| − | <dt>exportname
| + | |
| − | <dd>the resource export name, during export this name is used instead of the resource name
| + | |
| − | <dt>exportsuffix
| + | |
| − | <dd>JSP additional suffix during static export, default is "html".
| + | |
| − | <dt>folders.available
| + | |
| − | <dd>control the folders where templates or default bodies should be available
| + | |
| − | <dt>image.size
| + | |
| − | <dd>the image geometry for image resources
| + | |
| − | <dt>internal
| + | |
| − | <dd>internal use (e.g. delete)
| + | |
| − | <dt>Keywords
| + | |
| − | <dd>resource keywords
| + | |
| − | <dt>locale
| + | |
| − | <dd>
| + | |
| − | <dt>locale-default
| + | |
| − | <dd>default locale of the resource
| + | |
| − | <dt>login-form
| + | |
| − | <dd>the login form
| + | |
| − | <dt>NavImage
| + | |
| − | <dd>icons to use for display of admin tools
| + | |
| − | <dt>NavInfo
| + | |
| − | <dd>used to group related tools in the admin view
| + | |
| − | <dt>NavPos
| + | |
| − | <dd>navigation position, used to determine the order of tools in the admin view
| + | |
| − | <dt>NavText
| + | |
| − | <dd>navigation text
| + | |
| − | <dt>notification-interval
| + | |
| − | <dd>
| + | |
| − | <dt>relativeroot
| + | |
| − | <dd>relative root link substitution
| + | |
| − | <dt>restypes.available
| + | |
| − | <dd>name that defines the available resource types for the "new" dialog
| + | |
| − | <dt>category
| + | |
| − | <dd>sort search results in categories
| + | |
| − | <dt>search.extractionclass
| + | |
| − | <dd>define a bean for search content extraction
| + | |
| − | <dt>search.priority
| + | |
| − | <dd>to boost certain search results
| + | |
| − | <dt>secure
| + | |
| − | <dd>secure transmission of resources
| + | |
| − | <dt>stylesheet
| + | |
| − | <dd>stylesheet of files
| + | |
| − | <dt>template
| + | |
| − | <dd>control the template
| + | |
| − | <dt>template-elements
| + | |
| − | <dd>control the template elements
| + | |
| − | <dt>Title
| + | |
| − | <dd>resource title
| + | |
| − | <dt>visiblemethod
| + | |
| − | <dd>visible method in the administration view
| + | |
| − | <dt>
| + | |
| − | <dd>
| + | |
| − | </dl>
| + | |
OpenCms comes with its own filesystem. Most data like the dynamic pages of the OpenCms Workplace as well as websites and website templates are stored in a special filesystem, the so-called Virtual File System (or VFS in short).
The VFS is completely stored in the database. It has its own set of access functions, an own, operating-system independent permission model and it knows its own set of resource types. New custom resource types can be added without modifying the core routines of opencms.
The Virtual file system cannot be normally accessed on the operating system level. There are OpenCms extensions for making it available, e.g. through an FTP service. From version 7 on, OpenCms will support WebDAV out of the box.
