Site set 

The extension ships one site set. Its label is Profiles, its identifier is sbuerk/modern-extbase-frontend-edit — the composer package name, which is the convention for a set identifier — and it is defined in Configuration/Sets/Profiles/config.yaml.

The set does two things: it declares the five settings of the plugins, so they become editable in the backend, and it maps those settings onto the Extbase plugin configuration in its setup.typoscript. It declares no rendering definitions and no templates.

Adding the set to a site 

In the site configuration 

This is the way for a site without a site package. Add the set identifier to the site's dependencies:

config/sites/<identifier>/config.yaml 
base: https://example.com
dependencies:
  - sbuerk/modern-extbase-frontend-edit
Copied!

In a site package 

If the installation has a site package with a site set of its own, let that set depend on this one instead. The site then only names the site package's set:

EXT:my_site_package/Configuration/Sets/MySet/config.yaml 
name: myvendor/my-site-package
label: My site package
dependencies:
  - sbuerk/modern-extbase-frontend-edit
Copied!

Editing the settings 

Once the set is part of a site, its settings appear in the settings editor of that site, grouped under the category Profiles.

  • On TYPO3 v13 the editor is the module Site Management > Settings.
  • On TYPO3 v14 the backend modules were renamed and restructured (issue #107628): the top level module is called Sites, the former Settings module was merged into Sites > Setup, and the settings are edited from the site itself.

Saving writes the values to config/sites/<identifier>/settings.yaml, so they can equally be written there by hand:

config/sites/<identifier>/settings.yaml 
modernextbasefrontendedit:
  persistence:
    storagePid: '42'
  showPageUid: 43
  editPageUid: 44
Copied!

The two page settings are declared as type: page and are offered with a page picker in the editor. The storage page is declared as type: string on purpose: it accepts a comma separated list of page uids, which a page picker could not express.

Every key, its default and its meaning is listed in Settings.

The set is optional 

A site that does not use the set is fully supported. The classic TypoScript constants that ext_localconf.php registers ship alongside the set and carry exactly the same defaults, so nothing is missing without it — see TypoScript.

Where the set is used, the order is settled and not accidental: the classic defaults are also registered in the siteSets scope, which TYPO3 includes before the sets of a site. The set's setup.typoscript is therefore layered on top and its values win.