[TYPO3-ect] 4.1.0: Request parameters could not be validated

[Steffen Kamper]

Hi Franz,

"Franz Koch" <typo at fx.MINUS.graefix.DOT.de> schrieb im Newsbeitrag 
news:mailman.1.1173036806.28604.typo3-team-extension-coordination at lists.netfielders.de...
> Hi guys,
>
>> this is a point i didn't understood at all.
>> I fixed it in my installation by changing the default value in
>> t3lib/config_default.php
>> setting
>> 'pageNotFoundOnCHashError' => 0,
>>
>> But i don't see the point what we can do to prevent this error.
>
> you can easily disable that feature/bug in the install tool and don't have 
> to manipulate config files of typo3 ;)
>

I know that. But I think a change in core, that breaks a lot of extensions 
work only by setting default to 1 should be default 0 when this causes no 
errors. In other cases one of highest priorities is to be compatible with 
existing setups.

> The second thing not to get the error message even if activated is simply 
> not so define 'pi_checkCHash' in your extensions - or let's better say set 
> it to false.
>
Ok, I will try, but I don't understand it. Let's say - was pi_base wrong 
whole the time with setting 'pi_checkCHash' to true ? Whats the reason for 
changing the default so it produces a lot of errors now ?

By thinking of this I feel at the same point as I was when starting coding 
for Typo3. Setting up cache in the right way seems to be a magic.
So I have one problem with understanding:
Cache is part of the page, so the page is cached. Even when the page has 
non-cached objects, they will not cashed.
But cHash is for the page, and the plugin doesn't know if page is cached, 
normally it is. So every link hast to build a cHash - this would be the 
'pi_checkCHash' =true

Now I feel like all I know about cache is falling down or isn't true and I'm 
very confused now.

vg  Steffen

> That's what I found out that far.
>
> -- 
> Kind regards,
> Franz Koch