|
Content with label templates in Hippo CMS (See content from all spaces)
Related Labels:
validity, schema, backend, validity-test, types, check, internationalization, picker, editor, hints, communityapps, validation, poll, tips, cforms, htmlarea, xsd, style, css,
i18n, xinha, needs-refactoring
more »
03. Developing templates
Defining a new template In order to use a new document type you need to define it. Document types are defined in a file called 'types.xml'. The location of the file depends on how you build Hippo CMS. In the earlier binary distributions of Hippo CMS ...
Other labels:
types
|
Add a poll picker to CMS templates
business logic: <! in pickers > <picker id="activePolls" class="GenericPicker"> <arg><!CDATA'/editing/dialogs/listpicker/keyvaluepairs?editor=cforms&single item=true&source=cocoon://extensions/projectspecific/activePollsAsNodelist'> </arg> </picker> <! in sources > <source id="allPolls" type="nodetree">cocoon ...
Other labels:
poll, picker, backend, communityapps
|
Adding today's date to a new document
Inserting today's date in a new document In the CMS at the location editing/sitemap.xmap you will find a matcher that provides the default content for a newly created document: <map:match pattern="templates/.xml"> <map:generate src="{model://resource@name=' '/template}"/> <map ...
Other labels:
needs-refactoring
|
Internationalizing backend templates with I18N
Defining the location of the I18N catalogue In types.xml, add an i18n child element to the resource element defining your document type. Within the i18n element, write the absolute path to the directory containing your i18n catalogue files. <resource name ...
Other labels:
backend, internationalization, i18n
|
Rich text editor
Since version 6.03.00 Hippo CMS is using Xinha http://xinha.pythonhosting.com/ as the default richtext editor. We migrated to Xinha because the development of HTMLArea stopped some time ago. Xinha http://xinha.pythonhosting.com/ brings us a more stable editor ...
Other labels:
xinha, editor, htmlarea, cforms
|
Styling backend templates with CSS
Defining the location of the CSS file in types.xml In your types.xml file, add a 'css' child element to the 'resource' element defining your document type. Within the element, write the absolute URI where the CSS file can be found (it can be on the filesystem ...
Other labels:
backend, style, css
|
Template data model
General information The datamodel consists of an XML schema defining the XML structure of the document. RelaxNG is currently not supported. Supported XML Schema elements The schema elements supported by the editor is a subset of the W3C specifications. The following elements are currently supported (xs ...
Other labels:
schema, xsd
|
Template editing tips
CForms editor support html elements in layout files since version 6.04.xx (rev. 4093). More control over the styling of your backend templates! HTML elements must be in the xhtml namespace ({{http://www.w3.org/1999/xhtml}}). An example: <layout xmlns ...
Other labels:
backend, hints, tips, validity, check, validity-test
|
Template validation
Table of contents Validating fields shown in the template. To add validation to an element you will have to add a validation block to the rule. It should contain validation directives used to validate the contents of the field represented by the rule or typerule. <rule for="/root/title ...
Other labels:
types, htmlarea, validation
|
|
|