What does it do? 

The ext:clubmanager extension is the basis for managing clubs or associations with TYPO3.

Main features 

• Members incl. their location management via the list module, i.e. each member can be assigned several locations.
• Freely selectable categorization of members and their locations possible, e.g. as board members or certificate holders via TYPO3 categories.
• Highlighting of members by their membership type (e.g. Basic, Gold, Silver, Bronze)
• Frontend lists, respectively registers incl. extended single view
• Frontend output as member list, location list or by locations per city
• Automated frontend login generation for members (using felogin)
• Automated e-mail dispatch incl. templates for frontend login data
• Scheduler task for reminder of first frontend login
• Service for monitoring e-mails sent by the system
• Integrated 2-click solution for e.g. Google Maps and Youtube iFrames, extensible with ext:cookieman.
• Dummy member data creation for testing is possible via Upgrade Wizard Task.

The free version of "Quicko - The Clubmanager" can be extended for professional applications: Addons

Screenshots 

List of members 

Member Details 

Frontend member list 

Need Support? 

If you need private or personal support, ask one of the developers at https://quicko.software for it.

Be aware that this support may not be free of charge!

Update the database scheme 

Open your TYPO3 backend with system maintainer permissions.

In the module menu to the left navigate to Admin Tools > Maintenance, then click on Analyze database and create all.

Clear all caches 

In the same module Admin Tools > Maintenance you can also conveniently clear all caches by clicking the button Flush cache.

Enable Site Set 

This extension is configured via TYPO3 Site Sets. Static TypoScript templates are no longer supported. For details, see the TYPO3 main documentation: Site sets.

1. Open your site config: config/sites/<your-site>/config.yaml

2. Add the base set dependency:

   dependencies:
     - quicko/clubmanager

   Copied!

Read more about configuration via Site Settings (preferred) and TypoScript fallback in the Configuration section.

Further reading 

• Global extension configuration
• TypoScript, mainly configuration for the frontend
• TsConfig, configuration for the backend
• Routing for human readable URLs
• Templating customize the templates

Recommended page structure 

Create at least the following pages:

• "Home": Root page of the site, containing the start page content: Normal page.
• "Member Storage": A folder to store the members in: Folder.
• "Frontend User": A folder to store the automatic generated fe_users in: Folder.
• "Sys Categories Storage": A folder to store the TYPO3 sys categories in, which are probably needed to categorize, sort and output members or locations with different categories: Folder.

Depending on your use-case you can also make use of:

• "Member list": A list page to display all members on: Normal page.
• "Member detail": A single page to display the member detail view on: Normal page, hidden in menu.
• "Location list": A list page to display all members locations on: Normal page.
• "Location detail": A single page to display the member locations detail view on: Normal page, hidden in menu.
• "Cities list": A list page to display all cities with members on: Normal page.
• "Members per city": A list page to display the list of all members in one city on: Normal page, hidden in menu.

Your page tree could, for example look like that:

Home
├── Some page
├── ...
├── Member list
│  └── Member detail
├── Location list
│  └── Location detail
├── Cities list
│  └── Members per city
├── ...
├── Login page
│  └── Restricted content
├── Logout target page
└── Storage
   ├── Member storage
   ├── Frontend User
   ├── Sys Categories Storage
   ├── Other Storage
   └── ...

Create member records 

Before any member record can be shown in the frontend those need to be created.

1. Go to the module Web > List
2. Go to the "Member Storage" folder that you created in the first step.
3. Use the + icon in the topbar Create new record.
4. Then use the New record icon Clubmanager > Member.
5. Fill out all desired fields and click Save.

More information about this record can be found here: member record.

Create member and location categories 

Categories are not mandatory but make it easier to structure member and location records. If you want to make use of special categories for your members and their locations have a look at the category record.

Add plugins: display members in the frontend 

Plugins are used to render a defined selection of member records in the frontend.

Follow these steps to add a plugin respectively for list and detail views to a page:

Member/Location list page 

While there are own templates for different listings, creating pages with these listings is the same for all list views (Member/Location/Cities).

1. Go to module Web > Page and to the previously created page "Member list".
2. Add a new content element and select the entry, depending on your listing: Clubmanager > Member list.

3. Switch to the tab Plugin where you can define the plugins settings.

   1. The selected view is already Member list.

   2. The settings here are normally set global with the Global extension configuration and TypoScript! You can overwrite the global setting by selecting another Record Storage Page you created in the beginning of the tutorial, or use this if you don't use the global setting.

      

   3. Save the plugin.

Have a look at the frontend 

