femanager

Femanager is a TYPO3 extension for a modern Frontend-User registration and profile management.

Copyright: 2013 - 2024
Classification: femanager
Version: 7.4.0
Language: en
Keywords: frontend, user, registration, frontend, profile, sr_feuser_register
Author: Alex Kellner, Stefan Busemann
Email: service@in2code.de

Additional Links

You can use one of the following links, to get more informations about this plugin:

All information about femanager developing, the developers behind femanager, etc...: https://github.com/in2code-de/femanager
femanager is powered by https://www.in2code.de
Do you need help from the community:
- Slack channel #ext-femanager: https://typo3.slack.com/messages/C0NAHDRJB/

Known Issues

Resend confirmation in Backend Module is broken in V7

Introduction

What does it do? | Requirements | Suggestions |

What does it do?

Femanager is an extension for a TYPO3 Frontend-User Registration. Maybe you know sr_feuser_register but you want to use a more modern extension, give femanager a try.

This extension basicly brings an easy-to-use frontend-user-registration with a profile manager to your system. In addition femanager was developed to be very flexible and to bring a lot of features out of the box.

Note: Login and a I forgot my password function is part of the core and not part of femanager.

Requirements

TYPO3 11.5 LTS
Extbase / Fluid
Best use with jQuery and bootstrap

Suggestions

static_info_tables (to show localized countryselection)
sr_freecap (captcha for a spam prevention)

Installation and Configuration

Quick Guide | Step by Step |

Quick Guide

Get it via composer composer require in2code/femanager OR
Import extension from TYPO3 Extension Repository (TER)
Make your extension configuration in the Extension Manager
Include static template to your main TypoScript template
Make your configuration in the Constants Editor (e.g. include jQuery or Twitter Bootstrap)
Add a new page with the Frontend Plugin and make your settings (e.g. for Registration)
Don't forget to set the startpage in the Content Element (the page where the fe_users should be stored)
Setup the hashing algorythm in the TypoScript Setup (see settings passwordSave)
It's recommended to use https on the page with registration form, to secure registration and validation via AJAX
Done

Step by Step

Extension Manager Configuration

Images

Extension Manager

Extension Manager Configuration

Settings

Property	Data Type	Description
disableModule	boolean	Disable Backend Module: You can deactivate the Backend Module if you don't need it
enableConfirmationModule	boolean	Enable confirmation view: Enable a special confirmation view in Backend Module
disableLog	boolean	Disable Log: If you don't want to save each change of an fe_user, you can disable the logfile

Plugin Configuration

Images

Pagecontent

Plugin Configuration

Explanation Plugin Settings

Tab	Field Name	Description	Default Value
Main Settings	Choose View	Choose between Registration, Edit, List and Detail. This is the main setting for the output in Frontend.	[empty]
Registration	Select Fields for New-Form (empty = all fields)	Define which fields should be shown in the registration form in Frontend. Empty shows all fields.	[empty]
Registration	Select Usergroups for new Users	Define the usergroup(s) for the new registered user. Alternative define it via TypoScript or let the User decide which group is the right one.	[empty]
Registration	Registration must be confirmed from sender	If you check this field, the user has to confirm his registration with a link in a mail. This Double-Opt-In ensures that the email is correct.
Registration	Registration must be confirmed from an admin (add one ore more emails)	Add one ore more emails (one per line) if the admin should confirm the registration. This can be combined with the “User Confirmation” field.	[empty]
Registration	Notify admin on registration (add one or more emails)	Notify one or more email receivers (one per line) if a new user was completely registered	[empty]
Edit	Select Fields for Edit-Form (empty = all fields)	Define which fields should be shown in the profile-update-form in Frontend. Empty shows all fields.	[empty]
Edit	Show Delete Button in Edit Form	Renders a delete-Profile-Button in Edit view if checked.
Edit	Profile update must be confirmed from an admin (add one ore more emails)	Add one ore more emails (one per line) if the admin should confirm the profile-update.	[empty]
Edit	Notify admin on Profile update (add one ore more emails)	Add one ore more emails (one per line) if the admin should be informed on a profile-update.	[empty]
Listview	Show Searchfield	Displays a Search in Frontend
Listview	Limit	Set a maximum limit for the FE-List	[empty]
Listview	Order by	Order by a fe_users field	Lastname
Listview	Sorting	Order Ascending or Descending	Ascending
Listview	Show from usergroup (empty = show all)	Filter List by one or more Usergroups	[empty]
Detailview	User to show	Select one user for the Detailview. This can be left empty if this view is only visited from listview.	[empty]
Invitation	Restrict "Add Invitation" to one or more Usergroups (empty = No Restriction)	Restrict invitation form to a usergroup. Only users of this groups can invite new users (maybe an admin usergroup).	[empty]
Invitation	Select Fields for invitation-Form (empty = all fields)	Define which fields should be shown in the invitation form in Frontend. Empty shows all fields.	[empty]
Invitation	Select Usergroups for new Users	Define the usergroup(s) for the new registered user. Alternative define it via TypoScript or let the User decide which group is the right one.	[empty]
Invitation	Notify admin on step 1 (add one ore more emails)	Add one ore more emails (one per line) if the admin should be informed on a user creation in step 1.	[empty]
Invitation	Notify admin if user sets a password (add one ore more emails)	Add one ore more emails (one per line) if the admin should be informed on a user creation in step 2 (password set by user).	[empty]
Additional Settings	Add an internal link to a page with terms and conditions	Will be used for rendering the checkbox that asks the visitor to check that he/she accepted the terms for the registration	[empty]

FE Users Record

Images

fe_users Record

New Fields in FE-Users Records

Tab	Field Name	Description	Default Value
Registration	Creation Time	Date and Time when this profile was created.
Registration	Last profile change at	Date and Time when this profile was changed at the last time.
Registration	Registration confirmed by user	Was this profile confirmed by the user?
Registration	Registration confirmed by admin	Was this profile confirmed by the admin?
Registration	FE_user Log	Logs every femanager-change on this profile	[empty]
Registration	Change Request	This field is needed, if the admin has to confirm a profile update. All fields that should be updated will be stored with an XML in this field.	[empty]

TypoScript Configuration

Images

Constants Editor

Constants

You always find this constants in the file EXT:femanager/Configuration/TypoScript/Main/constants.txt

Constants can be easily changed with the Template Backend-Module (Constants Editor)

There are only a couple of constants in femanager. This is only for the main settings. Please have a look into the TypoScript Setup, if you want to configure more stuff.

Typoscript

plugin.tx_femanager {
    view {
        # cat=plugin.tx_femanager/file; type=string; label= Path to template root (FE)
        templateRootPath = EXT:femanager/Resources/Private/Templates/

        # cat=plugin.tx_femanager/file; type=string; label= Path to template partials (FE)
        partialRootPath = EXT:femanager/Resources/Private/Partials/

        # cat=plugin.tx_femanager/file; type=string; label= Path to template layouts (FE)
        layoutRootPath = EXT:femanager/Resources/Private/Layouts/
    }
    persistence {
        # cat=plugin.tx_femanager//a; type=int+; label= Default storage PID
        storagePid =
    }
    settings {
        # cat=plugin.tx_femanager//0100; type=text; label= Admin Name: Default admin name for all emails to the user
        adminName = Femanager

        # cat=plugin.tx_femanager//0101; type=text; label= Admin Email: Default admin email for all emails to the user
        adminEmail = Femanager@domain.org

        # cat=plugin.tx_femanager//0200; type=text; label= Upload folder: Define where to save images of the users
        uploadFolder = fileadmin/users/

        # cat=plugin.tx_femanager//0900; type=boolean; label= Include jQuery: Load and implement jQuery from external source (googleapis.com)
        jQuery = 0

        # cat=plugin.tx_femanager//0910; type=boolean; label= Include Twitter Bootstrap JS: Load and implement Twitter Bootstrap JavaScript from external source (bootstrapcdn.com)
        bootstrap = 0

        # cat=plugin.tx_femanager//0920; type=boolean; label= Include Twitter Bootstrap CSS: Load and implement Twitter Bootstrap CSS from external source (bootstrapcdn.com)
        bootstrapCSS = 0
    }
}

Setup

You always find this TypoScript in the file EXT:femanager/Configuration/TypoScript/Main/setup.txt

With TypoScript, you are able to:

Configure Clientside and Serverside Validation
Overwrite any Mail setting
Prefill Formfields
Save the values to another table (e.g. tt_address)
Send values to a third-party-software (e.g. a CRM like salesforce)
And much more...

All settings can be configured directly with TypoScript Setup. Please see all possibilities below:

Typoscript

