[TYPO3-dev] RealURL: bypass and lookupTable, missing feature?
Andreas Förthner
Andreas.Foerthner at netlogix.de
Thu Apr 20 13:53:44 CEST 2006
Hi,
I already posted this to the english list, but there nobody knew
anything about it. Now I have searched a bit in the sources an found out
that this just might not be possible. Here again the Problem:
I am configuring the RealURL Extension for my page. There I have some
Parameters for my own extension. These parameters can be existant on any
page, because the plugin could be everywhere. And it's also possible
that there are just a few of these parameters. Just to make this clear:
I am linking to some records in the database those records could be
associated to a subcategory or not, so the subcategory parameter is only
existant if the record is associated to one. Of course this shoul be
the same in the URL.
What I did was the configuration of those parameters as fixedPostVars.
This work so far very good, everything is mapped, but if there is one
parameter missing the URL gets an //. Meaning if one of the parameters
is there, all of the parameters defined are tried to get translated, if
there is one missing in the original url I get an empty one, ending in a
double slash.
I think the Problem is that there is no possibility to bypass an
parameter that is not in the database lookup. So there should be
something like the noMatch for the valueMap for the lookupTable. Once
the script runs into this elsif case the parameter is compiled in every
case. So if the DB lookup returns nothing (also because the parameter is
just not set in the original URL) the manipulated URL gets an empty
virtual pass, ending in those two slashes.
Or why are all parameters mapped even though they are not existant? Why
not add an additional if when filling the params Array, that checks if
the parameters is existant. If not this one should automatically bypassed.
Is there something speaking against such a behavior?
Greets
Andreas
More information about the TYPO3-dev
mailing list