Route enhancers 

What the files enhance 

Detail.yaml

Enhancer ProfileDetailPlugin for the plugin Detail , argument namespace tx_academicpersons_detail . One route, /{profile_name} , for the detail action, mapping the argument profile . The path segment is resolved by a PersistedAliasMapper on the table tx_academicpersons_domain_model_profile over the field slug .

List.yaml

Enhancer ProfileListPlugin for the plugin List , argument namespace tx_academicpersons_list . Two routes for the list action: {localized_page}-{page} for demand/currentPage and /{letter} for demand/alphabetFilter . The page number is limited to a StaticRangeMapper from 1 to 1000, the letter to a StaticRangeMapper from a to z, and the word in front of the page number is translated by a LocaleModifier — page by default, seite for German.

ListAndDetail.yaml

Enhancer ProfileListAndDetailPlugin for the plugin ListAndDetail , argument namespace tx_academicpersons_listanddetail . It is the union of the two above: the detail route, the pagination route and the letter route, with the same aspects, because that plugin renders both the list and the detail view.

Which file to import 

The three enhancers are bound to three different plugins, so they never collide and importing more than one is normal:

• A site that puts the List plugin on one page and the Detail plugin on another — the usual setup, where the list links to the detail page through the plugin setting detailPid — imports List.yaml and Detail.yaml.
• A site that puts the single ListAndDetail plugin on one page imports ListAndDetail.yaml only.
• A site that uses both variants imports all three.

The remaining plugins of this extension — SelectedProfiles , SelectedContracts and Card — take no frontend arguments, so no enhancer is shipped for them.

Importing into a site configuration 

Add the resources to the imports of the site:

imports:
  - resource: 'EXT:academic_persons/Configuration/Routes/List.yaml'
  - resource: 'EXT:academic_persons/Configuration/Routes/Detail.yaml'
  - resource: 'EXT:academic_persons/Configuration/Routes/ListAndDetail.yaml'

What the URLs look like 

Assuming the list plugin sits on a page with the slug /persons and the detail plugin on /persons/profile, the URLs change as follows.

/persons?tx_academicpersons_list%5Bdemand%5D%5BcurrentPage%5D=2
/persons?tx_academicpersons_list%5Bdemand%5D%5BalphabetFilter%5D=m
/persons/profile?tx_academicpersons_detail%5Bprofile%5D=42

/persons/page-2
/persons/m
/persons/profile/jane-doe

Caveats 

• The detail route needs a slug. PersistedAliasMapper resolves the path segment against the slug field of the profile record, so a profile whose slug is empty cannot be reached through the enhanced URL. The slug is generated by the TCA slug field, which means it is filled when the record is saved in the backend. Profiles created by academicpersons:createprofiles are persisted through the Extbase persistence manager and therefore never pass the DataHandler , so those records — and records that predate the field — start out with an empty slug and have to be saved once in the backend before the enhanced URL resolves.
• The two list routes are alternatives, not a combination. A link that carries a page number and a letter matches the pagination route, and the letter stays behind as a query argument — /persons/page-2?tx_academicpersons_list[demand][alphabetFilter]=m.
• Only the mapped value ranges are put into the path. A page number above 1000, and the empty filter value that the A-Z reset link of the alphabet pagination submits, are outside the mapped ranges, so those links keep their query argument.
• The localeMap of the LocaleModifier is matched against the locale of the site language, with the underscores replaced by hyphens and anchored at the start. The shipped map lists en_EN.* and de_DE.* , which means a German language configured as de-DE is translated to seite while a plain de is not. Adjust the map to the locales your site actually uses.
• Unlike the program list of academic_programs, the pagination and the alphabet filter of this extension are rendered as links, not as a form, so their own requests do carry the arguments in the URL and are enhanced.