Overview 

The ll_anthology extension creates a flexible plugin system that can display content from any TYPO3 repository in both list and single view modes. It dynamically loads repositories based on configuration and provides pagination, advanced filtering, template customisation, and routing capabilities.

Features 

• Dual Display Modes: List view with pagination and single record view
• Dynamic Repository Loading: Configurable to work with any TYPO3 repository
• Advanced Filtering System: Search, category, and date filtering with multiple display modes
• Flexible Template System: Custom template paths and template name overrides
• Pagination Support: Configurable items per page and pagination links
• SEO-Friendly: Automatic page title generation from record data
• Route Enhancement: Built-in route enhancers for clean URLs

Requirements 

• TYPO3 CMS ^13.4 || ^14.3
• PHP 8.2+
• Composer

Run the Command 

./vendor/bin/typo3 anthology:setup [site_package_path]

Replace [site_package_path] with the path to either your site package, or the extension you are modifying.

Once the command has completed, it is recommended you manually review the generated configuration for accuracy before proceeding.

Add the Generated Configuration 

If it is not already configured, you must include the generated sitemap.typoscript and [model_name].typoscript files in your site package or extension's TypoScript file:

@import './TypoScript/modules'

And also add the generated YAML configuration to your site configuration YAML:

imports:
  - resource: 'EXT:site_package/Configuration/Sites/[ModelName].yaml'

Repository Configuration 

For the extension to function, you must add the AsAnthologyRepository attribute to your model's repository.

use LiquidLight\Anthology\Attribute\AsAnthologyRepository;
use TYPO3\CMS\Extbase\Persistence\Repository;

#[AsAnthologyRepository('tx_myextension_domain_model_item')]
class ItemRepository extends Repository {
	...
}

• AsAnthologyRepository's tableName argument must be the name of your database table and TCA.

Add and Configure the Plugin 

1. Navigate to the Page module and add the Anthology content element from the Plugins tab.
2. Configure the plugin settings:

General Tab

• Mode: Choose List for the main view or Single for a detail page.
• Model name: Select your model (e.g., "My Extension Items"). This list is populated based on repositories with the AsAnthologyRepository attribute, and their corresponding TCA's title.
• Single View Page: For a List plugin, link to the page where the Single view is located.

Display Tab

• Items Per Page: Set the number of items for pagination (e.g., 10).
• Enable Pagination: Activate or deactivate the pagination.

Filters Tab

• Assign pre-configured filter records to the plugin.

Routing (for Detail Pages) 

To create user-friendly URLs for your detail pages, add a route enhancer to your site's config.yaml:

routeEnhancers:
  # Single view with slug-based URLs
  ItemSingle:
  type: Extbase
  limitToPages:
    - 123  # Your single view page UID
  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

This requires a slug field in your model's table.

For further information, and to add pagination route enhancers to the list view, refer to the Routing documentation.

Sitemap 

To include your detail pages in the XML sitemap, add a sitemap provider to your TypoScript:

plugin.tx_seo.config.xmlSitemap.sitemaps {
	my_items {
		provider = TYPO3\CMS\Seo\XmlSitemap\RecordsXmlSitemapDataProvider
		config {
			table = tx_myextension_domain_model_item
			sortField = crdate
			lastModifiedField = tstamp
			pid = 123  # Storage page UID
			url {
				pageId = 456  # Single view page UID
				fieldToParameterMap {
					uid = tx_llanthology_anthologyview[record]
				}
				additionalGetParameters {
					tx_llanthology_anthologyview.action = single
					tx_llanthology_anthologyview.controller = Anthology
				}
			}
		}
	}
}

See the Sitemap guide for more details.

Templates 

The extension will automatically use templates from your model's extension directory. To override a template, copy it from ll_anthology/Resources/Private/ to the corresponding path in your own extension (e.g., my_extension/Resources/Private/Partials/List/Record.html) and modify it.

Add plugin to page 

1. Add the Anthology plugin to the page where you want the list view to appear via the New Page Content Wizard.

2. Configure the plugin, ensure the following minimum settings are applied:

• Display mode: List
• Model name: Select your model. If your model is not listed, ensure it has been configured correctly, see Quick Start for instructions
• Single page: Select the page where the single view plugin is located (if required)
• Record Storage Page: Select where your records are stored

3. Configure filters (if required)

• Navigate to the Filters tab, and add any required filters. Anthology comes with a set of commonly used filter types already available, see Filters for more information

Filter mode 

The filter mode determines how filters are combined, if only one filter is available, this option is irrelevant.

Match all

A record must match all the supplied filters in order to be returned, this will return fewer results, but the results returned will match the users' intent more closely. This would be useful for job vacancies for example, where a user will want to match specific criteria and exclude matches which aren't exact.

Match any

A record will be returned if it matches any of the filters. This will return more results, but their correlation to what the user requires may be lower. This would be useful for news articles where a user may want to see any records which match a keyword, or are in a given category

Display modes 

Most filters have multiple options for display modes (with the obvious exception of Keyword search):

Dropdown

Renders a select box

Checkbox

Actually a radio button, but "checkbox" makes it clearer for integrators

Link

Renders a link, this will retain previously selected filters, but it will not retain values which have been entered since the page loaded

Keyword search 

Keyword search allows users to search across multiple fields using a single search input. The available fields are configured through the filter, and any text based field configured in the record's TCA is available

It is possible to include multiple fields in the keyword search, and results will be returned if they entered keyword is found in any of them

Category 

Category filters allow users to filter records based upon the records' selected TYPO3 categories . Only one parent category should be selected per filter, if filtering across more than one category is required, another category filter should be added. Select the parent category for the filter categories, and all child categories will be included.

