Member

The member record is obviously the most important record in this extension. It is used to organise the memberships of your club, association or company.

Add member record

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

Note

A TYPO3 module with extensive search function, improved view and extended options, is available with the ext:clubmanager_pro!

Member record data

The member record is divided into tabs:

Member Tab: General

Here the general data concerning the membership are recorded.

Membership

Since version 2.0.0 the membership status and level are no longer edited directly in the member record. All changes are managed via the Member Journal.

Field:	Description:
Membership number (ident)	Unique membership number. Must be set before the first activation. After activation this field is read-only for editors.
Membership status (derived)	Derived from Member Journal entries. Not editable directly.
Level (derived)	Derived from Member Journal entries. Not editable directly.
Reduced membership	Purely descriptive flag. No automatic logic in Base.
Beginning of membership (derived)	Automatically set on first activation. Not editable.
End of membership (derived)	Automatically set when a cancellation becomes effective. Not editable.

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/Person

Here is recorded whether the member is a person or a company, as well as the name of the member or the direct contact person for the membership. These data are also used for the postal address, for payment requests, or payment confirmations.

Field:	Description:
Type of person	Membership can be requested by the following "person types" by default: "natural person": private individual "Legal person": company, association, etc.
Salutation	Salutation of the member
Academic Title	Academic title of the member
First Name	First name of member
Middle Name	Middle name of member
Last Name	Last name of member
Date of birth	Date of birth of the member, e.g. for automatic sending of congratulations.

Address

This is where the postal address data is recorded. For payment requests, or payment confirmations, this address is also used, if in the ref:Tab Bank - Alternative Billing Address <recordMemberTabBankAltBillingAddress> no other address is stored.

Important

For integrated payment management the module ext:clubmanager_billing is required.

Field:	Description:
Company	Member's company
Address suffix	Member's address suffix
Street	Street of the member
Postal code	Postal code of the member
City	Location of member
Country	Country of member

Note

By default a new member record is nearly empty. Only a few properties are set automatically. Membership status and level are not set directly in version 2.0.0 and are managed exclusively via the Member Journal.

You can adjust default values for other fields using TSconfig

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.

Note

How many locations are offered per member can, for example, be linked to the degree of membership. For example, the following offer can be displayed:

Basic: No locations
Bronze: Only main location
Silver: Main location + 1 additional location
Gold: Main site + X additional sites

Main Location

Sub Location

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.

Direct Debit

Field:	Description:
Participates in direct debit	Is 'true' or 'false'. If 'true', then the fields with the account data must also be filled in.
Account holder	Name of the account holder for direct debit.
IBAN

Alternative Billing Address

Field:	Description:
Name	Name for payment requests, or payment confirmations.
Street

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.

Note

Only the TYPO3 system categories are displayed here, which are made available via the Extension Configuration uidCategoryMember. See also How to create member categories!

Important

With the module ext:clubmanager_faceted_search can be used to search for members can be searched very easily according to their categories.

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
        }
    }
}

Note

More information on how to use the fields in the fluid template, can be found here: How to: Templates!

Member Tab: Access

Field:	Description:
Visible	Only visible member records are displayed in the frontend. In addition, frontend output depends on the effective membership status derived from the Member Journal.
Record created on	Invariant timestamp for the initial creation of the member record.

Relations

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

Frontend-Benutzer

This relation handles the frontend-user for a member.

Field:	Description:

Note

An email address is required for the standard login workflow (initial password setup and password reset). Without an email address, frontend login is only possible if an administrator sets a password manually and communicates it through another channel.

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.