Load the "Member list". "Location list" or "Cities list" page in the frontend and you should now see the member records, location records or cities filter as output. A click on the name or the detail-button should show the record on the detail page. You want to change the way the records are displayed? Have a look at the chapter Templating

WARNING 

Run upgrade wizard 

• You must have admin rights.
• Go to Admin Tools > Upgrade.
• Click Run Upgrade Wizard
• Click on Execute in the wizard Create member placeholder data for clubmanager extension.
• Click Yes to confirm that you understand that the data of some tables will be deleted and rewritten!
• Click on Perform updates!

1000 member records with associated location and frontend user record were created. In addition, system categories were created for sorting of member and site records. The system categories will be created on the root page of your pagetree. You can transfer them afterwards to your "Sys Categories Storage".

Enable Site Sets 

1. Open your site config: config/sites/<your-site>/config.yaml

2. Add the needed dependencies:

   dependencies:
     - quicko/clubmanager
     # Optional:
     # - quicko/clubmanager-login
     # - quicko/clubmanager-cookieman

   Copied!

Configure Site Settings 

Add your project-specific values in: config/sites/<your-site>/settings.yaml

Base set quicko/clubmanager 

Login set quicko/clubmanager-login 

Use this set if you use frontend login features.

clubmanagerLogin.storagePid: 123
clubmanagerLogin.loginFormPid: 45
clubmanagerLogin.memberProfilePage: 67
clubmanagerLogin.emailFrom: 'demo@clubmanager.software'
clubmanagerLogin.emailFromName: 'Clubmanager Demo'
clubmanagerLogin.replyToEmail: 'post@quicko.software'
clubmanagerLogin.redirectPageLogout: 10
clubmanagerLogin.label.login: 'Login'
clubmanagerLogin.label.profile: 'Profil'
clubmanagerLogin.label.logout: 'Logout'

Cookieman set quicko/clubmanager-cookieman 

Use this set if you integrate ext:cookieman.

clubmanagerCookieman.contentBlockerMode: 'cookieman'
plugin.tx_cookieman.settings.theme: 'bootstrap5-modal'
clubmanagerCookieman.links.dataProtectionDeclarationPid: 10
clubmanagerCookieman.links.imprintPid: 11

The base set already keeps page.theme.cookieconsent.enable = false by default, so Bootstrap Package cookie consent stays disabled unless a project explicitly enables it again. The legacy TypoScript constants imported by the Cookieman set also enforce page.theme.cookieconsent.enable = 0 for the same reason.

Fallback behavior (legacy) 

Site Settings are preferred. For backward compatibility, existing TypoScript and extension configuration values are still used as fallback in these cases:

• clubmanagerLogin.storagePid = 0 falls back to plugin.tx_clubmanager.settings.feUsersStoragePid
• clubmanagerLogin.loginFormPid = 0 falls back to plugin.tx_clubmanager.settings.feUsersLoginPid
• clubmanagerCookieman.links.* = 0 keeps existing values from your legacy cookieman TypoScript/constants configuration

Basic 

Fe-user-login 

Mail 

General setup 

Set this in your EXT:mysitepackage/Configuration/TypoScript/setup.typoscript

page {
 includeCSS {
  theme = EXT:clubmanager/Resources/Public/Scss/Theme/Theme.scss
 }
}

General constants 

Set this in your EXT:mysitepackage/Configuration/TypoScript/constants.typoscript

Settings 

It is possible to overwrite existing Extension Configuration with these TypoScript settings.

Clubmanager member record 

Change the User TSconfig to disable not needed fields in member records for your backend editors. Use Page TSconfig to remove not needed elements in dropdown-fields or to add some and to rename field labels.

In addition, the member record has six predefined fields that you can use for your individual data.

• customfield1
• customfield2
• customfield3
• customfield4
• customfield5
• customfield6

page.TCEFORM.tx_clubmanager_domain_model_member {
    starttime.disabled = 0
    endtime.disabled = 0
    reducedRate.disabled = 0
    state.disabled = 0
    feuser.disabled = 0
    directDebit.disabled = 0
    iban.disabled = 0
    bic.disabled = 0
    account.disabled = 0
    mainLocation.disabled = 0
    subLocations.disabled = 0
    altBillingName.disabled = 0
    altBillingStreet.disabled = 0
    altBillingZip.disabled = 0
    altBillingCity.disabled = 0
    altBillingCountry.disabled = 0
    ident.disabled = 0
    title.disabled = 0
    firstname.disabled = 0
    midname.disabled = 0
    lastname.disabled = 0
    zip.disabled = 0
    street.disabled = 0
    city.disabled = 0
    country.disabled = 0
    email.disabled = 0
    altEmail.disabled = 0
    phone.disabled = 0
    company.disabled = 0
    personType.disabled = 0
    salutation.disabled = 0
    level.disabled = 0
    addAddressInfo.disabled = 0
    dateofbirth.disabled = 0
    categories.disabled = 0
}

