clubdirectory
Club Directory
main
en
Stefan Froemken
This document is published under the Creative Commons BY 4.0 license.
Fri, 06 Feb 2026 13:22:34 +0000
Manual covering TYPO3 extension clubdirectory
Table of Contents
With clubdirectory you can manage, list and show all clubs of your town. Further we have added a form for your FE users to register their new club or edit them.
Target group: Editors
Insert PluginPlugin select Clubs from selectbox.You can decide to show A-Z links above or not.
You can decide to prepend an All-link to A-Z links or not.
Sometimes it makes sense to reduce list of club entries to a given category.
ClubCategories you can relate club entry to a category. That way you can show only club records of
a defined category in plugin, if you want.If your TYPO3 installation works in composer mode, please execute following command:
composer req jweiland/clubdirectory
vendor/bin/typo3 extension:setup --extension=clubdirectoryIf you work with DDEV please execute this command:
ddev composer req jweiland/clubdirectory
ddev exec vendor/bin/typo3 extension:setup --extension=clubdirectoryOn non composer based TYPO3 installations you can install clubdirectory still
over the ExtensionManager:
Login
Login to backend of your TYPO3 installation as an administrator or system maintainer.
Open ExtensionManager
Click on Extensions from the left menu to open the ExtensionManager.
Update Extensions
Choose Get Extensions from the upper selectbox and click on
the Update now button at the upper right.
Install clubdirectory
Use the search field to find clubdirectory. Choose the clubdirectory
line from the search result and click on the cloud icon to
install clubdirectory.
This chapter describes the various configuration settings of clubdirectory.
Some general settings for clubdirectory can be configured
in Admin Tools -> Settings.
Default: 0
If you will allow for frontend users to create and edit their own club records you have to assign them a frontend usergroup and add this group UID to this property.
Default: 0
Only valid, if you have installed EXT:maps2, too.
While creating location records we catch the address and automatically create a maps2 record for you. Define a storage PID where we should store these records.
Default: 0
If you have many sys_category records with huge trees in your TYPO3 project, it may make sense to reduce the category trees in our Plugins to a parent category UID (root UID).
Default: empty (use value from INSTALL_TOOL)
With clubdirectory you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the sender, if a new record was created over the frontend.
Default: empty (use value from INSTALL_TOOL)
With clubdirectory you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the sender, if a new record was created over the frontend.
Default: empty
With clubdirectory you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add an email address of the receiver, if a new record was created over the frontend.
Default: empty
With clubdirectory you can give your website visitors the possibility to create new events. These created records will be hidden by default. Add a name of the receiver, if a new record was created over the frontend.
Tip
You must configure the extension maps2 first to run this extension correctly.
Default: Value from Constants EXT:clubdirectory/Resources/Private/Templates/
You can override our Templates with your own SitePackage extension. We prefer to change this value in TS Constants.
Default: Value from Constants EXT:clubdirectory/Resources/Private/Partials/
You can override our Partials with your own SitePackage extension. We prefer to change this value in TS Constants.
Default: Value from Constants EXT:clubdirectory/Resources/Layouts/Templates/
You can override our Layouts with your own SitePackage extension. We prefer to change this value in TS Constants.
Set this value to a Storage Folder (PID) where you have stored the records.
Example: plugin.
Default: 0
Example: plugin.
Define the page UID where the EXT:maps2 plugin is located to show an address on a map.
Default: 0
Example: plugin.
Often it is useful to move the detail view onto a separate page for design/layout reasons.
Default: 1
Example: plugin.
Merge record titles starting with numbers to 0- in glossary.
Default: 1
Example: plugin.
Prepend an additional button in front of the glossary to show all records again.
Default: 15
Example: plugin.
Reduce result of records to this value for a page
This chapter describes how to manage the extension from a superuser point of view.
With TYPO3 9 you have the possibility to configure RouteEnhancers
routeEnhancers:
ClubdirectoryGlossary2Plugin:
type: Extbase
extension: Clubdirectory
plugin: clubdirectory
routes:
-
routePath: '/first-club-page'
_controller: 'Club::list'
-
routePath: '/club-page-{page}'
_controller: 'Club::list'
_arguments:
page: '@widget_0/currentPage'
-
routePath: '/club-by-letter/{letter}'
_controller: 'Club::search'
_arguments:
letter: 'search/letter'
-
routePath: '/show/{club_title}'
_controller: 'Club::show'
_arguments:
club_title: club
requirements:
letter: '^(0-9|[a-z])$'
club_title: '^[a-zA-Z0-9]+\-[0-9]+$'
defaultController: 'Club::list'
aspects:
club_title:
type: PersistedAliasMapper
tableName: tx_clubdirectory_domain_model_club
routeFieldName: path_segmentIf you upgrade clubdirectory to a newer version, please read this
section carefully!
This version supports TYPO3 version 13 LTS only. Lower version support removed. Restructured ExtConf file and added SiteSet for the extension. Used Dependency Injection wherever possible. Migrate clubdirectory plugins to CTypes and added new migration wizard.
This version supports TYPO3 version 12 LTS only. Lower version support removed. All Test Cases which were based on Nimut Testing framework has been replaced with TYPO3 Testing Framework. The backend module for CSV export has been fixed for new backend module API service. All the deprecations are fixed in this version so there are no logs thrown in extension scanner.
clubdirectory allows maps2 in version 10.0.0. This version does not work
with fluid widgets anymore. That's why you also have to switch to the new
maps2 partial implementation for editPoi in your overwritten clubdirectory
templates. If you still use 9.3.1 of maps2 no template modifications are
needed.
If you have extended the controllers of clubdirectory please check, if your
implementation is still working, as we have drastically re-factored the
controllers.
TYPO3 log fills up with warnings about removed GET/POST params in PageBrowser. To solve this issue we have switched to new Paginate API of TYPO3. Please update following fluid files:
Templates/Club/List.html Partials/Club/List.html
And update the lines about PageBrowser. Use our files as an example
We have changed some method arguments, please flush cache in InstallTool
We have changed Fluid-Templates a lot. We have removed a lot of CSS classes and changed them to be compatible with Bootstrap. Further we have moved all Templates of Field directory into FormFields Template directly in to f:section. Please check your templates, if you have overwritten them.
We have remove form.objectContext VH with no replacement. Please have a look into our new templates and adopt your templates accordingly.
In case of TYPO3 9 you should execute the Slug Updater Wizard of clubdirectory in Installtool, to fill path_segments for better slugs.
As we have modified a lot of PHP classes you should clear all caches.
Currently it is not possible to separate glossary entry 0- into single
values.
If you're still using maps2 9.3 you have to override the templates and replace the new maps2 partial solution with the old maps:widget.editPoi solution
The links to issue and the GitHub repository are maintained in the Settings.cfg.
You may want to remove this file if all important links are already handled in Settings.cfg.