[TYPO3-core] RFC Feature #11460: felogin - Integrate possibility to disable redirects on the fly

Ingmar Schlecht ingmar at typo3.org
Fri Jul 3 11:24:40 CEST 2009


Whoops, sorry, missed the thread... This was NOT meant to be for this
patch but for #10656.

cheers
Ingmar

Ingmar Schlecht schrieb:
> Hi Olly,
> 
> could you please commit that to the 4.1 branch, too?
> 
> cheers
> Ingmar
> 
> Oliver Hader schrieb:
>> FYI: Committed to SVN Trunk (rev. 5679)
>>
>> It somehow was a nobrainer...
>>
>> olly
>>
>>
>> Oliver Hader schrieb:
>>> This is an SVN patch request.
>>>
>>> Type: Feature
>>>
>>> Bugtracker references:
>>> http://bugs.typo3.org/view.php?id=11460
>>>
>>> Branches: Trunk
>>>
>>> Problem:
>>> The felogin extensions does not use and proper namespace to transfer
>>> data back to the TYPO3 system. Thus, it's not clear whether felogin or
>>> any other frontend login extension with an expected different behaviour
>>> submitted data.
>>> Imagine a different second login form performs some actions (e.g. in a
>>> checkout process) and redirects should be disabled in this specific case.
>>>
>>> Solution:
>>> Extend the noRedirect behaviour to work also with GET/POST vars. Thus
>>> it's possible to submit the value tx_felogin_pi1[noredirect]=1 that
>>> prevents the felogin extension from executing the redirects.
>>>
>>> Notes:
>>> The patch was created by Steffen Kamper - I'm just posting this issue to
>>> the Core List...
>>>
>>> olly


More information about the TYPO3-team-core mailing list