plugin.tx_femanager {
    view {
        templateRootPaths {
            0 = EXT:femanager/Resources/Private/Templates/
            1 = {$plugin.tx_femanager.view.templateRootPath}
        }
        partialRootPaths {
            0 = EXT:femanager/Resources/Private/Partials/
            1 = {$plugin.tx_femanager.view.partialRootPath}
        }
        layoutRootPaths {
            0 = EXT:femanager/Resources/Private/Layouts/
            1 = {$plugin.tx_femanager.view.layoutRootPath}
        }
    }
    persistence {
        storagePid = {$plugin.tx_femanager.persistence.storagePid}
    }
    features {
        #skipDefaultArguments = 1
        requireCHashArgumentForActionArguments = 0
    }

    settings {

        ###################################
        # Settings for CREATE user profiles
        ###################################
        new {
            # take username and copy it to the email field (so email field is not necessary in FE)
#			fillEmailWithUsername = 1

            # login after profile creation (don't work if admin confirmation is turned on)
            login = 1

            # prefilling (empty) input fields with values from TypoScript
            prefill {
#				username = TEXT
#				username.value = ExampleUsername

#				email = TEXT
#				email.value = test@in2code.de
            }

            # redirect user (or admin if adminconfirmation) after profile creation (could be a PID, URL or fileadmin-Link)
#			redirect = TEXT
#			redirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after profile creation request (only if user confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			requestRedirect = TEXT
#			requestRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after user clicks confirmation link in email (only if user confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			userConfirmationRedirect = TEXT
#			userConfirmationRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after user clicks refuse link in confirmation email (only if user confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			userConfirmationRefusedRedirect = TEXT
#			userConfirmationRefusedRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect admin after admin clicks confirmation link in email (only if admin confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			adminConfirmationRedirect = TEXT
#			adminConfirmationRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect admin after admin clicks refuse link in email (only if admin confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			adminConfirmationRefusedRedirect = TEXT
#			adminConfirmationRefusedRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect admin after admin clicks silent-refuse link in email (only if admin confirmation is activated) (could be a PID, URL or fileadmin-Link)
#			adminConfirmationRefusedSilentRedirect = TEXT
#			adminConfirmationRefusedSilentRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # validation of user input values
            # possible validations for each field are: required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, date, mustInclude(number,letter,special,space,uppercase), mustNotInclude(number,letter,uppercase,special,space), inList(1,2,3), captcha, sameAs(password)
            # see manual for an example how to add custom serverside and clientside validation
            validation {
                # Enable clientside Formvalidation (JavaScript)
                _enable.client = 1

                # Enable serverside Formvalidation (PHP)
                _enable.server = 1

                username {
                    required = 1
                    uniqueInDb = 1
                    mustNotInclude = space
                }
                email {
                    required = 1
                    email = 1
                    #uniqueInPage = 1
                }
                password {
                    required = 1
                    #min = 10
                    #mustInclude = number,letter,special
                }
                password_repeat {
                    required = 1
                    sameAs = password
                }
                usergroup {
                    #inList = 1,2,3
                }
                captcha {
                    # requires installation of sr_freecap
#					captcha = 1
                }
            }


            # All email settings within the creation process
            email {

                # Email for User confirmation (User must confirm his Email address)
                createUserConfirmation {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value = {$plugin.tx_femanager.settings.adminEmail}
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailCreateUserConfirmationSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for Admin confirmation (Admin must confirm registration in an email)
                createAdminConfirmation {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailCreateAdminConfirmationSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
                    embedImage = COA
                    embedImage {
                        10 = FILES
                        10 {
                            references {
                                table = fe_users
                                fieldName = image
                                uid.field = uid
                            }

                            begin = 0
                            maxItems = 1

                            renderObj = IMG_RESOURCE
                            renderObj {
                                file.import.dataWrap = {file:current:storage}:{file:current:identifier}
                                file.maxW = 120
                                file.maxH = 120
                            }
                        }

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
                    }
                }

                # Email to user to confirm his new profile (with and without admin confirmation)
                createUserNotify {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 0

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value = {$plugin.tx_femanager.settings.adminEmail}
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailCreateUserNotifySubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for User notify, if admin refused profile registration
                createUserNotifyRefused {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value = {$plugin.tx_femanager.settings.adminEmail}
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailCreateUserNotifyRefusedSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for Admin notify, if profile registration
                createAdminNotify {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailCreateNotifySubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
                    embedImage = COA
                    embedImage {
                        10 = FILES
                        10 {
                            references {
                                table = fe_users
                                fieldName = image
                                uid.field = uid
                            }

                            begin = 0
                            maxItems = 1

                            renderObj = IMG_RESOURCE
                            renderObj {
                                file.import.dataWrap = {file:current:storage}:{file:current:identifier}
                                file.maxW = 120
                                file.maxH = 120
                            }
                        }

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
                    }
                }
            }

            # overwrite any user values with TypoScript
            forceValues {
                # Overwrite initally (default)
                beforeAnyConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 2

                    # Set a fix value
#					email = TEXT
#					email.value = service@in2code.de
                }

                # Overwrite on user confirmation (only if user confirmation was activated)
                onUserConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 3

                    # Set a fix value
#					company = TEXT
#					company.value = in2code.de
                }

                # Overwrite on admin confirmation (only if admin confirmation was activated)
                onAdminConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 4

                    # Set a fix value
#					www = TEXT
#					www.value = http://www.in2code.de
                }
            }

            # Send Form values via POST to another system (e.g. CRM like salesforce or eloqua)
            sendPost {
                # Activate sendPost (0/1)
#				_enable = TEXT
#				_enable.value = 0

                # Target URL for POST values (like http://www.target.com/target.php)
#				targetUrl = https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8

                # build your post datas like &param1=value1&param2=value2
#				data = COA
#				data {
#					10 = TEXT
#					10 {
#						# value from field {username}
#						field = username
#						wrap = &username=|
#                stdWrap.rawUrlEncode = 1
#					}

#					20 = TEXT
#					20 {
#						# value from field {email}
#						field = email
#						wrap = &email=|
#                stdWrap.rawUrlEncode = 1
#					}

#					30 = TEXT
#					30 {
#						# value from field {title}
#						field = title
#						wrap = &title=|
#                stdWrap.rawUrlEncode = 1
#					}
#				}

                # activate debug mode - shows all configuration from curl settings (needs extension devlog)
#				debug = 0
            }

            # Save user values to one or more other tables (e.g. tt_address or something else)
            #       With .field=[fieldname] you have access to the user object
            #       Possible values are: uid, username, address, city, company, country, email, fax, firstName, lastName, middleName, name, password, telephone, fax, title, www, zip and uid_[tablename] (to have access to the uid of one of the last loop)
            storeInDatabase {
#				tt_address {
#					_enable = TEXT
#					_enable.value = 0

#					pid = TEXT
#					pid.value = 21

#					name = TEXT
#					name.field = username

#					email = TEXT
#					email.field = email

#					first_name = TEXT
#					first_name.field = firstName

#					last_name = TEXT
#					last_name.field = lastName
#				}
            }

            misc {
                # Remove Usergroups from Usergroup Selection in Frontend
#				removeFromUserGroupSelection = 2,3

                # initially save password as hash ("Argon2i", "Bcrypt", "Pbkdf2", "Phpass", "Blowfish", "md5", "none" ("sha1" for TYPO3 V8) or empty for extension saltedpasswords - if installed
#				passwordSave = md5

                # Configuration for autogenerated Username and Password
                autogenerate {
                    username {
                        # Length
                        length = 6

                        # Allow uppercase Characters
                        addUpperCase = 0

                        # Allow special Characters
                        addSpecialCharacters = 0
                    }
                    password {
                        # Length
                        length = 10

                        # Allow uppercase Characters
                        addUpperCase = 1

                        # Allow special Characters
                        addSpecialCharacters = 1
                    }
                }
            }
        }




        ###################################
        # Settings for UPDATE user profiles
        ###################################
        edit {
            # take username and copy it to the email field (so email field is not nessesary in FE)
            #fillEmailWithUsername = 1

            # redirect user (or admin if adminconfirmation) after profile update
#			redirect = TEXT
#			redirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after profile update request (only if admin confirmation is activated)
#			requestRedirect = TEXT
#			requestRedirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # prefilling (empty) input fields with values from TypoScript
            prefill {
#				username = TEXT
#				username.value = ExampleUsername

#				email = TEXT
#				email.value = test@in2code.de
            }

            # validation of user input values
            # possible validations for each field are: required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, date, mustInclude(number,letter,special,space), mustNotInclude(number,letter,special,space), inList(1,2,3), captcha, sameAs(password)
            validation {
                # Enable clientside Formvalidation (JavaScript)
                _enable.client = 1

                # Enable serverside Formvalidation (PHP)
                _enable.server = 1

                username {
                    required = 1
                    mustNotInclude = space
                }
                email {
                    required = 1
                    email = 1
                }
                password {
                    required = 1
                    #min = 10
                    #mustInclude = number,letter,special
                }
                password_repeat {
                    required = 1
                    sameAs = password
                }
                usergroup {
                    #inList = 1,2,3
                }
                captcha {
                    # requires installation of sr_freecap
#					captcha = 1
                }
            }

            # All email settings within the update process
            email {

                # Email for admin if user requests update (only if confirmation by admin is activated)
                updateRequest {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailUpdateRequestSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email to user if update request was refused by admin
                updateRequestRefused {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receiver (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value = {$plugin.tx_femanager.settings.adminEmail}
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailUpdateRequestRefusedSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5 (from important to not important)
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for if update request was refused by admin
                notifyAdmin {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receiver (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailUpdateNotifySubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5 (from important to not important)
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }
            }

            # overwrite any user values with TypoScript
            forceValues {
                # Overwrite initally (default) - Note: This values will be updated as soon as the admin confirms the request (if admin confirm is activated)
                beforeAnyConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 2

                    # Set a fix value
#					email = TEXT
#					email.value = service@in2code.de
                }

                # Overwrite on admin confirmation (only if admin confirmation was activated)
                onAdminConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 3

                    # Set a fix value
#					www = TEXT
#					www.value = http://www.in2code.de
                }
            }

            misc {
                # Don't change password if it is empty
                keepPasswordIfEmpty = 1

                # Remove Usergroups from Usergroup Selection in Frontend
#				removeFromUserGroupSelection = 2,3

                # initially save password as hash ("Argon2i", "Bcrypt", "Pbkdf2", "Phpass", "Blowfish", "md5", "none" ("sha1" for TYPO3 V8) or empty for extension saltedpasswords - if installed
#				passwordSave = md5
            }
        }






        ###################################
        # Settings for INVITATION View
        ###################################
        invitation {
            # take username and copy it to the email field (so email field is not nessesary in FE)
            #fillEmailWithUsername = 1

            # redirect admin after step 1
#			redirectStep1 = TEXT
#			redirectStep1 {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after profile delete (from email)
#			redirectDelete = TEXT
#			redirectDelete {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # redirect user after he changed his password
#			redirectPasswordChanged = TEXT
#			redirectPasswordChanged {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}

            # validation of user input values
            # possible validations for each field are: required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, date, mustInclude(number,letter,special,space), mustNotInclude(number,letter,special,space), inList(1,2,3), captcha, sameAs(password)
            # Validation for first Step (Create)
            validation {
                # Enable clientside Formvalidation (JavaScript)
                _enable.client = 1

                # Enable serverside Formvalidation (PHP)
                _enable.server = 1

                username {
                    required = 1
                    uniqueInDb = 1
                    mustNotInclude = space
                }
                email {
                    required = 1
                    email = 1
                }
                usergroup {
                    #inList = 1,2,3
                }
                captcha {
                    # requires installation of sr_freecap
#					captcha = 1
                }
            }
            # Validation for second Step (Edit)
            validationEdit {
                # Enable clientside Formvalidation (JavaScript)
                _enable.client = 1

                # Enable serverside Formvalidation (PHP)
                _enable.server = 1

                password {
                    required = 1
                    #min = 10
                    #mustInclude = number,letter,special
                }
                password_repeat {
                    required = 1
                    sameAs = password
                }
            }

            # All email settings within the update process
            email {

                # Email to user for confirmation
                invitation {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value = {$plugin.tx_femanager.settings.adminEmail}
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailInvitationSubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for admin if profile added (only if admin notify is activated)
                invitationAdminNotifyStep1 {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailInvitationAdminNotifiyStep1Subject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for admin if profile added (only if admin notify is activated)
                invitationAdminNotify {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailInvitationAdminNotifiySubject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }

                # Email for admin if user refused profile invitation (only if admin notify on step 1 is activated)
                invitationRefused {
                    ##########################
                    # Set values (overwrite)
                    ##########################

                    # (de)activate email completely
                    _enable = TEXT
                    _enable.value = 1

                    # Overwrite Receivers (please fill both)
                    receiver {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value = {$plugin.tx_femanager.settings.adminName}
                    }

                    # Overwrite Senders (please fill both)
                    sender {
                        email = TEXT
                        email.value =
                        name = TEXT
                        name.value =
                    }

                    # Overwrite Subject
                    subject = TEXT
                    subject.data = LLL:EXT:femanager/Resources/Private/Language/locallang.xlf:emailInvitationUserRefusedAdminNotifiyStep1Subject

                    # Set CC receivers
                    cc = TEXT
                    cc.value =

                    # Set mail priority from 1 to 5
                    priority = TEXT
                    priority.value =

                    # Add Attachment (separate each with comma)
#					attachments = COA
#					attachments {
#						10 = TEXT
#						10.value = fileadmin/file.pdf
#						10.wrap = |,

#						20 = TEXT
#						20.value = fileadmin/file2.pdf
#						20.wrap = |,
#					}

                    # Add Embed Images (separate each with comma) - can be used in mail with <img src="{embedImages.0}" /> and so on...
#					embedImage = COA
#					embedImage {
#						10 = FILES
#						10 {
#							references {
#								table = fe_users
#								fieldName = image
#								uid.field = uid
#							}

#							begin = 0
#							maxItems = 1

#							renderObj = IMG_RESOURCE
#							renderObj {
#								file.import.dataWrap = {file:current:storage}:{file:current:identifier}
#								file.maxW = 120
#								file.maxH = 120
#							}
#						}

#						20 = TEXT
#						20.wrap = ,|
#						20.value = fileadmin/image.jpg
#					}
                }
            }

            # overwrite any user values with TypoScript
            forceValues {
                # Overwrite initally (default)
                beforeAnyConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 2

                    # Set a fix value
#					email = TEXT
#					email.value = service@in2code.de
                }

                # Overwrite on admin confirmation (only if admin confirmation was activated)
                onAdminConfirmation {
                    # Usergroups can be set with a commaseparated list
#					usergroup = TEXT
#					usergroup.value = 4

                    # Set a fix value
#					www = TEXT
#					www.value = http://www.in2code.de
                }
            }

            misc {
                # Remove Usergroups from Usergroup Selection in Frontend
#				removeFromUserGroupSelection = 2,3

                # initially save password as hash ("Argon2i", "Bcrypt", "Pbkdf2", "Phpass", "Blowfish", "md5", "none" ("sha1" for TYPO3 V8) or empty for extension saltedpasswords - if installed
#				passwordSave = md5
            }
        }


        delete {
            # redirect after profile delete
#			redirect = TEXT
#			redirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}
        }

        list {
            filter {
                searchword {
                    fieldsToSearch = address, city, company, country, email, fax, first_name, image, last_name, middle_name, name, telephone, title, usergroup.title, username, www, zip
                }
            }
        }

        loginAs {
            # redirect when simulate a frontenduser login from administrator
#			redirect = TEXT
#			redirect {
#				typolink {
#					parameter = 1
#					returnLast = url
#					#linkAccessRestrictedPages = 1
#				}
#			}
        }

        misc {
            # Where to save new image files
            uploadFolder = {$plugin.tx_femanager.settings.uploadFolder}

            # Number of allowed images to upload
            uploadAmount = 3

            # Maximum size for image upload in bytes
            uploadSize = 25000000

            # Number of allowed images to upload
            uploadFileExtension = jpeg, jpg, gif, png, bmp, svg, tif, tiff

            # Width of the rendered image in FE
            renderImageWidth = 250
        }

        # Add own finisher classes that will be called after registration, profile update, invitation or deletion (e.g. if you want to do something with form values by your own: Save into tables, call an API, etc...)
        finishers {
            # Femanager finishers
            10.class = In2code\Femanager\Finisher\SaveToAnyTableFinisher
            20.class = In2code\Femanager\Finisher\SendParametersFinisher

#			100 {
                # Classname that should be called with method *Finisher()
#				class = Vendor\Ext\Finisher\DoSomethingFinisher

                # optional: Add configuration for your PHP
#				config {
#					foo = bar

#					fooCObject = TEXT
#					fooCObject.value = do something with this text
#				}

                # optional: If file will not be loaded from autoloader, add path and it will be called with require_once
#				require = fileadmin/femanager/finisher/DoSomethingFinisher.php
#			}
        }

        # Add any dataProcessor classes that will be called just before the action will be rendered
        dataProcessors {

            # Remove empty usergroup variables
            10 {
                class = In2code\Femanager\DataProcessor\CleanUserGroup

                events {
                    New = create
                    Edit = update
                }
            }

            # Enable image upload
            20 {
                class = In2code\Femanager\DataProcessor\ImageManipulation

                config {
                    propertyNamesForUpload = image
                    sysFileRelation {
                        tablenames = fe_users
                        fieldname = image
                        table_local = sys_file
                    }
                }

                events {
                    New = create
                    Edit = update
                }
            }

            # Birthdate converter
            30 {
                class = In2code\Femanager\DataProcessor\DateConverter

                config {
                    fieldNames = dateOfBirth
                }

                events {
                    New = create
                    Edit = update
                }
            }

#			100 {
                # Classname that should be called with an existing method process()
#				class = Vendor\Ext\DataProcessor\DoSomethingDataProcessor

                # optional: Add configuration for your PHP
#				config {
#					foo = bar

#					fooCObject = TEXT
#					fooCObject.value = do something with this text
#				}

                # call this class just before this actions will be opened
#				events {
#					New = create,createStatus
#				}
#			}
        }

        # Add own autoAdminConfirmation classes that can decide if confirmation by admin (only if activated) can be skipped. E.g. if an Email domain fits to a given list.
        autoAdminConfirmation {
            # Femanager autoAdminConfirmation classes
#			10 {
#				class = In2code\Femanager\Domain\Service\AutoAdminConfirmation\EmailDomainConfirmation
#				config {
                    # Just look at the domains of the given Email-Addresses
#					confirmByEmailDomains = .de, .it, .ch, .at
#					confirmByEmailDomainsExceptions = gmail.de, gmx.de
#				}
#			}

#			100 {
                # Classname that should be called with method isAutoAdminConfirmationFullfilled()
#				class = In2code\FemanagerExtended\Domain\Service\AutoAdminConfirmation\IpAddressConfirmation

                # optional: Add configuration for your PHP
#				config {
#					foo = bar

#					fooCObject = TEXT
#					fooCObject.value = do something with this text
#				}
#			}
        }

        # Don't touch this - this is needed to let the plugin know if the main typoscript is included - otherwise an errormessage will be shown in the frontend
        _TypoScriptIncluded = 1
    }
}




#########################
# Inlude JavaScript files
#########################
# add jQuery if it was turned on in the constants
[globalVar = LIT:0 < {$plugin.tx_femanager.settings.jQuery}]
page.includeJSFooterlibs.femanagerJQuery = //ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js
page.includeJSFooterlibs.femanagerJQuery.external = 1
[end]

# add twitter bootstrap JS if it was turned on in the constants
[globalVar = LIT:0 < {$plugin.tx_femanager.settings.bootstrap}]
page.includeJSFooterlibs.femanangerBootstrap = EXT:femanager/Resources/Public/JavaScript/Vendor/bootstrap.min.js
[end]

#########################
# Inlude CSS files
#########################
# add twitter bootstrap CSS if it was turned on in the constants
[globalVar = LIT:0 < {$plugin.tx_femanager.settings.bootstrapCSS}]
page.includeCSS.femanangerBootstrap = EXT:femanager/Resources/Public/JavaScript/Vendor/bootstrap.min.css
[end]

page {
    includeCSS {
        femanagerMain = EXT:femanager/Resources/Public/Css/Main.min.css
    }
    includeJSFooter {
        femanagerValidation = EXT:femanager/Resources/Public/JavaScript/Validation.min.js
        femanager = EXT:femanager/Resources/Public/JavaScript/Femanager.min.js
    }
}

Backend Module

Images

Backend Module (List)

Backend Module (Confirmation)

Explanation

List Module

The Femanager-Backend-Module List is only a small module to search and list some frontend users.

Some AJAX-requests will help you and your editors to delete or hide and unhide users very fast. The edit icons works in the same way as in the list module.

In addition you can see who's only in this moment (If fe_users session exists and is not older than 2h) and you can logout your fe-users with just one click.

A new feature called log in as allows you to open a new window where your frontend is shown and you are already logged in as the chosen user (admin only feature)

Confirmation Module

The confirmation module can be activated via Extension Manager because it's still in the beta phase. Nevertheless you will see a list of not-yet-confirmed fe-users that can be confirmed (or refused) by just one click.

Per default only disabled users are listed that have a user confirmation. If all disabled users should be shown, even if they have no user confirmation (because your plugin is configured, that only admins should confirm the requests), User TSConfig can be used like (to list those users): tx_femanager.UserBackend.confirmation.filter.userConfirmation=0

Configuration

Nearly all settings for the backend module are done in ext_typoscript_setup.txt in the key module.tx_femanager. One setting must be done in your TypoScript Template, the setting module.tx_femanager.settings.configPID should be set in your TypoScript, the default is 1.

You can overwrite these settings in your page TS.

Tab	Field Name	Description	Default Value
settings.configPID	typoscript main template storage	You need to specify the pid, where your main typoscript settings (frontend) is stored. Usually you will take the root page of your installation. This is needed to perform actions like confirm users via Backend or resend confirmation mails. If you have a multidomain system, you can overwrite config in your typoScript Tempplate for each domain. If this setting is not applied by the root typoscript template, try to define your setting in a ext_typoscript_setup.txt in your template / sitepackage extension.	1

Upgrade

to version 7.1.0 | to version 6.0.0 | to version 5.2.0 | to version 5 | to version 4.2.3 / 4.2.4 / 4.2.5

to version 7.1.0

Invitation Template

If you are using customized templates for the invitation function, please check the Resources/Private/Templates/Invitation/Edit.html

You need to add

<f:form.hidden name="hash" value="{hash}"/>

in order,that the function is working.

to version 6.0.0

Version 6.0 support TYPO3 9 LTS and 10 LTS. The support for TYPO3 8 was dropped. No changes on Templates are needed.

Backend Module "Frontend User" - View User Confirmation

If you want to use the Backend Module to confirm or refuse Frontend User, you need to setup the configPID. The extension uses now a frontend call out of the backend, to organise these actions.

module.tx_femanager {
    settings {
        configPID = 1
    }
}

to version 5.2.0

The edit template has to be adjusted, as there is a new parameter 'token' is introduced.

Please update these partials:

/Partials/Misc/DeleteLink.html

The argument token was introduced (token:token)

old:

<f:link.action
   action="delete"
   arguments="{user:user}"
   class="btn btn-warning btn-large"
   additionalAttributes="{data-confirm:'{f:translate(key:\'UserDeleteConfirmation\')}'}">
   <i class="icon-trash icon-white"></i>
   <f:translate key="deleteProfile" />
</f:link.action>

new:

<f:link.action
   action="delete"
   arguments="{user:user, token:token}"
   class="btn btn-warning btn-large"
   additionalAttributes="{data-confirm:'{f:translate(key:\'UserDeleteConfirmation\')}'}">
   <i class="icon-trash icon-white"></i>
   <f:translate key="deleteProfile" />
</f:link.action>

/Templates/Edit/Edit.html

You need to add: <f:form.hidden name="token" value="{token}" /> between the form tag.

Example:

<f:form
	name="user"
	object="{user}"
	action="update"
	enctype="multipart/form-data"
	additionalAttributes="{data-femanager-plugin:data.uid}"
	class="form-horizontal {f:if(condition:'{settings.edit.validation._enable.client}',then:'feManagerValidation',else:'')}">
<fieldset>
	<legend>
		<f:translate key="titleUpdateProfile" />
	</legend>

	<f:form.hidden name="token" value="{token}" />

	more stuff here in the template file…

</f:form>

to version 5

There are minor breaking changes include. Main change is, that all eid scripts were replace, by a page num approach.

In order that the js validation works, you need to take care, that you these page typenums are available:

Backend Module: Login as User feature

feManagerLoginAs.typeNum = 1548943013

see the complete config in file ext_typoscript_setup.txt

Frontend Validation via JS

feManagerLoginAs.typeNum = 1548935210

see the complete config in file Configuration/TypoScript/setup.ext

to version 4.2.3 / 4.2.4 / 4.2.5

If you use your own HTML templates of new/edit/invitation-templates you should compare them with the one from EXT:femanager. There is a new additional attribute inside the form viewhelper: data-femanager-plugin, which contains the content element id.

If you use a modified version of the Validation.js, there are also changes: plugin and action parameter is send to the eID-Script now

Features

Best Practices & HowTos | All Features

Best Practices & HowTos

See some features or best practice parts of the extension femanager.

All Features

Frontend-User Registration

One step registration with autologin
Main configuration with Flexform
User confirmation (Double-Opt In) (optional)
Administration confirmation (optional)
Refuse and Silent Refuse
Fill email field with username (optional)
Redirect with TypoScript standardWrap (optional)
Prefill Formfields via TypoScript standardWrap (optional)
Multiple Validation Possibilities (JavaScript and PHP) (required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, mustInclude(number,letter,special), inList(1,2,3))
Same PHP Methods for JavaScript and PHP Validation
Simply extend validation methods with your extension
Override a lot of Email settings with TypoScript if needed
Set mail attachments or embeded images
Override field values on every single step (e.g. push user to usergroup1 and if he is ready confimed push him to usergroup2)
Send user values to a third party software (e.g. a CRM like salesforce)
Store values in other database tables (e.g. tt_address)
Add Captcha (sr_freecap) for spam prevention

Edit Profile

Main configuration with Flexform
Administration confirmation for change request (optional)
Refuse and Silent Refuse
Fill email field with username (optional)
Prefill Formfields via TypoScript standardWrap (optional)
Multiple Validation Possibilities (JavaScript and PHP) (required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, mustInclude(number,letter,special), inList(1,2,3))
Same PHP Methods for JavaScript and PHP Validation
Simply extend validation methods with your extension
Override a lot of Email settings with TypoScript if needed
Set mail attachments or embeded images
Delete profile with TypoScript redirect

Invitation

Admin could create a new User in Frontend
The new user receives a mail with a secured link, which leads to a password generation form
Same validations as in edit and new
A lot of configuration possibilities with TypoScript

Backend Module

Fulltext search for fe_users
Hide and delete of fe_users via AJAX
Shows Login status
Logout of a frontend user

General

Logging of every change
Saltedpasswords support
List FE-Users in the frontend
Show a user profile in frontend
jQuery include must activate via constants (per default no extra jQuery inclusion)
Show fe_user crdate and tstamp for editors
Store values in other database tables (e.g. tt_address)
Save password as md5 or sha1 per default
HTML with twitter bootstrap classes to reduce integration time
Image upload with status bar
Supports static_info_tables
Extend this extension with new validators or new fields in fe_users (see example in best practice section) or use some SignalSlots
Extension uses namespaces (so TYPO3 version 6.0 or higher is needed)

Use own HTML Templates

Basics

If you want to modify a HTML-File of femanager, you should not overwrite them directly in the extension folder. Think about upcoming versions with important bugfixes or security-patches.

There are two ways to use own HTML-Templates (and Partials / Layouts) instead of the original Templates.

Replace all HTML Templates from Femanager with own Templates

You can copy all Files from - EXT:femanager/Resources/Private/Templates/ - EXT:femanager/Resources/Private/Partials/ - EXT:femanager/Resources/Private/Layouts/

to a new folder in fileadmin - e.g. fileadmin/templates/femanager/ and modify them as you want. After that, you should say femanager to use the new Templates with some lines of TypoScript setup:

plugin.tx_femanager {
	view {
		templateRootPath = fileadmin/templates/femanager/Templates/
		partialRootPath = fileadmin/templates/femanager/Partials/
		layoutRootPath = fileadmin/templates/femanager/Layouts/
	}
}

Replace single HTML Template-Files

You can copy only the Files that you want to modify from - EXT:femanager/Resources/Private/Templates/ - EXT:femanager/Resources/Private/Partials/ - EXT:femanager/Resources/Private/Layouts/

to a new folder in fileadmin - e.g. fileadmin/templates/femanager/ and modify them as you want. After that, you should say femanager to use the old folders and merge them with the new folders

plugin.tx_femanager {
	view {
		templateRootPath >
		templateRootPaths {
			10 = EXT:femanager/Resources/Private/Templates/
			20 = fileadmin/templates/femanager/Templates/
		}
		partialRootPath >
		partialRootPaths {
			10 = EXT:femanager/Resources/Private/Partials/
			20 = fileadmin/templates/femanager/Partials/
		}
		layoutRootPath >
		layoutRootPaths {
			10 = EXT:femanager/Resources/Private/Layouts/
			20 = fileadmin/templates/femanager/Layouts/
		}
	}
}

Show and List Frontend Users

This Feature allows you to display the data of the current user, a selected user by an editor or list user and provide a detail page.

Caution: Please take care, that you do not disclose information in public environments and be careful, which data you show in the detail view.

Show the current user

Useful, if you want to show a "read only view" for the current logged in frontend user.

Configuration:

Add a femanager plugin to your page
choose "detail" view
select the tab "Detail" and choose "Logged in FE User"

Show a given user

You can provide a list view of all frontend users or frontend users of selected groups

Add a femanager plugin to your page
choose "detail" view
select the tab "Detail" and select your options

Attention

If you add this plugin with the selected view, take care, that you do not disclose information in public environments and be careful, which data you show in the detail view.

List Users and provide a detail page

Add a femanager plugin to your page
choose "list" view
select the tab "Detail" and choose a frontend user

Attention

By combining a list aIf you don't select any frontend user, any users can be displayed by passing the get param &tx_femanager_pi1[user]=XX to the detail page url. Be careful to avoid unwanted information disclosure!

Plugin Options:

Show Searchfield: You can provide a searchfield, to filter the users
Limit: Define, how many users are listed per page
Order by: Choose which field should be used to order the list
Sorting: Define sort ordering
Show from usergroup (empty = show all): Select one or more usergroups. If you don't select a group, all frontend users are displayed

Using static_info_tables for country selection

Basics

Install Extension static_info_tables
Install Extension static_info_tables(_de)(_fr)(_pl) etc... for localized countrynames
Import Records of the extensions via Extension Manager (see manual of static_info_tables)
Clear Cache
Copy all Partials from femanager to a fileadmin folder
Set the new Partial Path via Constants: plugin.tx_femanager.view.partialRootPath = fileadmin/femanager/Partials/
Open Partial Fields/Country.html and activate static_info_tables (see notes in HTML-File)

Details for Partial Country.html

The idea is very simple. You can change the “options Attribute” of the form.select ViewHelper:

<femanager:form.select
	id="femanager_field_country"
	property="country"
	options="{femanager:Form.GetCountriesFromStaticInfoTables()}"
	defaultOption="{f:translate(key:'pleaseChoose')}"
	class="input-block-level"
	additionalAttributes="{femanager:Validation.FormValidationData(settings:'{settings}',fieldName:'country')}" />

The GetCountriesFromStaticInfoTables-ViewHelper

Possible options for this ViewHelper are:

Name	Description	Default Value	Example Value
key	Define the Record Column of static_countries table which should be used for storing to fe_users country Note: Please use lowerCamelCase Writing for Fieldnames	isoCodeA3	isoCodeA2
value	Define the Record Column of static_countries table which should be visible in selection in femanager Note: Please use lowerCamelCase Writing for Fieldnames	officialNameLocal	shortNameFr
sortbyField	Define the Record Column of static_countries which should be used for a sorting Note: Please use lowerCamelCase Writing for Fieldnames	isoCodeA3	shortNameDe
sorting	Could be 'asc' or 'desc' for Ascending or Descending Sorting	asc	desc

Some Examples are:

{femanager:Form.GetCountriesFromStaticInfoTables(key:'isoCodeA2',value:'shortNameDe')}
{femanager:Form.GetCountriesFromStaticInfoTables(key:'isoCodeA2',value:'shortNameFr',sortbyField:'shortNameFr')}
{femanager:Form.GetCountriesFromStaticInfoTables(key:'isoCodeA3',value:'isoCodeA3',sortbyField:'isoCodeA3',sorting:'asc')}

Fill Email as Username during registraion

Introduction

Available since 2.0

If this setting is enabled, the mail address is taken as username. The setting can be applied in three situations:

During registration (new)
During edit process of an existing user (edit)
During Invitation process (invite)

Configuration

Enable the "fillEmailWithUsername" option for the area (new, edit, invite), where you like to apply it.

Example for "new" area:

plugin.tx_femanager.settings.new.fillEmailWithUsername = 1

Please take care, that the username is not set to required, otherwise it will not work

plugin.tx_femanager.settings.new.validation.username.required = 0

Example

TypoScript:

plugin.tx_femanager.settings {
    new {
         fillEmailWithUsername = 1
         validation.username.required = 0
    }
}

Remarks

Please mind, if you use this setting in the edit view, a user is able to change his username. Therefor you should always take care, via validation settings, that a username (and also the mail address) stays unique for your users.

Adding new fields to fe_users with your own extension

Picture

Add new Fields to the Registraion-/Editform

Basics

Create a new extension for the new fields
Create ext_tables.sql and Configuration/TCA/Overrides/fe_users.php for adding one or more new fields to fe_users
Add TSConfig file to add one or more fields to the field selection in femanager flexform and include it
Use TypoScript to add your own partials folder and add the templates for your new fields
Create your own user model with getter/setter for your new fields that extends the user model from femanager
Override the user model in your ext_localconf.php

See https://github.com/in2code-de/femanagerextended for an example extension how to extend femanager with new fields and validation methods

Step by Step

Add new fields to the flexform

Extend Fieldselection in Flexform

Add some Page-TSConfig to extend the selection:

tx_femanager {
   flexForm {
      new {
         addFieldOptions {
            twitterId = Twitter ID
            skypeId = Skype ID
            userCategories = User Categories
            somethingElse = LLL:EXT:yourextension/Resources/Private/Language/locallang_be.xlf:custom
         }
      }
      edit < tx_femanager.flexForm.new
   }
}

Modify the partial folder

“twitterId” (see TSConfig) means that femanager searches for a partial TwitterId.html to render the field in the form. So you have to copy the folder EXT:femanager/Resources/Private/Partials (e.g.) to fileadmin/Partials and set the new partial path via TypoScript Constants (see exmple below). In addition you have to add the new Partials files.

plugin.tx_femanager.view.partialRootPaths.100 = EXT:yourextension/Resources/Private/Partials/

Example file fileadmin/Partials/Fields/TwitterId.html:

{namespace femanager=In2code\Femanager\ViewHelpers}
<div class="femanager_fieldset femanager_twitterid form-group">
   <label for="femanager_field_twitterid" class="col-sm-2 control-label">
      <f:translate key="tx_yourextension_domain_model_user.twitter_id" extensionName="yourextension" />
      <f:if condition="{femanager:Validation.IsRequiredField(fieldName:'twitterId')}">
         <span>*</span>
      </f:if>
   </label>
   <div class="col-sm-10">
      <femanager:form.textfield
            id="femanager_field_twitterid"
            property="twitterId"
            class="form-control"
            additionalAttributes="{femanager:Validation.FormValidationData(settings:settings,fieldName:'twitterId')}" />
   </div>
</div>

Example file fileadmin/Partials/Fields/UserCategories.html:

<html
      xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers"
      xmlns:femanager="http://typo3.org/ns/In2code/Femanager/ViewHelpers"
      xmlns:femanagerextended="http://typo3.org/ns/In2code/Femanagerextended/ViewHelpers"
      data-namespace-typo3-fluid="true">
    <div class="femanager_fieldset femanager_user_categories form-group">
        <div class="col-sm-10">
            <fieldset>
                <f:translate key="tx_femanagerextended_domain_model_user.user_categories" extensionName="femanagerextended" />
                <f:if condition="{femanager:Validation.IsRequiredField(fieldName:'user_categories')}">
                    <span>*</span>
                </f:if>
            </fieldset>
            <f:if condition="{femanager:Validation.IsRequiredField(fieldName:'user_categories')}">
                <span>*</span>
            </f:if>
            <f:for as="category" each="{femanagerextended:form.getCategories(rootCategory:1)}">
                <div class="form-check">
                    <f:form.checkbox property="userCategories" value="{category.uid}" multiple="true" class="form-check-input" />
                    <label class="form-check-label">{category.title}</label>
                </div>
            </f:for>
            <f:comment>
                <f:form.select property="userCategories" options="{femanagerextended:form.getCategories(rootCategory:1)}" optionLabelField="title" multiple="true" class="form-select" />
            </f:comment>
        </div>
    </div>
</html>

ext_tables.sql

Example SQL file in your extension which extends fe_users with your new fields:

CREATE TABLE fe_users (
   twitter_id varchar(255) DEFAULT '' NOT NULL,
   skype_id varchar(255) DEFAULT '' NOT NULL,
   user_categories tinytext DEFAULT '0'
);

Configuration/TCA/Overrides/fe_users.php

Example Configuration/TCA/Overrides/fe_users.php file:

$GLOBALS['TCA']['fe_users']['ctrl']['type'] = 'tx_extbase_type';
$tmpFeUsersColumns = [
   'twitter_id' => [
      'exclude' => 1,
      'label' => 'LLL:EXT:yourextension/Resources/Private/Language/locallang_db.xlf:' .
         'tx_yourextension_domain_model_user.twitter_id',
      'config' => [
         'type' => 'input',
         'size' => 30,
         'eval' => 'trim',
      ],
   ],
   'skype_id' => [
      'exclude' => 1,
      'label' => 'LLL:EXT:yourextension/Resources/Private/Language/locallang_db.xlf:' .
         'tx_yourextension_domain_model_user.skype_id',
      'config' => [
         'type' => 'input',
         'size' => 30,
         'eval' => 'trim',
      ],
   ],
   'tx_extbase_type' => [
      'config' => [
         'type' => 'input',
         'default' => '0',
      ],
   ],
   'user_categories' => [
      'exclude' => 1,
      'label' => 'LLL:EXT:femanagerextended/Resources/Private/Language/locallang_db.xlf:' .
          'tx_femanagerextended_domain_model_user.user_categories',
      'config' => [
          'type' => 'category',
          'relationship' => 'oneToMany',
          'treeConfig' => [
              'startingPoints' => 1,
          ],
          'minitems' => 0,
          'maxitems' => 99,
      ]
   ],
];

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTCAcolumns('fe_users', $tmpFeUsersColumns);
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addToAllTCAtypes('fe_users', 'twitter_id, skype_id');

Own User Model

Example Model User.php which extends to the default femanager Model:

namespace In2code\Femanagerextended\Domain\Model;

use TYPO3\CMS\Extbase\Domain\Model\Category;
use TYPO3\CMS\Extbase\Persistence\ObjectStorage;

class User extends \In2code\Femanager\Domain\Model\User
{

    /**
     * twitterId
     *
     * @var string
     */
    protected string $twitterId;

    /**
     * skypeId
     *
     * @var string
     */
    protected string $skypeId;

    /**
     * @var ObjectStorage<Category>
     */
    protected ObjectStorage $userCategories;

    public function __construct($username = '', $password = '')
    {
        parent::__construct($username, $password);
        $this->userCategories = new ObjectStorage();
    }


    /**
     * Returns the twitterId
     *
     * @return string $twitterId
     */
    public function getTwitterId(): string
    {
        return $this->twitterId;
    }

    /**
     * Sets the twitterId
     *
     * @param string $twitterId
     * @return void
     */
    public function setTwitterId(string $twitterId): void
    {
        $this->twitterId = $twitterId;
    }

    /**
     * Returns the skypeId
     *
     * @return string $skypeId
     */
    public function getSkypeId(): string
    {
        return $this->skypeId;
    }

    /**
     * Sets the skypeId
     *
     * @param string $skypeId
     * @return void
     */
    public function setSkypeId(string $skypeId): void
    {
        $this->skypeId = $skypeId;
    }

    /**
     * @return ObjectStorage
     */
    public function getUserCategories(): ObjectStorage
    {
        return $this->userCategories;
    }

    /**
     * @param ObjectStorage $userCategories
     */
    public function setUserCategories(ObjectStorage $userCategories): void
    {
        $this->userCategories = $userCategories;
    }

    /**
     * @param Category $category
     * @return void
     */
    public function addUserCategory(Category $category)
    {
        $this->userCategories->attach($category);
    }

    /**
     * @param Category $category
     * @return void
     */
    public function removeUserCategory(Category $category)
    {
        $this->userCategories->detach($category);
    }
}

Include model with TYPO3 10.4.x

Configuration/Extbase/Persistence/Classes.php:

return [
    \YourVendor\YourExtension\Domain\Model\User::class => [
        'tableName' => 'fe_users',
        'recordType' => 0,
    ],
];

ext_localconf.php:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects'][\In2code\Femanager\Domain\Model\User::class] = [
    'className' => \YourVendor\YourExtension\Domain\Model\User::class,
];
\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Extbase\Object\Container\Container::class)
    ->registerImplementation(
        \In2code\Femanager\Domain\Model\User::class,
        \YourVendor\YourExtension\Domain\Model\User::class
    );

TypoScript to include Model and override default controller with TYPO3 9.5.x

config.tx_extbase{
	persistence{
		classes{
			In2code\Femanager\Domain\Model\User {
				subclasses {
					0 = In2code\Femanagerextended\Domain\Model\User
				}
			}
			In2code\Femanagerextended\Domain\Model\User {
				mapping {
					tableName = fe_users
					recordType = 0
				}
			}
		}
	}
	objects {
		In2code\Femanager\Controller\NewController.className = In2code\Femanagerextended\Controller\NewController
		In2code\Femanager\Controller\EditController.className = In2code\Femanagerextended\Controller\EditController
	}
}

Own Controller Files with TYPO3 9.5.x

EditController.php:

namespace In2code\Femanagerextended\Controller;

class EditController extends \In2code\Femanager\Controller\EditController {

	/**
	 * action update
	 *
	 * @param In2code\Femanagerextended\Domain\Model\User $user
	 * @validate $user In2code\Femanager\Domain\Validator\ServersideValidator
	 * @validate $user In2code\Femanager\Domain\Validator\PasswordValidator
	 * @return void
	 */
	public function updateAction(\In2code\Femanagerextended\Domain\Model\User $user) {
		parent::updateAction($user);
	}
}

NewController.php:

namespace In2code\Femanagerextended\Controller;

class NewController extends \In2code\Femanager\Controller\NewController {

	/**
	 * action create
	 *
	 * @param In2code\Femanagerextended\Domain\Model\User $user
	 * @validate $user In2code\Femanager\Domain\Validator\ServersideValidator
	 * @validate $user In2code\Femanager\Domain\Validator\PasswordValidator
	 * @return void
	 */
	public function createAction(\In2code\Femanagerextended\Domain\Model\User $user) {
		parent::createAction($user);
	}
}

Note: If there are PHP warnings like “…should be compatible with…“ for PHP7, see discussion and solution: https://stackoverflow.com/questions/45563671/how-to-extend-femanager-controller-under-php-7/45564378

or try to change the Controller Files to:

Own Controller Files with PHP 7.2 / TYPO3 9.5.x

EditController.php:

namespace In2code\Femanagerextended\Controller;

class EditController extends \In2code\Femanager\Controller\EditController {

	/**
	 * action update
	 *
	 * @param In2code\Femanagerextended\Domain\Model\User $user
	 * @validate $user In2code\Femanager\Domain\Validator\ServersideValidator
	 * @validate $user In2code\Femanager\Domain\Validator\PasswordValidator
	 * @return void
	 */
	public function updateAction($user) {
		parent::updateAction($user);
	}
}

NewController.php:

namespace In2code\Femanagerextended\Controller;

class NewController extends \In2code\Femanager\Controller\NewController {

	/**
	 * action create
	 *
	 * @param In2code\Femanagerextended\Domain\Model\User $user
	 * @validate $user In2code\Femanager\Domain\Validator\ServersideValidator
	 * @validate $user In2code\Femanager\Domain\Validator\PasswordValidator
	 * @return void
	 */
	public function createAction($user) {
		parent::createAction($user);
	}
}

Adding own serverside and clientside validation to femanager forms

Picture

Add own clientside (JavaScript) Validation

Add own serverside (PHP) Validation

Basics

Use TypoScript to override ValidationClass of femanager with own classes – this enables your validation methods
Config the new validation methods via TypoScript
Add translation labels via TypoScript

Attention

The following example works only with TYPO3 Version 10.4 LTS

See https://github.com/einpraegsam/femanagerextended for an example extension how to extend femanager with new fields and validation methods

Step by Step

New validation classes

CustomClientsideValidator.php:

namespace YourVendor\YourExtension\Domain\Validator;

class CustomClientsideValidator extends \In2code\Femanager\Domain\Validator\ClientsideValidator
{

   /**
    * Custom Validator
    *              Activate via TypoScript - e.g. plugin.tx_femanager.settings.new.validation.username.custom = validationSetting
    *
    * @param string $value Given value from input field
    * @param string $validationSetting TypoScript Setting for this field
    * @return bool
    */
   protected function validateCustom($value, $validationSetting): bool
   {
      // check if string has string inside
      if (stristr($value, $validationSetting)) {
         return true;
      }
      return false;
   }
}

CustomServersideValidator.php:

namespace YourVendor\YourExtension\Domain\Validator;

class CustomServersideValidator extends \In2code\Femanager\Domain\Validator\ServersideValidator
{

   /**
    * Custom Validator
    *              Activate via TypoScript - e.g. plugin.tx_femanager.settings.new.validation.username.custom = validationSetting
    *
    * @param string $value Given value from input field
    * @param string $validationSetting TypoScript Setting for this field
    * @return bool
    */
   protected function validateCustom($value, $validationSetting): bool
   {
      // check if string has string inside
      if (stristr($value, $validationSetting)) {
         return true;
      }
      return false;
   }
}

Configure override of ServersideValidator and ClientsideValidator

ext_localconf.php

$GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects'][\In2code\Femanager\Domain\Validator\ServersideValidator::class] = [
   'className' => \YourVendor\YourExtension\Domain\Validator\CustomServersideValidator::class,
];
$GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects'][\In2code\Femanager\Domain\Validator\ClientsideValidator::class] = [
   'className' => \YourVendor\YourExtension\Domain\Validator\CustomClientsideValidator::class,
];

