DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
EXT: FE-User Suite¶
| Author: | Chetan Thapliyal |
|---|---|
| Created: | 2007-08-23T14:43:36 |
| Changed by: | Suman Debnath |
| Changed: | 2007-08-25T13:30:14 |
| Classification: | cs_feuser_suite |
| Author: | Chetan Thapliyal, Suman Debnath |
| Email: | chetanthapliyal@gmail.com, contact@debnath.in |
| Info 3: | |
| Info 4: |
EXT:FE-User Suite¶
Extension Key: cs_feuser_suite
Copyright 2007, Chetan Thapliyal & Suman Debnath,
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.com
Table of Contents¶
EXT:FE-User Suite 1
Introduction 1
What does it do? 1
Features 1
Users manual 1
Installation and configuration 1
Redirection 2
FAQ 3
Known problems 3
To-Do list 3
Introduction¶
What does it do?¶
Although intended to cover many front end user utilities like registration, this release contains a front-end login box with some unique features.
Features¶
Template based interface.
Granular control over global, group level and user level redirection
Users manual¶
Installation and configuration¶
Install the extension just like any other Typo3 extensions.
Create a page and add `FE-User login` plug-in to it.
Browse and select the page containing user records in the
`Login Options` tab of the extension flexform, as shown in the
following screenshot.
Redirection options has been described in the following section
Clear both FE as well as cache in typo3conf.
Redirection¶
This extension allows multiple levels of control over redirection after login.
The simplest is the one available within the 'Main' tab of the extension flexform, as shown in the following screenshot. Browse and select the appropriate page where you want the users to be redirected after login. This will affect all users using this login form unless overridden by the other options.
For the group and user level controls, you will have to edit the appropriate template record and add something like the code shown in below within Info/Modify->Setup.
plugin.tx_csfeusersuite_pi1 {¶
plugin.tx_csfeusersuite_pi1 {redirect {user {0 {user_id = 1page_id = 21}1 {user_id = 2page_id = 20}}group {0 {group_id = 1page_id = 19}1 {group_id = 2page_id = 18}}}}
plugin.tx_csfeusersuite_pi1 {
redirect {
user {
0 {
user_id = 1
page_id = 21
}
1 {
user_id = 2
page_id = 20
}
}
group {
0 {
group_id = 1
page_id = 19
}
1 {
group_id = 2
page_id = 18
}
}
}
}
In the block under redirect.user , we are basically defining user_id and page_id pairs. You will need to define one pair for every individual user redirection.
Similarly, in the block under redirect.group , we are defining group_id and page_id pairs. Again, you will need to define one pair for every individual group redirection.
Now, user level redirection has higher priority than group and group level redirection has higher priority than global i.e. the flexform option . This means, you are able to add only just enough configuration to handle any special cases. In a typical scenario, you will set the global option as a 'Catch All', set the group level options to handle any special groups (e.g. paid subscribers, front end administrators, etc) and use the user level option for exceptional cases.
FAQ¶
Known problems¶
If you face any problem in login or post login redirection then try enabling the `No cache:` option within page properties.
To-Do list¶
EXT: FE-User Suite - 3