---
title: "Routing"
manual: "liquidlight/typo3-anthology"
version: "3.2"
permalink: "https://docs.typo3.org/permalink/liquidlight/typo3-anthology:routing@3.2"
source: "Developers/Routing.rst"
rendered: "2026-10-14T11:57:18+00:00"
---

# Routing {#routing}

To create user-friendly, human-readable URLs for the detail view of your records, you need to configure routing for the Anthology plugin.

This guide explains how to set up a route enhancer for the Anthology extension's single record view and list view pagination.

## YAML Configuration {#yaml-configuration}

Routing is configured in the main `config.yaml` file for your TYPO3 site.

Here is an example of a route enhancer for an Anthology detail page:

```yaml
routeEnhancers:
  # Single view with slug-based URLs
  [UniqueIdentifier]:
    type: Extbase
    limitToPages:
      - 123
    extension: LlAnthology
    plugin: AnthologyView
    routes:
      # Single record by slug
      - routePath: '/{record}'
        _controller: 'Anthology::single'
    defaultController: 'Anthology::view'
    aspects:
      record:
        type: PersistedAliasMapper
        tableName: tx_myextension_domain_model_item
        routeFieldName: slug
```

-   `[uniqueIdentifier]` must be replaced by a unique value; this can be anything so long as it is unique.

And a more general configuration for list view pagination:

```yaml
routeEnhancers:
  # Anthology list view - handles pagination
  AnthologyList:
    type: Extbase
    limitToPages:
      - 123
      - 456
    extension: LlAnthology
    plugin: AnthologyView
    routes:
      # List view
      - routePath: '/'
        _controller: 'Anthology::list'
      # List view with pagination
      - routePath: '/page-{page}'
        _controller: 'Anthology::list'
        _arguments:
          page: 'currentPage'
    defaultController: 'Anthology::list'
    defaults:
      page: '1'
    aspects:
      page:
        type: StaticRangeMapper
        start: '2'
        end: '1000'
```

The list view configuration can be reused across all instances of the Anthology list view as it is not dependent upon a model. Add the list view page UIDs to the `limitToPages` array.

Each single view requires a route configuration per-model as it requires the `tableName` configuration. Single view page UIDs can be added to the `limitToPages` array.

## Important Considerations {#important-considerations}

-   ****Slugs****

    For the `PersistedAliasMapper` to work, your table must have a dedicated field to store the URL slug. You are responsible for generating and saving the unique slugs for your records.

-   ****Site Configuration****

    The YAML above needs to be placed under the `routeEnhancers` key within your site's configuration.

-   ****Clearing Caches****

    After adding or changing routing configuration, you must clear the caches in the TYPO3 backend for the changes to take effect.