...
| Excerpt |
|---|
The FarCry Core framework takes cues from the URL to determine what content instance or content type and what view should be rendered in the browser. These variables are closely integrated with the Friendly URL engine to provide good looking URLs that can drive the frameworks output. Understanding how the URL is interpreted by the framework is an important part of FarCry development. |
| Info | ||
|---|---|---|
| ||
The behaviour of the URL interpreter varies slightly between subsequent releases of FarCry – gradually improving functionality. This documentation reflects the 5.2+ release. |
...
- This order is strict. Once a variable is matched, it and previous possibilities are not considered again.
- This includes name/value - once a "directory" defaults to the name/value option, only name/value will be checked again.
- Type and/or objectid MUST be provided, either with a predefined FU prefix, or by including them in the constructed portion.
If you are explicit about the view to be called FarCry will follow your instructions – the more you leave out the more FarCry tries to "work out' what's needed.
Aliases
To avoid using the actual names of types and webskins in the URL we have added support for an fuAlias property. This property can be added to the content type as an attribute and to a webskin with a comment variable. This value can be used in the URL instead of the file name.
...