Site sets reference
ext: is configured via TYPO3 Site Sets and Site Settings.
This is the recommended and default approach.
See the TYPO3 main documentation for Site Sets: Site sets.
Properties
Enable Site Sets
- Open your site config:
config/sites/<your- site>/ config. yaml -
Add the needed dependencies:
dependencies: - quicko/clubmanager # Optional: # - quicko/clubmanager-login # - quicko/clubmanager-cookiemanCopied!
Configure Site Settings
Add your project-specific values in:
config/
Base set quicko/clubmanager
clubmanager.memberJournalStoragePid
-
- type
-
int
- Default
- Path
-
settings.yaml
Page/folder where new member journal entries are stored. If set to
0, entries are stored in the same folder as the member record.
Login set quicko/clubmanager-login
Use this set if you use frontend login features.
clubmanagerLogin.storagePid: 123
clubmanagerLogin.loginFormPid: 45
clubmanagerLogin.memberProfilePage: 67
clubmanagerLogin.label.login: 'Login'
clubmanagerLogin.label.profile: 'Profil'
clubmanagerLogin.label.logout: 'Logout'
Copied!
Cookieman set quicko/clubmanager-cookieman
Use this set if you integrate ext:.
clubmanagerCookieman.contentBlockerMode: 'cookieman'
plugin.tx_cookieman.settings.theme: 'bootstrap5-modal'
clubmanagerCookieman.links.dataProtectionDeclarationPid: 10
clubmanagerCookieman.links.imprintPid: 11
Copied!
Fallback behavior (legacy)
Site Settings are preferred. For backward compatibility, existing TypoScript and extension configuration values are still used as fallback in these cases:
clubmanagerfalls back toLogin. storage Pid = 0 plugin.tx_ clubmanager. settings. fe Users Storage Pid clubmanagerfalls back toLogin. login Form Pid = 0 plugin.tx_ clubmanager. settings. fe Users Login Pid styles.falls back tocontent. loginform. redirect Page Logout = 0 plugin.tx_ clubmanager. settings. default Target Logout Page clubmanagerkeeps existing values from your legacy cookieman TypoScript/constants configurationCookieman. links.* = 0