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

[Ernesto Baschny [cron IT]]

Elmar HInz wrote: on 06.03.2007 12:39:

>> 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.
> 
> Yes. But if you want to build an extension that can be used as USER or
> USER_INT alternatively, you need to set pi_checkCHash to true for them.
> Now you run into problems with this flexible type of extensions.
> 
> But for lib/div we will surly find a way to detect, if it is a USER or
> USER_INT. Then we can set reqCHash automatically in the libraries
> controller class.

Just an add-on for this comment. If you have a single entry-point for
your plugin that handles USER and USER_INT, you just have to set

	var $pi_checkCHash = FALSE;

and then call

	$GLOBALS['TSFE']->reqCHash();

directly depending on the situation.

The pi_checkCHash variable was just added as a convenience for extension
developers of USER-plugins. In this case, the reqCHash() check will
happen before the call to "main" (in the constructor of pi_base), so
that your plugin won't even be called if this check fails (with
pageNotFoundOnCHashError=1).

Cheer,
Ernesto