Config felogin
Important
If you want to make use of the onboard fe_users function for active members
you have to install felogin first.
See ext: Documentation (Link above).
Important steps
Felogin: Enable Site Set
- Install ext:felogin
- Open your site config:
config/sites/<your- site>/ config. yaml -
Add the login set dependency:
dependencies: - quicko/clubmanager - quicko/clubmanager-loginCopied!
Note
Static TypoScript templates are no longer used. Configure values via site settings.
Felogin: Site settings
Set login-related values in your site settings file:
config/
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
- Go to the module Web > List
- Move to Storage > Frontend User in your pagetree.
- Click on + Create new record on top of the page.
- Click on Frontend Access > Website Usergroup.
- Fill in the Group Title and Save.
Important global configuration
Note
After creating your page tree and the default frontend user group, configure login-related page UIDs in site settings (preferred) and keep extension configuration in sync for legacy fallback where needed.
-
Configure these values in
config/:sites/<your- site>/ settings. yaml clubmanagerLogin.storagePid: 123 clubmanagerLogin.loginFormPid: 45 clubmanagerLogin.memberProfilePage: 67Copied! - Go to Admin Tools > Settings > Extension Configuration.
- Choose clubmanager and then Tab Fe-user-login.
- Set the uid of your default fe_users group defaultFeUserGroupUid (this is still required for member to fe_user assignment).
- Optional fallback values (used if matching site settings are
0): feUsersStoragePid, feUsersLoginPid, defaultTargetLogoutPage. - In case you want to change it, set the lifetime of password recovery links in hours: passwordRecoveryLifeTime.
-
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.
Setup
Have a look at the ext: localization TypoScript Setup and
change wording in your own sitepackage to your needs.
EXT:clubmanager/Configuration/TypoScript/Felogin/setup.typoscript
Important
Copy and change only the localization TypoScript if needed. Keep functional values in site settings where possible.
plugin.tx_felogin_login {
_LOCAL_LANG.de {
//Change the existing localization text as you want them
}
Constants
Have a look at the ext: TypoScript constants and change
them in your own sitepackage to your needs.
EXT:clubmanager/Configuration/TypoScript/Felogin/constants.typoscript
Important
You can still use the following constants in legacy projects. Prefer site settings for the documented login page and storage page UIDs.
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
Note
If you want to change the standard TYPO3 email templates you have to make changes in the LocalConfiguration.php. Therefor open Admin Tools > Settings > Configure Installation-Wide Options > Mail and adjust the following settings to your needs:
- [MAIL] layoutRootPaths: EXT:core/Resources/Private/Layouts/,EXT:backend/Resources/Private/Layouts/,EXT:mysitepackage/Resources/Private/Extensions/Sysmail/Layouts/
- [MAIL] partialRootPaths: EXT:core/Resources/Private/Partials/,EXT:backend/Resources/Private/Partials/,EXT:mysitepackage/Resources/Private/Extensions/Sysmail/Partials/
- [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!
Note
How to setup ext: to work with ext: as expected, see
How to setup felogin!