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

[Franz Koch]

Hi Steffen,

>> 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.

I don't understand that either - so welcome to the club - just figured it out in my last extension for a customer. I mean - now it is not in any way possible to build cached form results. Let's take f.e. tt_news (as it is common known) with a category selector over a form dropdown. It is not possible to cache the pages requested by the dropdown - even if told so, because you can't append the correct cHash for forms - or did I miss something about that? Before at least the page itself was cached if I'm right.

-- 
Kind regards,
Franz Koch