Page Operations
Browse Space
Webskin
List all the webskins available for a specific typename. Should pick up core, plugin and project webskin for the nominated content type. Commonly associated with the displayMethod property.
| Attribute | Description | Default Value |
|---|---|---|
| ftPrefix | Prefix to filter webskin directory by; for example "display" would include all templates starting with "display". | (blank) |
| ftTypename | Specify the typename for the webskin. Typically only used in publishing rules as you would typically default to the current typename. | Defaults to current typename. |
Example from ./plugins/farcrycms/packages/types/dmnews.cfc
<cfproperty ftseq="3" ftfieldset="General Details" ftwizardStep="General Details" name="displayMethod" type="string" hint="Display method to render." required="yes" default="display" fttype="webskin" ftprefix="displayPage" ftlabel="Content Template" />
Multiple Webskins of the Same Name
Given that you can have the same content type nominated in core, plugins or your project there is the potential for conflict. If there are multiple webskins of the exact same name for a single content type, then the webskin specified last will be selected. The order of selection is core, plugin (in the order specified in farcryinit), project.
For example, if you wanted to override the webskin template in a plugin you would specifiy the exact same template name in your project:
./plugins/farcrycms/webskins/dmNews/displayPageStandard.cfm is overridden by ./projects/myproject/webskins/dmNews/displayPageStandard.cfm
Starting in version 5.1, you can also pass in bExcludeCoreViews="true" so that the webskins in farcry core are not picked up in your form tools. If you use the display* convention for your webskins, you may not want the core views in your custom type.