TCEFORM {
    tx_clubmanager_domain_model_member {
        // Set this to 0 if your member categories have no subcategories.
        // 0,1 is useful when using the placeholder data.
        categories.config.treeConfig.appearance.nonSelectableLevels = 0,1

        salutation {
            removeItems =
            altLabels {
                default = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_member.salutation.default
            }
            addItems {
                divers = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_member.salutation.divers
            }
        }
        customfield1 {
            label = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_member.customfield1.default
        }
    }
}

Clubmanager location record 

Change the User TSconfig to disable not needed fields in location records for your backend editors. Use Page TSconfig to remove not needed elements in dropdown-fields or to add some and to rename field labels.

page.TCEFORM.tx_clubmanager_domain_model_location {
    salutation.disabled = 0
    title.disabled = 0
    firstname.disabled = 0
    midname.disabled = 0
    lastname.disabled = 0
    company.disabled = 0
    street.disabled = 0
    addAddressInfo.disabled = 0
    zip.disabled = 0
    city.disabled = 0
    state.disabled = 0
    country.disabled = 0
    latitude.disabled = 0
    longitude.disabled = 0
    image.disabled = 0
    info.disabled = 0
    categories.disabled = 0
    phone.disabled = 0
    mobile.disabled = 0
    fax.disabled = 0
    email.disabled = 0
    website.disabled = 0
    socialmedia.disabled = 0
    youtubeVideoUrl.disabled = 0
}

TCEFORM {
    tx_clubmanager_domain_model_location {
        salutation {
            removeItems =
            altLabels {
                default = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_location.salutation.default
            }
            addItems {
                divers = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_location.salutation.divers
            }
        }
    }
}

How to rewrite URLs with clubmanager parameters 

On setting up your page you should already have created a site configuration. You can do this in the backend module Site Managements > Sites.

Your site configuration will be stored in /config/sites/<your_identifier>/config.yaml. The following configurations have to be applied to this file.

Any URL parameters can be rewritten with the Routing Enhancers and Aspects. These are added manually in the config.yaml:

1. Add a section routeEnhancers, if one does not already exist.
2. Choose an unique identifier for your Routing Enhancer. It doesn't have to match any extension key.
3. type: For clubmanager, the Extbase Plugin Enhancer (Extbase) is used.
4. extension: the extension key, converted to UpperCamelCase.
5. plugin: the plugin name of clubmanager could be city, member or location.
6. After that you will configure individual routes and aspects depending on your use case.

routeEnhancers:
  ClubmanagerCity:
    type: Extbase
    extension: Clubmanager
    limitToPages:
      - /*YOUR PIDS HERE */
    plugin: City
    routes:
      -
        routePath: '/{city}'
        _controller: 'Cities::detail'
        _arguments:
          city: city
    aspects:
      city:
      type: SanitizeValue
      tableName: tx_clubmanager_domain_model_location
      columnName: city
  ClubmanagerMember:
    type: Extbase
    extension: Clubmanager
    limitToPages:
      - /*YOUR PIDS HERE */
    plugin: Member
    routes:
      -
        routePath: '/{ident}'
        _controller: 'Member::detail'
        _arguments:
          ident: member
    aspects:
      ident:
        type: PersistedAliasMapper
        tableName: tx_clubmanager_domain_model_member
        routeFieldName: ident
  ClubmanagerMemberList:
    type: Extbase
    extension: Clubmanager
    limitToPages:
      - /*YOUR PIDS HERE */
    plugin: MemberList
    routes:
      -
        routePath: '/page/{currentPage}'
        _controller: 'Member::list'
        _arguments:
          currentPage: currentPage
    defaultController: 'Member::list'
    defaults:
      currentPage: ''
    aspects:
      currentPage:
        type: StaticRangeMapper
        start: '1'
        end: '100'
  ClubmanagerLocation:
    type: Extbase
    extension: Clubmanager
    plugin: Location
    routes:
      -
        routePath: '/{location}'
        _controller: 'Location::detail'
        _arguments:
          location: location
    aspects:
      location:
        type: PersistedAliasMapper
        tableName: tx_clubmanager_domain_model_location
        routeFieldName: slug
  ClubmanagerLocationList:
    type: Extbase
    extension: Clubmanager
    plugin: LocationList
    routes:
      -
        routePath: '/page/{currentPage}'
        _controller: 'Location::list'
        _arguments:
          currentPage: currentPage
    defaultController: 'Location::list'
    defaults:
      currentPage: ''
    aspects:
      currentPage:
        type: StaticRangeMapper
        start: '1'
        end: '100'

