Routing Manager v3.1 (New)
Purpose | This section describes the Routing Manager concept within the Forrit CMS. |
Supplementary |
Overview
From v3.0 Forrit allows users to configure URL redirects and rewrites from the Routing Manager.
There are three types of routing that can be configured:
Redirect to an external site
Redirect to a page in the CMS
Set static URL for a media item
Note: The routing for a page and the structure of pages in the page tree are separate concepts. Please refer to the Page Tree concepts for more information.
This table shows the different types of redirect/rewrite that are allowed for each type:
Routing type | Permanent redirect | Temporary redirect | Rewrite |
---|---|---|---|
Redirect to an external site | Yes | Yes | No |
Redirect to a page in the CMS | Yes | Yes | Yes |
Set static URL for a media item | No | No | Yes |
Redirect to an external site
Sets up a redirect from any given internal route to an external site.
These can be edited from the Routing manager screen.
The external site must begin with “https://”.
Redirect to a page in the CMS
Sets up a redirect from any given internal route to the route of a page in the CMS.
These can be edited from the Page Settings screen.
Set static URL for a media item
Sets up a rewrite from any given internal route to the source of the image.
This allows the same URL to be used when a media item is replaced.
The static URL can be edited from the Media Library.
Routing manager in consumer app
See the user guide for how to set up the consumer app to use routing.
There are two approaches to using routing in a consumer app:
Use the SDK’s built-in routing manager. This handles all routing automatically. It assumes that all routing is defined in the CMS.
Use the SDK APIs. This is more useful if custom behaviour is required. The SDK contains APIs that allow access to all routing information released through the CMS. That information can be used however it is needed by the consumer app.
Note that choosing this option means that the consumer app must implement support for routing, static media item URLs and for the production-only page attribute - the information for these are stored in the three JSON manifests available from the SDK APIs.