TypoScript to enable new validation and set labels

plugin.tx_femanager {
   settings.new.validation {
      _enable.client = 1
      _enable.server = 1
      username {
         # Custom Validator - check if value includes "abc"
         custom = abc
      }
   }
   _LOCAL_LANG {
      default.validationErrorCustom = "abc" is missing
      de.validationErrorCustom = "abc" wird erwartet
   }
}

Auto admin confirmation

Introduction

Available since 4.0.0

If you turn on an adminconfirmation by adding an email address in the FlexForm field, admins normally have to confirm new requests from users. But it's possible to implement some own magic to make a confirmation happen automaticly. You can add own AutoAdminConfirmation classes to bring in own magic (auto confirmation for an IP-Range, etc...). At the moment, femanager offers only one AutoAdminConfirmation class, which decided which users are auto-confirmed by the top-level-domain of the email-address.

EmailDomainConfirmation

Small example

Accept every user profile from domains de, it, ch and at:

plugin.tx_femanager.settings {
    autoAdminConfirmation {
         # Femanager autoAdminConfirmation classes
         10 {
             class = In2code\Femanager\Domain\Service\AutoAdminConfirmation\EmailDomainConfirmation
             config {
                 # Just look at the domains of the given Email-Addresses
                 confirmByEmailDomains = .de, .it, .ch, .at
             }
         }
    }
}

