[TYPO3-core] RFC: #9599: [felogin] Enable Caching "USER" instead of "USER_INT"

Oliver Hader oliver at typo3.org
Tue Aug 25 09:58:17 CEST 2009


Hi Michael,

I'm going to take care about that behaviour in pibase that is triggered
on creating the object.

olly


Michael Stucki schrieb:
> Unfortunately, there was no feedback since my last mail.
> 
> So, is anyone going to take care of it, or should I revert the change?
> 
> - michael
> 
> Michael Stucki schrieb:
>> Hi Olly & Steffen,
>>
>> there is a bug in this patch:
>>
>> Changing a plugin from USER_INT to USER requires more than just changing
>> ext_localconf.php. You also need to change variables within the plugin
>> code, most notably $this->pi_USER_INT_obj and $this->pi_checkCHash.
>>
>> pi_USER_INT_obj is a flag that controls whether or not the link
>> generator should apply the &cHash or &no_cache parameter. Have a look at
>>  $this->pi_linkTP() to see the magic.
>>
>> pi_checkCHash is also a flag which controls whether or not a page should
>> be triggered non-cached if the cHash is incorrect. Thus, I would always
>> turn this on for USER objects, and off for USER_INT objects.
>>
>> So it seems to me like if there are internal links, they will be
>> generated wrong now in either of the cases. What I suggest is to
>> duplicate the logic from the condition into the main() function.
>>
>> - michael
>>
>> Oliver Hader schrieb:
>>> FYI: Committed the attached patch as follow-up to SVN Trunk (rev. 5630)
>>> * globalVar is just for numbers, not for strings
>>> * forgot password action and logout action did not trigger to use
>>> USER_INT - thus, redirects have not been processed
>>>
>>> olly
>>>
>>>
>>> Steffen Kamper schrieb:
>>>> Hi,
>>>>
>>>> here is an update taken the followed comments into account.
>>>>
>>>> vg Steffen
-- 
Oliver Hader
TYPO3 Release Manager 4.3


More information about the TYPO3-team-core mailing list