routeEnhancers:
  ClubmanagerCity:
    type: Extbase
    extension: Clubmanager
    limitToPages:
      - 20
      - 21
    plugin: City
    # routes and aspects will follow here

https://www.example.com/location-list/location-detail/?tx_clubmanager_member[action]=detail&tx_clubmanager_member[controller]=Member&tx_clubmanager_member[location]=1&cHash=

https://www.example.com/location-list/location-detail/1/?cHash=

https://www.example.com/location-list/location-detail/firstname-lastname-company-city/

routeEnhancers:
  ClubmanagerLocation:
    type: Extbase
    extension: Clubmanager
    plugin: Location
    routes:
      - routePath: '/{location}'
        _controller: 'Location::detail'
        _arguments:
          location: location
    aspects:
      location:
        type: PersistedAliasMapper
        tableName: tx_clubmanager_domain_model_location
        routeFieldName: slug

Common routeEnhancer configurations 

routeEnhancers:
  ClubmanagerCity:
    type: Extbase
    extension: Clubmanager
    limitToPages:
      - 90
      - 91
    plugin: City
    routes:
      -
        routePath: '/{city}'
        _controller: 'Cities::detail'
        _arguments:
          city: city
    aspects:
      city:
        type: SanitizeValue
        tableName: tx_clubmanager_domain_model_location
        columnName: city
  ClubmanagerMember:
    type: Extbase
    extension: Clubmanager
    plugin: Member
    routes:
      -
        routePath: '/{ident}'
        _controller: 'Member::detail'
        _arguments:
          ident: location
    aspects:
      ident:
        type: PersistedAliasMapper
        tableName: tx_clubmanager_domain_model_member
        routeFieldName: ident
  ClubmanagerMemberList:
    type: Extbase
    extension: Clubmanager
    plugin: MemberList
    routes:
      -
        routePath: '/page/{currentPage}'
        _controller: 'Member::list'
        _arguments:
          currentPage: currentPage
    defaultController: 'Member::list'
    defaults:
      currentPage: ''
    aspects:
      currentPage:
        type: StaticRangeMapper
        start: '1'
        end: '100'
  ClubmanagerLocation:
    type: Extbase
    extension: Clubmanager
    plugin: Location
    routes:
      - routePath: '/{location}'
        _controller: 'Location::detail'
        _arguments:
          location: location
    aspects:
      location:
        type: PersistedAliasMapper
        tableName: tx_clubmanager_domain_model_location
        routeFieldName: slug
  ClubmanagerLocationList:
    type: Extbase
    extension: Clubmanager
    plugin: LocationList
    routes:
      -
        routePath: '/page/{currentPage}'
        _controller: 'Location::list'
        _arguments:
          currentPage: currentPage
    defaultController: 'Location::list'
    defaults:
       currentPage: ''
    aspects:
       currentPage:
        type: StaticRangeMapper
        start: '1'
        end: '100'

Mail service task 

The ext:clubmanager automatically generates e-mails for certain actions. To send them automatically, the scheduler task EMail Service (clubmanager) must be set up and triggered in short intervals if possible.

1. Go to the module System > Scheduler
2. Use the + icon in the topbar Create new task
3. Set dropdown Class to clubmanager > EMail Service (1.)
4. Set task frequency (2.) to a short interval. */1 * * * * ensures that the task is executed every minute.
5. Set Maximum number of emails per run (3.) to a number, which fits to the needs of your club. If the number of members is high, it makes sense to increase the Maximum number of emails per run.
6. After you have filled in all required fields click Save.

Member login reminder task 

The basic version of ext:clubmanager provides the scheduler Task Reminder Email (clubmanager), which can be used by which members who have never logged in to the member area before get a reminder e-mail after a predefined interval to do so.

1. Go to the module System > Scheduler
2. Use the + icon in the topbar Create new task
3. Set dropdown Class to clubmanager > Member login reminder (1.)
4. Set task frequency (2.) to the shortest possible interval. 0 7 * * 2 ensures that the task is executed every tuesday at 7am.
5. Set Days until reminder (3.) to a number of days, after which a member is to be reminded again. The lower the number of days, the higher the probability that a member will perceive the message as spam.
6. Set List of PIDs for members, comma-separated (4.) if only members from certain folders should receive a reminder email. If the field is empty, all members who have never logged in will receive an email.
7. After you have filled in all required fields click Save.

At the set time, the scheduler runs Task Reminder Email (clubmanager) and creates a new reminder email for all active(!) members who have never logged in before, a new Email Tasks Member Login Reminder. During the next automatic execution of the EMail Service scheduler task, all open Email Tasks will be processed one after the other.