Extended example

Accept every user profile from domains de, it, ch and at but not if they are using gmail.de or gmx.de:

plugin.tx_femanager.settings {
    autoAdminConfirmation {
         # Femanager autoAdminConfirmation classes
         10 {
             class = In2code\Femanager\Domain\Service\AutoAdminConfirmation\EmailDomainConfirmation
             config {
                 # Just look at the domains of the given Email-Addresses
                 confirmByEmailDomains = .de, .it, .ch, .at
                 confirmByEmailDomainsExceptions = gmail.de, gmx.de
             }
         }
    }
}

YourAutoConfirmation

Of course you can add your own classes to bring in some own magic.

Example

TypoScript:

plugin.tx_femanager.settings {
    autoAdminConfirmation {
         # Femanager autoAdminConfirmation classes
         100 {
             # Classname that should be called with method isAutoAdminConfirmationFullfilled()
             class = In2code\FemanagerExtended\Domain\Service\AutoAdminConfirmation\IpAddressConfirmation
             # optional: Add configuration for your PHP
             config {
                 ip = 127.0.0.1

                 foo = bar

                 fooCObject = TEXT
                 fooCObject.value = do something with this text
             }
         }
    }
}

PHP:

<?php
declare(strict_types=1);
namespace In2code\FemanagerExtended\Domain\Service\AutoAdminConfirmation;

