Defining a Pretty URL template is a matter of placing one or more metadata keys between curly braces and separating them with either a dash (-), an underscore (_) or a slash (/), such as in the following example:
{FT_Version}_{Platform}/{ft:title}
Administrators can further customize Pretty URL templates in the following ways:
- Add static text.
- Use metadata prefixes.
- Define metadata requirements.
There are no restrictions as to which metadata administrators can include in a pretty URL.
- Only content with all of the metadata defined in one of the templates will have a pretty URL.
- If an administrator modifies the previously activated templates and selects Activate for all documents, this potentially breaks the pretty URLs generated prior to the modification.
- Defining rules to automatically generate pretty URLs does not override any existing pretty URLs that were previously defined by means of a control file, a source document, or a web service.
- Only use mono-valued metadata in pretty URLs as it is not possible to predict which value will be used with multi-valued metadata.
Template hierarchy
The Fluid Topics pretty URL generator tries to apply templates in the order in which they are listed in the Pretty URL administration interface. For this reason, it is recommended to place more specific templates (for example, a template with metadata restrictions) at the top of the list and less specific ones (for example, a "catch all" template) at the bottom.
Apply Templates
Selecting Activate for all documents in the Pretty URL administration interface displays a dialog asking for permission to trigger a reprocess job. Any content a user uploads while a reprocess job is underway is queued and processed after the reprocess job is complete.
Selecting Save and activate in the Pretty URL administration interface only applies the templates to future uploads. This prevents previously generated Pretty URLs from breaking.