Date 

Date filters allow filtering based upon datetime values, as well as selecting the field to filter by, it is also possible to configure what date options are available

Relative

Will display dates relative to the current date.

The following options are available:

• 24 hours
• 7 days
• 1 month
• 3 months
• 6 months
• 1 year

This is useful for time sensitive records, for example displaying recently added job vacancies or frequently updated news.

Months

Displays options based upon available months in the records. This will be constrained to the first and last date in the range of the selected field.

This is useful for records which have a medium range time archive, for example, sporadically updated news or events

Years

Displays options based upon available years in the records. This will be constrained to the first and last date in the range of the selected field.

This is useful for records which have a large time archive, for example, infrequently updated news or events

Configuration Breakdown 

[model_identifier]

A unique key for your sitemap provider. This can be any descriptive name (e.g., my_items, news_articles, products).

provider

Uses the standard RecordsXmlSitemapDataProvider from the TYPO3 core SEO extension.

config

Contains the specific settings for the provider:

• table: The name of the table your anthology is displaying (must match your repository configuration).
• sortField: How the records should be sorted in the sitemap. crdate (creation date) is a sensible default.
• lastModifiedField: Field used to determine when the record was last modified. Usually tstamp.
• pid: The UID of the storage page where your records are stored. The provider will only select records from this page.

• url: Defines how to construct the URL for each record:

  • pageId: The UID of the page that will handle the single view (your detail page).
  • fieldToParameterMap: Maps database fields to URL parameters. Here, the uid field is mapped to the tx_llanthology_anthologyview[record] parameter.
  • additionalGetParameters: Additional parameters required for the Anthology plugin to work correctly.

Automatic Overrides (Recommended) 

A powerful feature of the Anthology extension is its ability to automatically detect and use templates from the extension that provides the data.

As described in the "Models" guide, you configure the Anthology plugin to use a repository from one of your own extensions. When you do this, the Anthology plugin will automatically add your extension's Resources/Private/ directories to its template paths.

This means you can simply copy a template file from the Anthology extension to your own extension, modify it, and it will be used automatically.

For example, to customise the display of a single record in the list view:

1. Copy the file from ll_anthology/Resources/Private/Partials/List/Record.html.
2. Paste it into the corresponding directory in your own extension: my_extension/Resources/Private/Partials/List/Record.html.
3. Clear the cache.
4. Modify the copied file to your liking.

This is the recommended approach as it keeps the templates for your model logically grouped with the model itself.

Manual TypoScript Overrides 

You can also explicitly tell the Anthology plugin where to find your templates using TypoScript:

plugin.tx_llanthology {
	settings {
		view {
			templateRootPaths.123456789 = EXT:my_site_package/Resources/Private/Templates/
			partialRootPaths.123456789 = EXT:my_site_package/Resources/Private/Partials/
			layoutRootPaths.123456789 = EXT:my_site_package/Resources/Private/Layouts/
		}
	}
}

Register the FlexForm 

To provide customisable options for your filter, you need to create a FlexForm. This is done in the TCA for the filter record. If no further configuration options are required, this is not necessary.

Configuration/TCA/Overrides/tx_anthology_domain_model_filter.php

<?php

// Add this to your extension's TCA override file
$GLOBALS['TCA']['tx_anthology_domain_model_filter']['columns']['settings']['config']['ds']['tag'] =
	'FILE:EXT:my_extension/Configuration/FlexForms/Filter/Tag.xml';

Register the Template 

Finally, ensure the template is found by placing it in your extension's Resources/Private/Partials/Filter/ directory. As explained in the Templates guide, the Anthology extension will automatically find templates in the extension that provides the model.

Configuration Options 

handler

The PHP class handling the link browser functionality. Required

label

Display name in the link browser tab. Required

table

Database table name of your model. Required

storagePid

Page ID where records are stored (0 for all pages).

hidePageTree

Hide the page tree in link browser (1 = hide, 0 = show).

scanAfter

Position of the tab in link browser.

Configuration Options 

forceLink

Force link generation even if target page doesn't exist. Default: 0

parameter

Target page ID where Anthology plugin is configured. Required

additionalParams.data

Data source for the record identifier. Default: field:uid

additionalParams.wrap

URL parameters to append. See example above.

Link Handler Tab Not Appearing 

• Check that page.tsconfig is properly loaded
• Verify the table name matches your model exactly
• Ensure the storage PID exists and contains records

Links Not Working 

• Verify the target page ID in parameter has the Anthology plugin
• Check that the repository is configured in plugin.tx_llanthology.settings.repositories
• Ensure routing is properly configured for clean URLs

No Records Showing 

• Check the storagePid configuration
• Verify records exist on the specified page
• Use storagePid = 0 to search all pages

Multiple Storage Pages 

TCEMAIN.linkHandler {
	tx_myextension_domain_model_item {
		handler = TYPO3\CMS\Backend\LinkHandler\RecordLinkHandler
		label = Items
		configuration {
			table = tx_myextension_domain_model_item
			storagePid = 10,20,30
			hidePageTree = 1
		}
		scanAfter = page
	}
}

BeforeGetRecordsEvent 

BeforeAnthologyListViewRenderEvent 

BeforeAnthologySingleViewRenderEvent 

BeforeAnthologyViewRenderEventInterface 

Both BeforeAnthologyListViewRenderEvent and BeforeAnthologySingleViewRenderEvent implement the BeforeAnthologyViewRenderEventInterface, which can also be listened for as an event in itself. This will ensure that a listener will be triggered before the rendering of both list and single views.