use In2code\Femanager\Domain\Service\AutoAdminConfirmation\AbstractConfirmation;
use TYPO3\CMS\Core\Utility\GeneralUtility;

/**
 * Class IpAddressConfirmation
 */
class IpAddressConfirmation extends AbstractConfirmation
{

    /**
     * @return bool
     */
    public function isAutoConfirmed(): bool
    {
        return GeneralUtility::getIndpEnv('REMOTE_ADDR') === $this->config['ip']);
    }
}

Some notices

Called method in Confirmation class is always isAutoConfirmed()
Confirmation classes must implement In2codeFemanagerDomainServiceAutoAdminConfirmationConfirmationInterface or extend In2codeFemanagerDomainServiceAutoAdminConfirmationAbstractConfirmation
You have to take care, that your class is included from TYPO3 autoloader otherwise it's not included
Per default femanager offers only EmailDomainConfirmation class at the momment

Add own Finisher classes

Introduction

Let's say you want to easily add some own php functions, that should be called after a user registered. Maybe you want to handle the user input with:

Send it to an API
Store it in a logfile
Save it into a table
Something else...

Small example

Just define which classes should be used. Every method like *Finisher() will be called - e.g. myFinisher():

plugin.tx_femanager.settings {
    finishers {
        1 {
            class = Vendor\Ext\Finisher\DoSomethingFinisher
        }
    }
}