Member Journal processing task 

The Member Journal uses pending entries when a change is scheduled for a future date. To apply such changes automatically, a scheduled task must process due entries regularly.

The recommended setup uses the scheduler task Execute console commands with the command:

clubmanager:journal:process

Recommended cron schedule:

0 2 * * *

Felogin: Enable Site Set 

1. Install ext:felogin
2. Open your site config: config/sites/<your-site>/config.yaml

3. Add the login set dependency:

   dependencies:
     - quicko/clubmanager
     - quicko/clubmanager-login

   Copied!

Felogin: Site settings 

Set login-related values in your site settings file: config/sites/<your-site>/settings.yaml

clubmanagerLogin.storagePid: 123
clubmanagerLogin.loginFormPid: 45
clubmanagerLogin.memberProfilePage: 67
clubmanagerLogin.label.login: 'Login'
clubmanagerLogin.label.profile: 'Profil'
clubmanagerLogin.label.logout: 'Logout'

See also Site sets reference.

Felogin pagetree 

Your page tree should look like that:

Home
├── ...
├── Login page
│  └── Restricted content
├── Logout target page
├── ...
└── Storage
   ├── ...
   ├── Frontend User
   └── ...

Create default frontend user group 

1. Go to the module Web > List
2. Move to Storage > Frontend User in your pagetree.
3. Click on + Create new record on top of the page.
4. Click on Frontend Access > Website Usergroup.
5. Fill in the Group Title and Save.

Important global configuration 

1. Configure these values in config/sites/<your-site>/settings.yaml:

   clubmanagerLogin.storagePid: 123
   clubmanagerLogin.loginFormPid: 45
   clubmanagerLogin.memberProfilePage: 67
   clubmanagerLogin.emailFrom: 'demo@clubmanager.software'
   clubmanagerLogin.emailFromName: 'Clubmanager Demo'
   clubmanagerLogin.replyToEmail: 'post@quicko.software'
   clubmanagerLogin.redirectPageLogout: 10

   Copied!
2. Go to Admin Tools > Settings > Extension Configuration.
3. Choose clubmanager and then Tab Fe-user-login.
4. Set the uid of your default fe_users group defaultFeUserGroupUid (this is still required for member to fe_user assignment).
5. Optional fallback values (used if matching site settings are 0): feUsersStoragePid, feUsersLoginPid.
6. Configure frontend login mail values and the logout target page via site settings: clubmanagerLogin.emailFrom, clubmanagerLogin.emailFromName, clubmanagerLogin.replyToEmail, clubmanagerLogin.redirectPageLogout.
7. In case you want to change it, set the lifetime of password recovery links in hours: passwordRecoveryLifeTime.

8. In tab Mail set the number of attempts for a mail delivery.

   Important

   For more information see section E-Mail Task and for automatisation scheduler task.

Felogin TypoScript 

TypoScript is optional and mainly relevant as legacy fallback / targeted override in your own sitepackage. Site settings are the preferred place for login page, mail sender and logout target configuration.

EXT:clubmanager/Configuration/TypoScript/Felogin/setup.typoscript

