[TYPO3-dev] config.linkVars cHash cache problem

[Ernesto Baschny [cron IT]]

Hi,

please also be aware that if your parameter can be user-generated, and
you start creating menus considering this parameter and an according
cHash in your URLs, you might end up with endless cached pages (i.e.
when google hits your page with different parameters). This might
potentially fill your cache tables "to death".

So you might want to make sure your extension parameter are not
user-generated but generated server-side.

If they need to be user-generated client-side, I wouldn't recommend
generating menus with cHash's, but instead to transform your plugin into
USER_INT which is not influenced by TYPO3 page caching.

Cheers,
Ernesto


JoH asenau schrieb am 14.03.2013 20:54:
> Am 14.03.2013 17:38, schrieb Christian Ludwig:
>> Hi Joey,
>>
>> Well, this was only an example to demonstrate the switch between both of
>> the "test values".
>> But the Links in the HMENU should generate a cHash, shouldn't they?
> 
> Well - it depends ;-)
> 
> Taking a look at the code of 6.0 you can see there is a cHash for
> typolink as soon as you set "useCacheHash = 1"
> 
> HMENU on the one hand is using typolink but on the other hand it is
> called without any "useCacheHash" paramater at all. So IF you want to
> generate a cHash there, you have to provide your own TypoScript setting
> unless there will be a patch to implement this behaviour by default.
> 
> Something like
> 
> doNotLinkIt = 1
> stdWrap.typolink {
>     parameter.field = uid
>     useCacheHash = 1
>     # some other settings here
> }
> 
> should do the job.
> 
> But IMHO you are right and the core should provide that out of the box.
> 
> HTH
> 
> Joey
>