Hi all,

I have a question regarding the new felogin system extension. It has a
sophisticated redirection system whose configuration by TypoScript is
possible, but not described in the manual. I tried to guess from the
source code, but I'm stuck with one thing.

I have the following configuration:

plugin.tx_felogin_pi1 {
storagePid = 5
redirectMode = groupLogin,logout
redirectPageLogout = 39
_LOCAL_LANG.fr.ll_welcome_header = Connexion
}

For the login, it works as expected. For the logout not. What would be
the corect configuration?

Cheers

--

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Francois Suter wrote:
> Hi all,
>
> I have a question regarding the new felogin system extension. It has a
> sophisticated redirection system whose configuration by TypoScript is
> possible, but not described in the manual. I tried to guess from the
> source code, but I'm stuck with one thing.
>
> I have the following configuration:
>
> plugin.tx_felogin_pi1 {
> storagePid = 5
> redirectMode = groupLogin,logout
> redirectPageLogout = 39
> _LOCAL_LANG.fr.ll_welcome_header = Connexion
> }
>
> For the login, it works as expected. For the logout not. What would be
> the corect configuration?

No answer from me ;-), but it would be cool if this is documented. We are also
investigating some stuff that is not documented for the crawler extension.

gRTz

ben
--
netcreators :: creation and innovation
www.netcreators.com - www.TYPO3.nl

Interesse in werken bij Netcreators?
http://www.netcreators.com/bedrijf/vacatures/
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Francois Suter schrieb:
> Hi all,
>
> I have a question regarding the new felogin system extension. It has a
> sophisticated redirection system whose configuration by TypoScript is
> possible, but not described in the manual. I tried to guess from the
> source code, but I'm stuck with one thing.
>
> I have the following configuration:
>
> plugin.tx_felogin_pi1 {
> storagePid = 5
> redirectMode = groupLogin,logout
> redirectPageLogout = 39
> _LOCAL_LANG.fr.ll_welcome_header = Connexion
> }
>
> For the login, it works as expected. For the logout not. What would be
> the corect configuration?
>
> Cheers
>
Hi,

i try to explain:

there are some redirect methods possible. With redirectMode you specify
all methods you want to use.
Now there are 2 options
1) normal (default
last fitting method will be used.
Example: redirectMode = groupLogin, userLogin, logout
If user login extension checks:
groupLogin - has the group a pid configured ? If yes, set redirect
userLogin - has the user a pid configured? If yes, set redirect
So userLogin has higher priority

2) additional config: redirectFirstMethod = 1
Now first method will be used, now groupLogin has higher priority.


The method logout is only used with logout (sounds logic )
So in your case it should work.
I've seen some installations where logout redirect isn't working when
used from an access restricted page. Imho this should work with TS
configuration, at least in my installation this works.

I will complete the manual, but will update if some issues are done (one
is still open in core list)
If something not work as expected feel free to contact me, you should
know where i am

vg Steffen
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi,

> I've seen some installations where logout redirect isn't working when
> used from an access restricted page. Imho this should work with TS
> configuration, at least in my installation this works.

I have tracked down the problem, but I don't know how to solve it.
Here's what happens:

1) the user logs in and moves (or is redirected) to an access-restricted
page
2) from that page, the user logs out
3) TYPO3 kills the FE session
4) TYPO3 then refuses access to that page, since it is access-restricted
and the user is not logged in
5) if a pageNotFound_handling has been defined (as is my case), the user
is redirected to that page before felogin is called (since rendering of
the access-restricted page has not even started)
6) the user arrives at the pageNotFound_handling page, which (in my
case) also contains felogin, but since a redirection took place in
between, the logintype is empty. No logout redirection takes place.

Actually I have an idea for a solution, but I wanted to check with you
first: the solution would to use the logout redirect page as the action
URI for the logout form. Of course this means there must be felogin on
that page, but I don't see another way out. Or maybe is there a hook
that felogin could use *before* the redirection takes place?

Cheers

--

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi,

Francois Suter schrieb:
> Hi,
>
>> I've seen some installations where logout redirect isn't working when
>> used from an access restricted page. Imho this should work with TS
>> configuration, at least in my installation this works.
>
> I have tracked down the problem, but I don't know how to solve it.
> Here's what happens:
>
> 1) the user logs in and moves (or is redirected) to an access-restricted
> page
> 2) from that page, the user logs out
> 3) TYPO3 kills the FE session
> 4) TYPO3 then refuses access to that page, since it is access-restricted
> and the user is not logged in
> 5) if a pageNotFound_handling has been defined (as is my case), the user
> is redirected to that page before felogin is called (since rendering of
> the access-restricted page has not even started)
> 6) the user arrives at the pageNotFound_handling page, which (in my
> case) also contains felogin, but since a redirection took place in
> between, the logintype is empty. No logout redirection takes place.
>
> Actually I have an idea for a solution, but I wanted to check with you
> first: the solution would to use the logout redirect page as the action
> URI for the logout form. Of course this means there must be felogin on
> that page, but I don't see another way out. Or maybe is there a hook
> that felogin could use *before* the redirection takes place?
>
> Cheers
>

that was my idea too to use the action for logout. There is no plugin
needed on the redirect PID as logout is done by core and not the plugin.
You always can logout by append this to any link: &logintype=logout

vg Steffen
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Steffen Kamper schrieb:
> Hi,
>
> Francois Suter schrieb:
>> Hi,
>>
>>> I've seen some installations where logout redirect isn't working when
>>> used from an access restricted page. Imho this should work with TS
>>> configuration, at least in my installation this works.
>>
>> I have tracked down the problem, but I don't know how to solve it.
>> Here's what happens:
>>
>> 1) the user logs in and moves (or is redirected) to an
>> access-restricted page
>> 2) from that page, the user logs out
>> 3) TYPO3 kills the FE session
>> 4) TYPO3 then refuses access to that page, since it is
>> access-restricted and the user is not logged in
>> 5) if a pageNotFound_handling has been defined (as is my case), the
>> user is redirected to that page before felogin is called (since
>> rendering of the access-restricted page has not even started)
>> 6) the user arrives at the pageNotFound_handling page, which (in my
>> case) also contains felogin, but since a redirection took place in
>> between, the logintype is empty. No logout redirection takes place.
>>
>> Actually I have an idea for a solution, but I wanted to check with you
>> first: the solution would to use the logout redirect page as the
>> action URI for the logout form. Of course this means there must be
>> felogin on that page, but I don't see another way out. Or maybe is
>> there a hook that felogin could use *before* the redirection takes place?
>>
>> Cheers
>>
>
> that was my idea too to use the action for logout. There is no plugin
> needed on the redirect PID as logout is done by core and not the plugin.
> You always can logout by append this to any link: &logintype=logout
>
> vg Steffen

I made a patch which is in BT and in core list

vg Steffen

http://bugs.typo3.org/view.php?id=8677
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english