Add a php-file and extend your class with the AbstractFinisher from femanager:

<?php
namespace Vendor\Ext\Finisher;

use In2code\Femanager\Finisher\AbstractFinisher;

/**
 * Class DoSomethingFinisher
 *
 * @package Vendor\Ext\Finisher
 */
class DoSomethingFinisher extends AbstractFinisher
{

    /**
     * MyFinisher
     *
     * @return void
     */
    public function myFinisher()
    {
        // ...
    }
}

Extended example

See the advanced example with some configuration in TypoScript and with the possibility to load the file (useful if file could not be loaded from autoloader because it's stored in fileadmin or elsewhere)

plugin.tx_femanager.settings {
    finishers {
        1 {
            # Classname that should be called with method *Finisher()
            class = Vendor\Ext\Finisher\DoSomethingFinisher

            # optional: Add configuration for your PHP
            config {
                foo = bar

                fooCObject = TEXT
                fooCObject.value = do something with this text
            }

            # optional: If file will not be loaded from autoloader, add path and it will be called with require_once
            require = fileadmin/femanager/finisher/DoSomethingFinisher.php
        }
    }
}

Add your php-file again and extend your class with the AbstractFinisher from femanager:

<?php
namespace Vendor\Ext\Finisher;

use In2code\Femanager\Domain\Model\User;
use In2code\Femanager\Finisher\AbstractFinisher;

/**
 * Class DoSomethingFinisher
 *
 * @package Vendor\Ext\Finisher
 */
class DoSomethingFinisher extends AbstractFinisher
{

    /**
     * @var User
     */
    protected $user;

    /**
     * @var array
     */
    protected $configuration;

    /**
     * @var array
     */
    protected $settings;

    /**
     * Will be called always at first
     *
     * @return void
     */
    public function initializeFinisher()
    {
    }

    /**
     * Will be called before myFinisher()
     *
     * @return void
     */
    public function initializeMyFinisher()
    {
    }

    /**
     * MyFinisher
     *
     * @return void
     */
    public function myFinisher()
    {
        // get value from configuration
        $foo = $this->configuration['foo'];

        // get subject
        $subject = $this->getMail()->getSubject();

        // ...
    }
}

Some notices

All methods which are ending with "finisher" will be called - e.g. saveFinisher()
The method initializeFinisher() will always be called at first
Every finisher method could have its own initialize method, which will be called before. Like initializeMyFinisher() before myFinisher()
Classes in extensions (if namespace and filename fits) will be automaticly included from TYPO3 autoloader. If you place a single file in fileadmin, use "require" in TypoScript
Per default 10 and 20 is already in use from femanager itself (SaveToAnyTableFinisher, SendParametersFinisher) since version 2.0

Using SignalSlots (Hook pendant) to extend femanager

Introduction

SignalSlots (former Hooks) are the possibility for other developer to extend the runtime of a femanager process with their own code.

As an example let's build an extension which sends username and email address of a new registered user to a defined email address.

Note: this is a little bit useless because there is already a setting in flexform to inform administrators and there is a setting in TypoScript to POST values to a third-party-software, but let's use this case for an example.

SignalSlots List

File	Located in	Signal Name	Available Parameters	Description
NewController.php	createAction()	createActionBeforePersist	$user, $this	Use this signal if you want to hook into the process before the new user was persisted
NewController.php	confirmCreateRequestAction()	confirmCreateRequestActionBeforePersist	$user, $hash, $status, $this	Use this signal if you want to hook into the confirmation process
NewController.php	createAdminConfirmationRequest()	createAdminConfirmationRequestAutoConfirm	$user, $this	Signal if a user was auto-confirmed
NewController.php	createAdminConfirmationRequest()	createAdminConfirmationRequestManualConfirmation	$user, $this	Signal if a user was not auto-confirmed and must be confirmed manually
EditController.php	updateAction()	updateActionBeforePersist	$user, $this	Use this signal if you want to hook into the process before the user- profile was updated
EditController.php	confirmUpdateRequestAction()	confirmUpdateRequestActionAfterPersist	$user, $hash, $status, $this	Use this signal if you want to hook after a profile was accepted or refused
EditController.php	deleteAction()	deleteAction	$user, $this	Use this signal if you want to hook into the process before the user- profile will be deleted
InvitationController.php	createAction()	confirmUpdateRequestActionBeforePersist	$user, $hash, $status, $this	Use this signal if you want to hook into the process before a new user was persisted
InvitationController.php	createAllConfirmed()	createAllConfirmedAfterPersist	$user, $this	Use this signal if you want to hook into the process after a new user was persisted
InvitationController.php	editAction()	editActionAfterPersist	$user, $hash, $this	Use this signal if you want to hook into the process before a user adds a new password (step 1)
InvitationController.php	updateAction()	updateActionAfterPersist	$user, $this	Use this signal if you want to hook into the process after a user adds a new password (step 2)
UserController.php	loginAsAction()	loginAsAction	$user, $this	Use this signal if you want to hook into the process after you simulate a frontend user login
UserBackendController.php	confirmUserAction()	confirmUserAction	$user, $this	Signal if a user profile was confirmed in backend module
UserBackendController.php	refuseUserAction()	refuseUserAction	$user, $this	Signal if a user profile was refused in backend module
AbstractController.php	finalCreate()	finalCreateAfterPersist	$user, $action, $this	Use this signal if you want to hook into the process after the new user was persisted
AbstractController.php	updateAllConfirmed()	updateAllConfirmedAfterPersist	$user, $this	Use this signal if you want to hook into the process after the new user was persisted
?	?	?	?	Do you need a new Signal in femanager? Just request one on https://github.com/in2code-de/femanager

Use a SignalSlot

Introduction

As described before, we want to send an email to a defined address every time when a new user is registered.

Creating an extension

femanagersignalslot/ext_emconf.php:

This file is important to install your new extension – write something like:

<?php

$EM_CONF[$_EXTKEY] = array(
		'title' => 'femanagersignalslot',
		'description' => 'signalslotexample for femanager',
		'state' => 'alpha',
		'version' => '0.0.1',
		'constraints' => array(
				'depends' => array(
						'extbase' => '6.0.0-6.1.99',
						'fluid' => '6.0.0-6.1.99',
						'typo3' => '6.0.0-6.1.99',
						'femanager' => '1.0.0-1.0.99',
				),
				'conflicts' => array(
				),
				'suggests' => array(
				),
		),
);

file:femanagersignalslot/ext_localconf.php:

This is an example how to use a signal from femanager – in this case we decided to use the signal “createActionBeforePersist” in class “In2codeFemanagerControllerNewController” and want to call a slot in class “In2codeFemanagersignalslotDomainServiceSendMailService” with methodname “send()”

<?php

$signalSlotDispatcher = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Extbase\\SignalSlot\\Dispatcher');
$signalSlotDispatcher->connect(
	'In2code\Femanager\Controller\NewController',
	'createActionBeforePersist',
	'In2code\Femanagersignalslot\Domain\Service\SendMailService',
	'send',
	FALSE
);

femanagersignalslot/Classes/Domain/Service/SendMailService.php:

This is our main class which is called every time a new registration process was initiated.

<?php
namespace In2code\Femanagersignalslot\Domain\Service;

class SendMailService
{

	/**
	 * Send mail about user information
	 *
	 * @param \In2code\Femanager\Domain\Model\User $user
	 * @param \In2code\Femanager\Controller\NewController $pObj
	 * @return void
	 */
	public function send($user, $pObj)
	{
		$message = '
			New user registered
			Username: ' . $user->getUsername() . '
			Email: ' . $user->getEmail() . '
		';
		mail('your@email.com', 'SignalSlot Test', $message);
	}
}

Resend User Confirmation Request

Introduction

Available since 4.2.0

This feature adds a new view in the backend module to list user, which did not confirm their user accounts. An frontend user admin is now able to resend the confirmation mail or decline (and delete) the user via backend.

Frontend View

An editor can setup a new view "resend confirmation mail". Frontend users, who started their registration process and did not confirm their email so far, can resend a confirmation mail.

Configuration. Add the plugin "Femanager" to a page and select "resend confirmation mail".

IMPORTANT: If you want to use these new views and you did use femanager version 4.1 or older, you need open existing plugins and save them again, in order to allow the usage of this views.

Sometimes unconfirmed users are trying to trigger the confirmation mail again by registering again with the same email or username. They get an error "username / email already existing". Since 4.2, an additional message with a "resend confirmation mail" link is displayed in those cases where the existing user has not yet confirmed his registration.

For this message to be displayed, you need to have the following typoscript setting configured:

settings.showResendUserConfirmationRequestView = {your pid}

The pid is the page uid where your "resend confirmation mail" plugin resides.

Backend View

Lists all frontend users, which did not confirm their email so far. An admin is able, to decline (delete) users or resend an email with a confirmation link.

To activate the feature add the userTSConfig:

tx_femanager.UserBackend.confirmation.ResendUserConfirmationRequest = 1

Rate Limiter

Basics

If you want prevent, that your registration forms, you can enable the rate limiter.

Note: The limiter is enabled by default.

TypoScript Settings

plugin.tx_femanager {
	settings {
		ratelimiter {
		# Number of seconds for the sliding window rate limiter
		timeframe = {$plugin.tx_femanager.settings.ratelimiter.timeframe}
		# Request count. How many requests are allowed in the last <timeframe> seconds. Set to 0 to disable rate limiter.
		limit = {$plugin.tx_femanager.settings.ratelimiter.limit}
	}
	}
}

Frequently Asked Questions (FAQ)

Q: How to use static_info_tables for countryselection?

A: See code in best practice section

Q: How to add new fields to fe_users?

A: See code in best practice section

Q: How to add my own field validation?

A: See code in best practice section

Q: Class 'In2codeFemanagerDomainModelLog' not found - what can I do?

A: This problem normally occurs only if you have installed femanager without composer (btw: it's time for composer :), so your instance is running in classic mode. It's possible that you have added femanager via Extension Manager. Please go into the install tool by opening the URL www.yourdomain.org/typo3/install (of course you have to add a file named ENABLE_INSTALL_TOOL to typo3conf/ folder first) and click on Create autoload information for extensions in section Dump Autoload Information. That will create a new autoload file.

Q: An exception occurred while executing `SELECT uid FROM tx_femanager_domain_model_log WHERE ...` doesn't exist

A: There are some tables missing in your database. Please compare databases with Admin Tools > Maintenance > Database Compare.

Q: How can I disable the clientside/serverside validation?

A: Enable/Disable Validation via TypoScript – disable example:

plugin.tx_femanager {
	settings.new.validation {
		_enable.client = 0
		_enable.server = 0
	}
}

Q: How can I configure the validation of my fields?

A: Have a look into TypoScript:

plugin.tx_femanager {
	settings.new {

		# validation of user input values
		# possible validations for each field are: required, email, min, max, intOnly, lettersOnly, unicodeLettersOnly, uniqueInPage, uniqueInDb, date, mustInclude(number,letter,special,space), mustNotInclude(number,letter,special,space), inList(1,2,3), captcha, sameAs(password)
		# see manual for an example how to add custom serverside and clientside validation
		validation {
			# Enable clientside Formvalidation (JavaScript)
			_enable.client = 1

			# Enable serverside Formvalidation (PHP)
			_enable.server = 1

			username {
				required = 1
				uniqueInDb = 1
				mustNotInclude = special,space
			}
			email {
				required = 1
				email = 1
				#uniqueInPage = 1
			}
			password {
				required = 1
				#min = 10
				#mustInclude = number,letter,special
			}
			usergroup {
				#inList = 1,2,3
			}
		}
	}
}

Note: If you use validation for passwords, values will be send via AJAX to server to check if all is right. It's recommended to use https connections for the registration form.

Q: System should generate random passwords – possible?

Since version 1.0.10 femanager is able to create passwords and username per random if there is no input. If you want to use this, please disable required settings of password (and username)

If no username given, try to get email (if set)
If no username and no email given, create a username by random
If no password given, create a password by random
It's possible to create a new user without filling out any field – this could be used as “onetimeaccount”

Q: How can I prefill form fields?

A: You can use TypoScript cObj to fill form fields in registration- or edit-form:

plugin.tx_femanager {
	settings {
		new {
			prefill {
				username = TEXT
				username.value = ExampleUsername

				email = TEXT
				email.value = test@in2code.de
			}
		}
		edit {
			prefill {
				# fill from GET or POST param like &username=Alex
				username = TEXT
				username.data = GP:username

				# fill from GET or POST param like &email=info@test.de
				email = TEXT
				email.data = GP:email
			}
		}
	}
}

Q: JavaScript Validation won't work – what can I do?

A: Check if all needed JavaScript files are loaded (see frontend html- source). Add some JavaScript with constant editor or directly:

plugin.tx_femanager.settings.jQuery = 1
plugin.tx_femanager.settings.bootstrap = 1
plugin.tx_femanager.settings.bootstrapCSS = 1

Example ordering and needed JavaScripts:

<script src="//ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js" type="text/javascript"></script>
<script src="/typo3conf/ext/femanager/Resources/Public/JavaScript/Vendor/bootstrap.min.js?1502824793" type="text/javascript"></script>
<script src="/typo3conf/ext/femanager/Resources/Public/JavaScript/Validation.min.js?1502824793" type="text/javascript"></script>
<script src="/typo3conf/ext/femanager/Resources/Public/JavaScript/Femanager.min.js?1502824793" type="text/javascript"></script>

Q: How can I send user values to a third-party-software like a CRM?

A: Use some lines of TypoScript to send values after a registration to a tool like a CRM. Test it with a simple php file on your server which sends an email to you with the $_REQUEST Array.

!!! take care to validate the incomming data in your receiver script !!!

TypoScript:

plugin.tx_femanager {
	settings {
		new {
			# Send Form values via POST to another system (e.g. CRM like salesforce or eloqua)
			sendPost {
				# Activate sendPost (0/1)
				_enable = TEXT
				_enable.value = 1

				# Target URL for POST values (like http://www.target.com/target.php)
				targetUrl = https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8
				#targetUrl = http://eloqua.com/e/f.aspx

				# build your post datas like &param1=value1&param2=value2
				data = COA
				data {
					10 = TEXT
					10 {
						# value from field {username}
						field = username
						wrap = &username=|
                    stdWrap.rawUrlEncode = 1
					}

					20 = TEXT
					20 {
						# value from field {email}
						field = email
						wrap = &email=|
                    stdWrap.rawUrlEncode = 1
					}

					30 = TEXT
					30 {
						# value from field {title}
						field = title
						wrap = &title=|
                    stdWrap.rawUrlEncode = 1
					}
				}

				# activate debug mode - shows all configuration from curl settings (needs extension devlog)
				debug = 0
			}
		}
	}
}

Q: How can I store values in another table?

A: With some lines of TypoScript it's possible to store values to any table in the TYPO3 database:

plugin.tx_femanager {
	settings {
		new {
			# Save user values to one or more other tables (e.g. tt_address or something else)
			#       With .field=[fieldname] you have access to the user object
			#       Possible values are: uid, username, address, city, company, country, email, fax, firstName, lastName, middleName, name, password, telephone, fax, title, www, zip and lastGeneratedUid (to have access to the uid of the last loop in the next loop)
			storeInDatabase {
				tt_address {
					_enable = TEXT
					_enable.value = 0

					pid = TEXT
					pid.value = 21

					name = TEXT
					name.field = username

					email = TEXT
					email.field = email

					first_name = TEXT
					first_name.field = firstName

					last_name = TEXT
					last_name.field = lastName
				}
			}
		}
	}
}

Q: How can I overwrite labels and errormessages with my own text?

A: Every TYPO3 extension can be extended with own labels in any language. You have to search for the key, that you want to overwrite – have a look into the file EXT:femanager/Resources/Private/Language/locallang.xlf – example:

plugin.tx_femanager {
	_LOCAL_LANG {
		# Field Labels
		default.tx_femanager_domain_model_user\.username = Email
		de.tx_femanager_domain_model_user\.username = E-Mail
		fr.tx_femanager_domain_model_user\.username = E-mail

		# Errormessages
		default.validationErrorRequired = This is a mandatory field
		de.validationErrorRequired = Hierbei handelt es sich um ein Pflichtfeld
		fr.validationErrorRequired = Ce champ est obligatoire
	}
}

Q: How to add a captcha for spam prevention

A: Since version 1.1.0 femanager allows sr_freecap as captcha extension. Import sr_freecap to your TYPO3. From this moment on, you can add a new fieldtype in your flexform “captcha”. In addition you have to enable captcha with TypoScript:

plugin.tx_femanager.settings.new.validation.captcha.captcha = 1
plugin.tx_femanager.settings.edit.validation.captcha.captcha = 1

Q: How to change the dateformat of the birthday field?

A: Per default “m/d/Y” (for EN) and “d.m.Y “ (for DE) will be used. If you want to overwrite this, you can use some lines of TypoScript

plugin.tx_femanager {
	_LOCAL_LANG {
		# Default Language
		default.tx_femanager_domain_model_user.dateFormat = Y-m-d
		default.tx_femanager_domain_model_user.dateOfBirth.placeholder = Y-m-d

		# For DE
		de.tx_femanager_domain_model_user.dateFormat = Y-m-d
		de.tx_femanager_domain_model_user.dateOfBirth.placeholder = Y-m-d
	}
}

Q: Flashmessage from other plugins are shown in femanager!

A: If you want to hide flashmessages in other extbase plugins, use following TypoScript setup:

config.tx_extbase.legacy.enableLegacyFlashMessageHandling = 0

Q: “Please log in before” but I'm already logged in?

A: Check if the logged in user is really logged in (e.g. add a content-element which should not be viewed if the FE-User is not yet logged in). Check if the FE-Users have an empty value or 0 for column tx_extbase_type in your database.

Q: How to change the extbase_type of new Users?

A: You can change this via TypoScript:

config.tx_extbase.persistence.classes {
	In2code\Femanager\Domain\Model\User {
		mapping {
			tableName = fe_users
			recordType = anyExtbaseType
		}
	}
}

Q: What else can I do with femanager?

A: Have a look into the TypoScript of femanager (see EXT:femanager/Configuration/TypoScript/Main/setup.txt) – here you see how to configure your mails, forceValues, redirect, autologin and much more...

Changelog

Version

7.4.2

Date

2025-05-20

Changes
Version

7.4.1

Date

2024-11-11

Changes
- [DOCS] Update Roadmap
Version

7.4.0

Date

2024-10-04

Changes
- [TASK] Use semantic HTML for tables in the emails - thx to Oliver Klee
- [TASK] Improve the code formatting of additional input attributes - thx to Oliver Klee
- [TASK] Apply the latest Rector fixes for TYPO3 11LTS - thx to Oliver Klee
- [TASK] Mitigate browser "spell jacking" in form elements- thx to Patrick Lenk
- [TASK] Add autocomplete attribute to password fields - thx to Patrick Lenk
- [TASK] Switch to PHP-based Documentation Rendering - thx to Sandra Erbel
- [BUGFIX] Avoid deprecated PHP function utf8_decode - thx to Oliver Klee
- [BUGFIX] Add missing scope - thx to Stefan Busemann (in2code)
- [BUGFIX] Add missing if clause in UserProperties.html - thx to Sandra Erbel
- [BUGFIX] Use specific seleniarm image for behat tests - thx to Stefan Busemann (in2code)
- [BUGFIX] Restore email notification to admin after registration - thx to Patrick Lenk
- [BUGFIX] Fix composer script calls in the test:rector:fix script - thx to Oliver Klee
- [BUGFIX] Fix the Rector PHP target version - thx to Oliver Klee
- [BUGFIX] Allow the PHPStan extension installer for Composer - thx to Oliver Klee
Version

7.3.0

Date

2024-05-08

Changes
- [FEATURE] Add confirmation form to delete profile during registration - thx to Stefan Busemann (in2code)
- [FEATURE] Add BeforeMailBodyRenderEvent - thx to Michael Bakonyi
- [FEATURE] Include bootstrap directly from repository instead of maxcdn.bootstrapcdn.com - thx to Felix Ranesberger (in2code)
- [BUGFIX] Fix a typo in the labels - thx to Oliver Klee
- [BUGFIX] Open the "terms & conditions" page in a new tab - thx to Oliver Klee
- [BUGFIX] errorClass attribute not working - thx to Stig Nørgaard Færch
- [DOC] Update documenation - thx to Daniel Hoffman (in2code)
Version

7.2.3

Date

2023-12-13

Changes
- [SECURITY] This update is needed for version for 7.0.0 to 7.2.2 older versions are not affected
- BUGFIX] Dont use initilize actions for granting access - thx to Daniel Hofmann (in2code)
Version

7.2.2

Date

2023-10-04

Changes
- [SECURITY] This update is needed for version for 7.0.0 to 7.2.1 older versions are not affected
- [BUGFIX] Add missing permission check for invitation controller - thx to Daniel Hofmann (in2code)
Version

7.2.1

Date

2023-08-08

Changes
- [TASK] Adds documentation for extended - thx to Daniel Hofmann (in2code)
- [TASK] Update Image used for Github Actions
- [BUGFIX] Fixes reaction when no typoscript configuration is set for redirect - thx to Daniel Hofmann (in2code)
- [BUGFIX] Fixed Object Support for getDirtyPropertiesFromUser() - thx to Daniel Hofmann (in2code)
Version

7.2.0

Date

2023-07-17

Changes
- [FEATURE] Add column "inactive since" to backend list - thx to Thomas Löffler
- [BUGFIX] missing email AdminNotify after editing of user profile - thx to Christian Ludwig
- [BUGFIX] Do not re-evaluate object values in ServersideValidator - thx to Torben Hansen
- [BUGFIX] Add full object support in getDirtyPropertiesFromUser() - thx to Daniel Haupt
- [BUGFIX] Prevent undefined array key for empty configPID - thx to Daniel Haupt
- [BUGFIX] Migrate usage of GU::lcfirst with Rector - thx to Torben Hansen
- [TASK] Corrects Documenation Rendering Configuration - thx to Daniel Hoffmann
- [TASK] [TASK] Replace jQuery scrollTop with vanilla scrollIntoView - thx to Felix Ranesberger
Version

7.1.1

Date

2023-03-16

Changes
- [BUGFIX] Notification email to admin now sends changes again
- [BUGFIX] Notification email to admin is also sent when adding recipient's address to flex form only
- [TASK] Removes configPID from ext_typoscript_setup.typoscript
Version

7.1.0

Date

2023-01-19

Changes
- [FEATURE] Add support for PHP 8 and 8.1 - thx to Stefan Busemann, Bastien Lutz, Mathias Bolt Lesniak, Thomas Löffler, Johannes Seipelt
- [BUGFIX] Re-fetch session from database to update 'userSession' property of TSFE. Thx to Thomas Off <thomas.off@retiolum.de>
- [BUGFIX] Add hash check for invitation action - thx to Max Schäfer & Dennis Schober-Wenger
- [REFACTOR] Remove deprecated code and introduce rector - thx to Thomas Löffler
Version

7.0.1

Date

2022-10-31

Changes
- [BUGFIX] (!!!) Security Fix - Broken Access Control in Usergroup Validation (Andreas Nedbal - in2code) - thx to TYPO3 Security Team
- [BUGFIX] login after registration (Re-fetch session from database to update 'userSession' property of TSFE) - thx to Thomas Off
- [BUGFIX] CleanUserGroup DataProcessor - thx to Daniel Hoffmann (in2code)
Version

7.0.0

Date

2022-07-11

Changes
- [FEATURE] Add column "inactive since" to backend list - thx to SpoonerWeb
- [TASK] Add support for TYPO3 11
- [TASK] Update Test enviroment and add addtitional tests
- [TASK] Add missing translation key for "createStatus"
- [TASK] Bump jquery from 3.2.1 to 3.6.0 and migrate deprecated shorthand event .blur and .submit - thx to Patrick Lenk
- [BUGFIX] replace is_array with isset - hx to AlexVossBu
- [BUGFIX] no custom controller needed in TYPO3 10
- [BUGFIX] Remove "endtime" for check of unique in db
- [DOCS] Add note for configpid setting
- [BUGFIX] updated sjbr/static-info-tables version
Version

6.4.0

Date

2024-05-08

Changes
- [FEATURE] Add confirmation form to delete profile during registration - thx to Stefan Busemann (in2code)
- [TASK] Remove unnecessary scrollIntoView property - thx to Felix Ranesberger (in2code)
- [TASK] Replace jQuery scrollTop with vanilla scrollIntoView - thx to Felix Ranesberger (in2code)
- [TASK] Build new JS distribution file - thx to Felix Ranesberger (in2code)
Version

6.3.2

Date

2021-10-13

Changes
- [TASK] Add setter to allow modification of email object inside event listeners - thx to https://github.com/mediaessenz
- [TASK] Refactor forceValues to FrontendUtility and add a test - thx to https://github.com/ute-arbeit
- [TASK] Remove TCA configuration showRecordFieldList - thx to https://github.com/Patta
- [BUGFIX] Make forceValues work for field names with underscores - thx to https://github.com/ute-arbeit
- [BUGFIX] Allow frontend user login via EXT:femanager - thx to https://github.com/webian
- [BUGFIX] repairs confirmation view due to missing state column - thx to in2code / Bastien Lutz
- [BUGFIX] refusing users from the admin confirmation backend list - Thx to https://github.com/fwg
- [BUGFIX] correct v10 Extbase persistence config - thx to jonaseberle
- [BUGFIX] add missing field mapping for custom properties for TYPO3v10+ - thx to jonaseberle
- [BUGFIX] embedded images in emails - thx to https://github.com/fwg
- [BUGFIX] Email subject for sendCreateUserConfirmationMail - thx to Pixelant
Version

6.3.1

Date

2021-07-19

Changes
- [BUGFIX] Security: Disallow SVG as Filetype
Version

6.3.0

Date

2021-07-02

Changes
- [FEATURE] Add divers as gender - thx to spoonerWeb
- [FEATURE] Add possibility to set preferred or limited countries to selector - thx to spoonerWeb
- [TASK] Use USER_INT instead of no_cache for better performance - thx to
- [TASK] Update Behat Tests and Test Environment - thx to in2code
- [TASK] Add option to run single behat test - thx to in2code
- [TASK] Add terupload via Github Action - thx to in2code
- [BUGIFX] subject translation for createUserConfirmationMail - thx to https://github.com/martinschoene
- [BUGFIX] Fix field validation messages - thx to https://github.com/dahaupt
- [BUGFIX] Fix link generation in general redirect method - thx to Andre Spindler
- [BUGFIX] If user confirmation sent, do not send admin confirmation - thx to SpoonerWeb
- [BUGFIX] Use exact email to check for resending confirmation mail - thx to SpoonerWeb
Version

6.2.1

Date

2021-14-06

Changes
- [BUGFIX] Use ratelimiter service only in FE context - thx to Thomas Löffler
Version

6.2.0

Date

2021-06-06

Changes
- [FEATURE] Add RateLimiter for registration form - see documentation
- [BUGFIX] Improve date validation - thx to https://github.com/pfuju
- [BUGFIX] Validation for checkUniqueDb ignores starttime/endtime - thx to in2code
- [BUGFIX] return true for FileReferences - https://github.com/marclindemann
- [BUGFIX] Template missing for New->create - https://github.com/kitzberger
- [BUGFIX] Select previously saved state in state menu - ttps://github.com/mabolek
- [BUGFIX] Subject not translated on confirmation email - thx to https://github.com/Moongazer
- [BUGFIX] Remove unnecessary paramter from disable url - thx to https://github.com/Patta
- [TASK] change language detection to language aspect - thx to https://github.com/cehret
- [TASK] Add validation for all unicode letters - thx to in2code
- [TASK] Add Behaviour Test for terms and conditions - thx to in2code
- [TASK] Add tests for countries and states, update test data - thx to in2code
- [TASK] Resolve TYPO3 V11 breaking change for plugin registration - thx to https://github.com/Footrotflat
Version

6.1.2

Date

2020-12-03

Changes
- [BUGFIX] JavaScript error in FeManager.js - thanks to https://github.com/grischpel
Version

6.1.1

Date

2020-10-26

Changes
- [TASK] Set fixed install tool password for dev env (better dev env performance)
- [BUGFIX] Prevent warning in UpperViewHelper - thanks to christophlehmann's PR https://github.com/in2code-de/femanager/pull/289
- [BUGFIX] Use getter for userTS - thanks to siwa-pparzer's PR https://github.com/in2code-de/femanager/pull/287
- [BUGFIX] fix statically called non-static method calls in InvitationController - thanks to ewokhias's PR https://github.com/in2code-de/femanager/pull/294
- [BUGFIX] Fix Exception in wrong file upload - thanks to marclindemann's PR https://github.com/in2code-de/femanager/pull/262
Version

6.1.0

Date

2020-08-13

Changes
- [FEATURE] Add support for country selection options - see documentation
- [BUGFIX] Allow validation via captcha - thanks to Germar https://github.com/Germar and dnozdrin https://github.com/dnozdrin
Version

6.0.1 (!!!)

Date

2020-07-15

Changes
- [TASK] Remove falsly declarated support for TYPO3 V9 in femanager 6 branch
Version

6.0.0 (!!!)

Date

2020-07-06

Changes
- [FEATURE] Add Support for TYPO3 10 LTS - Sponsored by inixmedia and in2code, Thanks to Markus Bachmann, Filar
- [FEATURE] Add support for PageTS and UserTS configuration for femanager backend module - Sponsored by in2code
- [FEATURE] Change user confirmation process to frontend requests - Sponsored by in2code
- [TASK] (!!!) Remove Support for TYPO3 8.7 and PHP < 7.2
- [TASK] Add docker based development env - Sponsored by in2code
- [TASK] Update Unit and Behaviour Tests - Sponsored by inixmedia and in2code
- [TASK] Remove legacy password hashing code - Sponsored by in2code
Version

5.4.2

Date

2020-12-03

Changes
- [BUGFIX] JavaScript error in FeManager.js - thanks to https://github.com/grischpel
Version

5.4.1

Date

2020-10-26

Changes
- [BUGFIX] Prevent Exceptions on wrong file upload - thanks to https://github.com/in2code-de/femanager/pull/262
Version

5.4.0

Date

2020-08-30

Changes
- [FEATURE] Add support for country selection options (for TYPO3 V8 / V9) - see documentation- Sponsored by Resultify.se
Version

5.3.1

Date

2020-08-06

Changes
- [BUGFIX] Allow validation via captcha - thanks to Germar https://github.com/Germar and dnozdrin https://github.com/dnozdrin
Version

5.3.0

Date

2020-07-06

Changes
- [FEATURE] Adds uppercase validation for password (https://github.com/in2code-de/femanager/issues/91) - thanks to https://github.com/alexkue7911
- [FEATURE] Add support for PageTS and UserTS configuration for femanager backend module - Sponsored by in2code
- [FEATURE] Change user confirmation process to frontend requests - Sponsored by in2code
- [BUGFIX] Use FlexFormService to validate allowed views (https://github.com/in2code-de/femanager/issues/177) - thanks to https://github.com/nigelmann
- [BUGFIX] TCA migrations for TYPO3 v9.5 - thanks to https://github.com/TrueType
- [BUGFIX] Make ajax validation URL more robust - thanks to https://github.com/baschny
- [BUGFIX] Allow '0' if field is required (https://github.com/in2code-de/femanager/issues/52) - thanks to https://github.com/DanielSiepmann
- [DOCS] Add info about PHP7 and extending femanager - thanks to https://github.com/uwejakobs
Version

5.2.0 (!!!)

Date

2019-11-26

Changes
- !!![BUGFIX] Allow password hashing none for TYPO3 V9

-

Version: 5.1.1
Date: 2019-05-26
Changes

[BUGFIX] Allow password hashing none for TYPO3 V9

-

Version: 5.1.0
Date: 2019-05-21
Changes

[FEATURE] Allow TYPO3 Version 8, allow PHP 7.3
[BUGFIX] Allow password hashing none for TYPO3 V9
[BUGFIX] Invitation: Peform expected redirect (thanks to Footrotflat)
[BUGFIX] Use HashFactory of V9 and fallback for V8
[BUGFIX] use hash password methods (thanks to Lex Frolenko)
[BUGFIX] Fix JS validation URL (thanks to Daniel Haupt)
[BUGFIX] Use doctrine contraints on pluginRespository (thanks to netcoop)
[BUGFIX] use doctrine for UserUtility queries
[BUGFIX] Update russian lang label
[BUGFIX] Update GetFirstViewHelper (thanks to Oliver Beck)
[BUGFIX] Fix translation of field names in form errors (thanks to Daniel Haupt)
[TASK] Add signal beforeSend (thanks to Michael Bakonyi)
[TASK] Updated 5.0.0 release date (thanks to Stephan Großberndt)
[TASK] Consistent naming for ConnectionPool method (thanks to Stephan Großberndt)
[TASK] Fix a small typo in FAQ (thanks to Thomas Deuling)
[DOCS] Add migration notes
[DOCS] Fix multiple errors and warnings (thanks to Daniel Haupt)
[DOCS] Add detailed changelog

-

Version: 5.0.0 (!!!)
Date: 2019-02-01
Changes

Feature: Support for TYPO3 version 9
Bugfix: Change feManagerLoginAs Feature to typeNum
Bugfix: Change Frontend Validation from eid script to typeNum

Pls look at https://github.com/in2code-de/femanager for a changelog for older versions

Older versions of femanager, even those which are probably not downloadable through TER, are available on github: https://github.com/in2code-de/femanager/releases

femanager

Table of Contents

Additional Links

Known Issues

Introduction

What does it do?

Requirements

Suggestions

Installation and Configuration

Quick Guide

Step by Step

Extension Manager Configuration

Images

Settings

Plugin Configuration

Images

Explanation Plugin Settings

FE Users Record

Images

New Fields in FE-Users Records

TypoScript Configuration

Images

Constants

Typoscript

Setup

Typoscript

Backend Module

Images

Explanation

Configuration

Upgrade

to version 7.1.0

to version 6.0.0

to version 5.2.0

to version 5

to version 4.2.3 / 4.2.4 / 4.2.5

Features

Best Practices & HowTos

All Features

Frontend-User Registration

Edit Profile

Invitation

Backend Module

General

Use own HTML Templates

Basics

Replace all HTML Templates from Femanager with own Templates

Replace single HTML Template-Files

Show and List Frontend Users

Show the current user

Show a given user

List Users and provide a detail page

Using static_info_tables for country selection

Basics

Details for Partial Country.html

Fill Email as Username during registraion

Introduction

Configuration

Example

Remarks

Adding new fields to fe_users with your own extension

Picture

Basics

Step by Step

Add new fields to the flexform

Modify the partial folder

ext_tables.sql

Configuration/TCA/Overrides/fe_users.php

Own User Model

Include model with TYPO3 10.4.x

TypoScript to include Model and override default controller with TYPO3 9.5.x

Own Controller Files with TYPO3 9.5.x

Own Controller Files with PHP 7.2 / TYPO3 9.5.x

Adding own serverside and clientside validation to femanager forms

Picture

Basics

Step by Step

New validation classes

Configure override of ServersideValidator and ClientsideValidator

TypoScript to enable new validation and set labels

Q: An exception occurred while executing `SELECT uid FROM tx_femanager_domain_model_log WHERE ...` doesn't exist