[TYPO3-dev] realURL: new patch for bypassing non-existant GETVARS

[Andreas Förthner]

Andreas Förthner schrieb:
> Hi,
> 
> finally I got my patch working for the realURL extension. The patch 
> bypasses non-existant GETVARS. This is the detailed description from my 
> feature request in the bugtracker: (http://bugs.typo3.org/view.php?id=3313)
> 
> 
> I have uploaded a new patch for this Problem 
> (class.tx_realurl.php.second.diff). You have to activate it with a new 
> config option. Set 'bypassIfAbsent' => 1 in your localconf. You can do 
> it for every GETVAR independent from eachother. Set the entry on the 
> same level as 'noMatch' or 'lookUpTable' is defined.
> 
> Then the behavior is now as follows:
> 
> - If a parameter is not existant it is bypassed in the URLencode
> - This applies not only for lookUpTables it works also for normal 
> valueMaps, of course then the noMatch property must not be set. If you 
> need a default value use valueDefault instead.  Is there anything else 
> where the feature would be nice to have? Just tell me.
> 
> Then the decoding:
> 
> This is a bit a Problem, because the system doesn't know which one of 
> the parameters has been bypassed. For this reason it behaves as follows 
> (I think it's the same as noMatch => bypass works):
> 
> - We are checking if there is a value in a valueMap. If not an noMatch 
> is not set, we are looking in a userfuc (this has not changed) then we 
> look in the lookup table. If we still couldn't decode the parameter, we 
> bypass this one and proceed with the next in the postVarSet.
> 
> I didn't check it with preVars. I think the same functions are used 
> there, so it might work. If not tell me  then I'll try to realize this.
> 
> For me it works great, please test it as much as possible and if there 
> are no bugs in it, it would be great to see it in the next official 
> release of realurl.
> 
> Have a nice day
> 
> Andreas

Hi,

I know Kasper vetoed the patch, but he relied on the first one that 
didn't work and where it wasn't possible to disable/enable it. Please 
rethink the whole thing and perhaps it is a nice feature that could be 
implemented...

Greets

Andreas