Configuration
Configuration steps
These are the steps to configuring the Agency Registration extension:
#. Install the extension using the Extension Manager. If not already installed, it is recommended that you install the extensions Frontend Login for Website Users (felogin), Salted user password hashes (saltedpasswords), RSA authentication for TYPO3 (rsaauth). And it is required that you install Static Info Tables (static_info_tables) 2.3.0+ and Static Methods since 2007 (div2007) 1.0.3+.
If you want to use the fields of Mail, e.g. the checkbox to send HTML emails, then you must install Mail. Make sure to add the table fields for Mail. You can deinstall Mail afterwards..
#. Using the TYPO3 Install Tool, frontend (FE) login security level should be configured to 'normal', if using an SSL connection, or to 'rsa' otherwise. When frontend (FE) login security level is configured to 'rsa', the page cannot contain multiple registration/login forms (see: http://forge.typo3.org/issues/34568).
#. The extension always uses character set utf-8 by default.
#. Use the status report in Admin Tools->Reports (TYPO3 4.6+ only) to check for possible problems with the installation of the extension (required and conflicting extensions, login security level, salted passwords enablement).
#. Add the following static template to your TypoScript template: 'Agency Registration'.
#. Create a folder page that will contain the records of front end users. Set the TS template constant pid to the page id of this folder. In the folder, create two Front End User Groups. Set the TS template constant userGroupUponRegistration to the uid of the first group and constant userGroupAfterConfirmation to the uid of the second group. The second group gives access to the pages targeted at the registered front end users, while the first group does not. If you use the generation of the user group from an XML file then the user groups will be filled in from uid values in the setfixed setup array.
#. Insert the login box plugin on any page. Then, on the same page, after the login box, insert the Agency Registration extension, using the default (DE: 'normal') display mode, but setting the Record Storage Page to the folder that will contain the front end user records. Set the TS template constant loginPID to the page id of this page.
#. Create a second page after the previous one and set the access general options to “Hide at login”. Insert the Agency Registration extension, setting the display mode to Create (DE: 'Anlegen'), and the Record Storage Page to the folder that will contain the front end user records. Note that the access restriction should be set on the page, not on the content elements. Set the TS template constant registerPID to the page id of this page.
#. Create a third page limiting access to this page to the second user group you created. Insert the Agency extension, setting the display mode to Edit, and the Record Storage Page to the folder that will contain the front end user records. Note that the access restriction should be set on the page, not on the content elements. Set the TS template constant editPID to the page id of this page.
#. Create a fourth page and click the checkbox “Hide in menu”. Insert the Agency Registration plugin, using the Default display mode and setting the Record Storage Page to the folder that will contain the front end user records. Note that no access restriction should be set on this page, because otherwise unregistered users cannot see the confirmation page, and they cannot click on the confirmation link. Set the TS template constant confirmPID to the page id of this page.
#. Decide which fields you want included on the registration form and, among those, which ones you want to be required in order to register. Set TS template constants formFields and requiredFields.
#. Review the extension constants described below. All these properties may be conveniently edited using the Constant Editor TS template tool. If you do not use the Constant Editor to configure the extension, please note the form of the constants assignments in the constants section of your TS template:
typoscript:plugin.
or if you assign multiple values:
constants exampleplugin.tx_agency { property = value ... }Copied!
- TypoScript Setup:
.. code-block:: php :caption: EXT:my_extension/ext_localconf.php
- config {
- sys_language_uid = 0 language = de locale_all = german typolinkLinkAccessRestrictedPages = NONE
}
Setting an image upload folder compatible with front end login for website users
The path of the image upload folder used by the Agency Registration extension may be set in the installation dialog. The default value is uploads/. A popular alternative in many configurations is uploads/. The Agency Registration extension will update the TCA of the fe_users table. Therefore, the back end forms will use the specified path.
It is also possible to show the user image in the user listing produced by the front end login for website users.
Configure the extension to use the email address as user name
- Use the Constant editor to set the constant
useto 1;Email As Username - You may want to change the relative position of the email field in the following subparts of the HTML template:
###TEMPLATE_,CREATE### ###TEMPLATE_andINVITE### ###TEMPLATE_.EDIT###
Note that if you have set constant
enable, the email field will not appear on the editing form because no confirmation request is sent when the email address is modified.
Also in tt_products the email addresses are used as user names.
Make the user name changeable
Use the following setup. Example:
plugin.tx_agency {
edit {
overrideValues {
username >
}
}
}
automatic generation of the customer number
plugin.tx_agency {
create {
generateCustomerNumber = 1
generateCustomerNumber {
prefix = No-
}
}
}
Activate the privacy policy check
Setup:
plugin.tx_agency {
privacyPolicyUrl = 28
create {
fields = first_name, last_name, password, hidden, email, mail_html, privacy_policy_acknowledged
}
}
Alternative in Constants:
plugin.tx_agency {
formFields := addToList(privacy_policy_acknowledged)
}
Language Labels:
plugin.tx_agency._LOCAL_LANG {
de {
click_here_to_edit = Benutzerdaten bearbeiten
privacy_policy_acknowledged = Ich bestätige, dass ich die Datenschutzbestimmung gelesen habe und dieser zustimme.
privacy_policy_acknowledged_2 = Ich bestätige für alle Daten, die ich auf dieser Webseite eingebe, dass Sie diese gemäß den Datenschutzbestimmungen verwenden dürfen.
privacy_policy_hint = Hinweis
privacy_policy_hint_1 = Sie haben das Recht diese Zustimmung zu einem späteren Zeitpunkt per E-Mail zu widerrufen.
click_here_to_see_privacy_policy = Hier klicken um die Datenschutzbestimmung zu lesen.
}
}