plugin.tx_felogin_login {
   _LOCAL_LANG.de  {
      //Change the existing localization text as you want them
}

EXT:clubmanager/Configuration/TypoScript/Felogin/constants.typoscript

styles.content.loginform {
   emailFrom = your-email@your-site.tld
   emailFromName = Your Name
   replyToEmail = no-reply@your-site.tld

   redirectPageLogout = ###UID-OF-YOUR-LOGOUT-TARGET-PAGE###

   //Login|Logout button label on every page. Change the labels if you want to.
   label {
      login = Login
      logout = Logout
   }
}

Change default core mail templates 

1. [MAIL] layoutRootPaths: EXT:core/Resources/Private/Layouts/,EXT:backend/Resources/Private/Layouts/,EXT:mysitepackage/Resources/Private/Extensions/Sysmail/Layouts/
2. [MAIL] partialRootPaths: EXT:core/Resources/Private/Partials/,EXT:backend/Resources/Private/Partials/,EXT:mysitepackage/Resources/Private/Extensions/Sysmail/Partials/
3. [MAIL] templateRootPaths: EXT:core/Resources/Private/Templates/Email/,EXT:backend/Resources/Private/Templates/Email/,EXT:mysitepackage/Resources/Private/Extensions/Sysmail/Templates/

Afterwards you can overwrite the core templates in your sitepackage and fit them to your needs!

Recommended felogin pagetree 

Your page tree for the automatisation of felogin should now look like that:

Home
├── ...
├── Login page
│  └── Restricted content
├── Logout target page
├── ...
└── Storage
   ├── ...
   ├── Frontend User
   └── ...

Default content elements 

1. In your pagetree click on Login page
2. Insert + Content some default content which is shown if members are not logged in yet.
3. Set Tab Access > Usergroup Access Rights > Hide at login.
4. Save the contentelement and create a + New one.
5. Insert a welcome message and stuff which is shown if members are successfully logged in.
6. Set Tab Access > Usergroup Access Rights > Show at any login.
7. Create new pages beneath your login page and Edit page properties.
8. See Tab Access and set Usergroup Access Rights to your felogin_usergroup you created here: Create default frontend user group.
9. At least insert + Content > Text > Text & Media to say "Logout successful" on page Logout target page.

Testing your felogin setup 

1. Go to the module Web > List
2. Go to the "Member Storage" folder that you created in Create some initial content.

3. Open a test member with Edit record and have a look at section Frontend User. Now you can (+ Create new) create a Frontend User for this member or edit an exiting one.

   

4. Set/Change Username and change the Password to some easy to remember string for testing. Then save the member data.

   Important

   If you clear the Password input field and save an E-Mail Task is generated. For automatic sending of created E-Mail Tasks you have to configure the EMail Service scheduler task as described there.

5. Load the "Login page" in the frontend and try to login.

Setup member login reminder task 

Cookieman: Enable Site Set 

1. Install ext:cookieman
2. Open your site config: config/sites/<your-site>/config.yaml

3. Add the cookieman set dependency:

   dependencies:
     - quicko/clubmanager
     - quicko/clubmanager-cookieman

   Copied!

Cookieman: Site settings 

Set cookieman-related values in: config/sites/<your-site>/settings.yaml

clubmanagerCookieman.contentBlockerMode: 'cookieman'
plugin.tx_cookieman.settings.theme: 'bootstrap5-modal'
clubmanagerCookieman.links.dataProtectionDeclarationPid: 10
clubmanagerCookieman.links.imprintPid: 11

See also Site sets reference.

If a project wants to use the Bootstrap Package cookie consent feature instead of ext:cookieman, it can override page.theme.cookieconsent.enable in its site settings.

Cookieman TypoScript (fallback / optional overrides) 

EXT:clubmanager/Configuration/TypoScript/Cookieman/setup.typoscript

plugin.tx_clubmanager.settings.contentBlockerMode = cookieman

EXT:clubmanager/Configuration/TypoScript/Cookieman/constants.typoscript

page.theme.cookieconsent.enable = 0

plugin.tx_cookieman {
   settings {
      links {
         dataProtectionDeclarationPid = ###YOUR-DATA-PROTECTION-PID###
         imprintPid = ###YOUR-IMPRINT-PID###
      }
   }
}

Breaking Changes 

The following fields are no longer editable directly:

• starttime
• endtime
• state
• level

These values are now exclusively derived from Member Journal Entries. The database field cancellation_wish has been removed.

Architectural Change: Member Journal 

Version 2.0.0 introduces the Member Journal as the single source of truth for all membership status and level changes.

Instead of directly modifying the fields state, level, starttime and endtime inside the member record, all changes are now created as journal entries. The system derives the effective membership state from these entries.

This architectural change ensures:

• Complete historical tracking of status changes
• Complete historical tracking of level changes
• Statistically correct member development over time
• Persistence of historical data even if a member record is deleted

The Member Journal forms the foundation for advanced features such as statistics, billing and frontend self-service functionality.

Field Behaviour Changes 

The following member fields are no longer editable directly in version 2.0.0. Their values are exclusively derived from Member Journal entries.

Upgrade Procedure 

Create member and location categories 

1. Go to the module Web > List
2. Go to the "Sys Categories Storage" folder that you created in the first step at Recommended page structure or alternatively use your "Member Storage".
3. Use the + icon in the topbar Create new record.

4. Then use the New record icon Content > Category.

   

5. First of all create two parent categories: Locations & Members and Save them.

6. Now you have to remember the ID's of these two categories and enter them in the Global extension configuration! The ID's can be found out by hovering the mouse pointer over the icon of the the respective category.

   

7. Now create the required member and location categories and in the field Parent set the check mark for the parent category.

Important properties for sys categories 

Add member record 

Members can be added in ext:clubmanager only in the <List module>.

Member record data 

The member record is divided into tabs:

Member Journal 

The Member Journal manages all status and level changes of a membership. It replaces the direct editing of the fields state, level, starttime and endtime.

Each change of a membership is stored as a journal entry. The current state of a member record is always derived from the processed journal entries.

The following entry types are available:

• Status Change
• Level Change

See Member Journal for a complete functional description including lifecycle rules, validations and scheduler processing.

Member Tab: Locations 

Different locations can be linked to each member. These are used for presentation in the frontend and displayed in listings. With the ext:clubmanager there is the possibility to display a listing of all locations of members as well as to offer a categorization of member locations according to the the city. See plugins for more information.

Member Tab: Bank 

The member's bank details are recorded here if the member participates in the direct debit, which is usually the standard for clubs and associations. For payment requests, or payment confirmations an alternative billing address can be created.

Member Tab: Categories 

Here, members can be additionally categorized, e.g., according to completed certifications, as members of the board of directors or membership of other bodies.

Member Tab: Additional Data 

In this tab, 6 fields are available for free assignment by default.

• customfield1
• customfield2
• customfield3
• customfield4
• customfield5
• customfield6

The designation can be changed with the following TCEFORM:

TCEFORM {
    tx_clubmanager_domain_model_member {
        customfield1 {
            label = LLL:EXT:your_sitepackage/Resources/Private/Language/locallang_db.xlf:tx_clubmanager_domain_model_member.customfield1.default
        }
    }
}

Member Tab: Access 

Frontend-Benutzer 

This relation handles the frontend-user for a member.

Locations 

Basically, Main location and Other locations have the same data structure. While there can be only one main location, many Other locations are possible. See Record > Location for more information.

Architecture Principle 

Since version 2.0.0 the Member Journal is the single source of truth for membership status and level management.

The member record itself only reflects the current effective state. All changes are stored as journal entries and processed according to defined lifecycle rules.

Core principles:

• The member record shows only the current effective state.
• The journal contains the complete historical record.
• Sorting of entries is based on entry_date.
• Effectiveness is determined by effective_date.
• Processing occurs either immediately or via scheduler.

Processing modes:

• Immediate processing if the effective date is today or in the past.
• Scheduled processing via the command clubmanager:journal:process if the effective date lies in the future.

Member Fields (Derived Behaviour) 

The following fields of the member record are derived from processed journal entries and are not edited directly.

The membership number (Membership number (ident)) is editable until the first activation. After activation it becomes read-only for editors. Administrators may modify it if required.

The frontend username is derived from the membership number and is read-only for editors.

Journal Entry Types 

Two entry types are available in the Member Journal:

• Status Change
• Level Change

Status Change 

A status change updates the effective membership status.

Allowed statuses in Base:

• active
• resting
• cancelled

Level Change 

A level change updates the effective membership level.

Fields:

Processing Logic 

Each journal entry is evaluated based on its effective_date.

Status Lifecycle and Side Effects 

Status changes may trigger additional side effects such as setting membership dates or managing the associated frontend user.

Validation Rules 

The Member Journal enforces strict validation rules to ensure data consistency and historical integrity.

Visibility Logic (Hidden Entries) 

The Hidden flag of a journal entry controls whether an entry is processed.

If a journal entry is marked as hidden:

• It is excluded from processing.
• It is excluded from statistics and billing.
• It is treated as if it did not exist for lifecycle evaluation.

The hidden flag is the official mechanism to withdraw a pending journal entry.

Permissions 

Permissions differ between administrators and editors.

Edge Cases 

The following scenarios require special attention.

Add location record 

Location data records are always linked to a member data record and can only be created and edited via the associated member record. So first open the member record with the 'List module' and switch to the tab Locations.

Location record data 

The location record is divided into the tabs:

Relations 

Location records can have relations to other records. These are described in more detail here.

Automatic password recovery email 

1. Open an existing member and open the connected Frontend User. Clear the Password Input and save the member data. Now you can see, that a new password is automatically generated.

2. What happens next is, that an "E-Mail Task" is generated which will send an E-Mail to the "Frontend Users" so he can reset the password.

   Important

   Make sure, that the Scheduler Task EMail Service scheduler task is running at short intervals

Change core mail settings 

The "ext:clubmanager" uses the TYPO3 core mail settings, which have to be changed in the LocalConfiguration.php. Therefor open Admin Tools > Settings > Configure Installation-Wide Options > Mail and adjust the following settings to your needs:

1. [MAIL] defaultMailFromAddress > your-email@your-site.tld
2. [MAIL] defaultMailFromName > Your Name
3. [MAIL] defaultMailReplyToAddress > no-reply@your-site.tld
4. [MAIL] defaultMailReplyToName > Your Name

Change clubmanager mail templates 

To override the standard ext:clubmanager mail templates with your own you can use the TypoScript constants to set the paths. Add these lines to the file EXT:mysitepackage/Configuration/TypoScript/constants.typoscript in your sitepackage. and fit the templates to your needs.

plugin.tx_clubmanager {
   mailView {
      templateRootPath = EXT:mysitepackage/Resources/Private/Extensions/Clubmanager/Templates/Email
      partialRootPath = EXT:mysitepackage/Resources/Private/Extensions/Clubmanager/Partials/Email
      layoutRootPath = EXT:mysitepackage/Resources/Private/Extensions/Clubmanager/Layouts/Email
   }
}

Email Task Record 

Email task are always generated, when emails were send out by the ext:clubmanager itself. The reason for this is to have an overview of the club's email processes and to be able to follow up in case of doubt if there were errors in the dispatch.

Email tasks are titled after the process that triggered them and could not be renamed by an editor.

List of members 

Displays an unfiltered list of all member records.

Location list 

Displays an unfiltered list of all location records.

City overview 

Displays a list of all cities with location records.

Use a site package extension 

It is recommended to always store overwritten templates in a custom TYPO3 extension. Usually this is done in a special extension called the site package.

If you do not have a site package yet you can create one manually following this Official Tutorial: Site Package.

There is also a site package generator available (Provided by Benjamin Kott).

Create a directory called EXT:mysitepackage/Resources/Private/Extensions/Clubmanager for example and create 3 directories therein called Templates, Partials and Layouts. In these directories you can store your version of the Fluid templates that you need to override.

If you want to change a template, copy the desired files to the directory in your site package. If the template is in a sub folder you have to preserve the folder structure.

For example the template:

EXT:clubmanager/Resources/Private/Templates/Location/Detail.html

would have to be copied to

EXT:mysitepackage/Resources/Private/Extensions/Clubmanager/Templates/Location/Detail.html

Since your site package extends the extension clubmanager you should require clubmanager in your composer.json:

{
   "require": {
      "quicko/clubmanager": "^2.0"
   }
}

And / or ext_emconf.php:

$EM_CONF[$_EXTKEY] = [
    // ...
    'constraints' => [
        'depends' => [
            'clubmanager' => '2.0.0-2.99.99',
        ],
        // ...
    ],
];

<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
     xmlns:cm="http://typo3.org/ns/Quicko/Clubmanager/ViewHelpers"
     xmlns:x="http://typo3.org/ns/Vendor/SomeExtension/ViewHelper"
     data-namespace-typo3-fluid="true">
...
</html>

The extension for professional use 

• Backend module for member management
• Mail journal module for mail task management
• Dynamic registration process for new members via web form
• Automated cancellation process for members
• Prioritization of members (e.g. for advertising purposes)

Payment processing made easy 

• Extension of member management with bank data
• Set up different contributions and payment frequency
• One-time admission fee possible
• Collect membership fees: Submit collection file for house bank
• Invoice dispatch via e-mail
• Invoice retrieval in personalized login area
• Search functions

Search the network, find experts 

• Benefit from better positioning depending on membership status
• Map view with markers for all member locations
• different map providers adjustable
• radius search with location detection
• Targeted search via postal code

Filter cleverly, discover diversity 

• Own, powerful SOLR search server with Java basis
• Combine facets (categories) freely
• Free text search with intelligent auto-completion
• Do not guess, but know what is wanted
• Comfortably browse results with Ajax page browser

More information is coming soon 

• Appointment scheduling
• Booking appointments for members
• More to come

More information is coming soon 

• Event Management
• Bookings with costs
• More to come

Statistics for management, board and reporting 

• Membership development over time
• Joiners and leavers by period and granularity (months, quarters, years)
• Separate visibility of currently resting and currently requested members
• User activity tracking, including total logins and total profile changes
• Evaluations by period and quarter for operational reporting
• Statistics by member categories such as status, roles or qualifications
• Marketing evaluation for the How did you find out about us field to assess which campaigns or channels are effective
• Output in backend for office teams and in frontend for authorized users, for example board members in their profile area
• Excel export of all statistics for internal reporting and presentations

The Excel export contains multiple worksheets with structured evaluations, for example by year, membership development, joiners and leavers, and further tracked key figures for detailed internal analysis.

Newsletter subscriptions for members 

• Frontend plugin Newsletter List for subscribe/unsubscribe and resend confirmation
• Integration into member management (Newsletters tab in member records)
• Dashboard integration for members (Newsletters module)
• Subscription sync based on member lifecycle: active membership, verified email and newsletter consent
• Support for mandatory and optional newsletters, including sign-in type for new members
• REST API integration (base URL + API key) for newsletter provider communication
• Optional mapping of member fields to newsletter custom fields

More information is coming soon 

• Operation possible without cookie manager
• Automated data disclosure for members
• More to come