[Typo3-dev] Empty cHash problem

[Ernesto Baschny [cron IT]]

Elmar Hinz schrieb am 07.10.2005 01:09:

>> checked (if present, TYPO3 will check it on its own, if not present or
>> empty, TYPO3 needs the plugins to inform if a checking is needed, which
>> is what this section of the article is about).

> It is informed by setting the useCacheHash paramter in the plugin. Still
>  I don't make friendship with this concept. Programmers could forget to
> set it. Why can't it be done automatically for USER-objects?

I am not 100% sure that my reasoning is right, but imagine:

The same USER-object might want to output cached and non-cached things,
e.g. cached detail views for an event, but uncached registration
processing for that event. Ok, in this case I would rather do two
plugins in this case (one USER and one USER_INT), but still, TYPO3
cannot know if the USER object generated all typolink's with the $cache
parameter set.

> First checking if there are more parameters then type and id. And if so
> requireing a valid cHash before any saving action takes part, to say it
> shortend.
> 
> I know there could be some other parameters around like the L-Parameter
> for languages. But that information could be fetched from TypoScript Setup.

If you have an USER object and don't check for cHash, you must make sure
that either you have a no_cache=1 in the URL for all links, or you
set_no_cache(). Then it will also work (without caching).

But ok, I agree that I am missing something here, because TYPO3 could
also simply check for cHash for me and will disable caching on its own.
Its too early monday for such thinking exercises!  :)

Cheers,
Ernesto