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:
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
All important data regarding the membership status is recorded here.
Field: |
Description: |
---|---|
Membership number |
Membership Number. Must be individual. |
Membership status. |
A membership can have different statuses:
|
Level |
By default, a membership has a "Basic" level. Here you can further levels/grades can be offered, e.g. to highlight members in the frontend- listing and/or to offer additional information about the single view:
|
Reduced membership |
Here it can be set that only a reduced fee is e.g. for children, young people or pensioners. For automatic billing the module ext:clubmanager_billing is required. |
Cancellation requested |
Here a member can be marked so that the membership is cancelled after the end of the current billing period. For automatic billing the module ext:clubmanager_billing is required. |
Beginning of membership |
Membership start date. |
End of membership |
Date for the end of membership |
|
Main email of the member. This is used for the |
Phone |
Main telephone number to contact. Not for publication intended. |
User |
The frontend user associated with the member to login to the closed member area. See also Relation: frontend user |
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:
|
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 <record
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 by default. You can change them with TSconfig:
- (Membership) State: Not set
- (Membership) Level: Basic
- Type of person: Natural person
- Country: Germany
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:
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
See also: Degree of membership
Important
For clubs with many members there are the following additional modules ext:clubmanager_zip_search and ext:clubmanager_faceted_search.
Main Location
See also Record > Location
Sub Location
See also Record > 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, 5 fields are available for free assignment by default.
- customfield1
- customfield2
- customfield3
- customfield4
- customfield5
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 if. the membership status is > active. |
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: |
---|---|
Username |
The username for the frontend login is freely selectable, but must be be unique. By default, when using the Placeholder datathe member number is used. |
Password (Empty = Regenerate + email to user). |
Password is never sent in plain text. Users get an
e-mail with the request to assign a password, if the password
field is empty, or the existing password is deleted here and the
member record is saved. The mail is sent with the
|
User Groups |
Frontend users are automatically assigned to group clubmanager_FrontendUserGroup. |
Last login |
Shows the date of the last login. If a member has never logged in, it will say 01-01-70 00:00. In this case the member will receive a reminder e-mail for the first login when the corresponding Member login reminder task is set up. |
First login reminder email. |
If a First login reminder email is generated for a member, the timestamp of this e-mail is set here. The member will then receive a new First login reminder e-mail only after the days until reminder has expired in the Member login reminder task. |
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.