please help...
I have the configuration below.
With this configuration postVars do not work.
If I remove "'noMatch' => 'bypass'," then the fixedPostVars does not work.
what is wrong?
'fixedPostVars' => array(
'_DEFAULT' => array (
array( 'GETvar' => 'tx_d
Hi!
Vahan Amirbekyan wrote:
> I have the configuration below.
> With this configuration postVars do not work.
> If I remove "'noMatch' => 'bypass'," then the fixedPostVars does not work.
> what is wrong?
Nothing is wrong. This is how it should work.
> 'fixedPostVars' => array(
>
Dmitry,
first I want to let you know how much i appreciate your prompt
responses. Thank you.
pls see here my configuration below.
This is how I read it:
fixedPostVars are not mandatory. And if not found then the segment
should be re-applied to the stack.
Example:
http://domain/pagename/fixedpost
Hi!
Vahan Amirbekyan wrote:
> This is how I read it:
> fixedPostVars are not mandatory. And if not found then the segment
> should be re-applied to the stack.
This is what "noMatch=bypass" does. If it is not specified, than the segment is
assumed to be a fixedPostVar.
fixedPostVars should be ap
hi again,
your suggestion is exactly what I end up doing but I do not like it as
it limits my options.
Dmitry Dulepov wrote:
> Hi!
>
> Vahan Amirbekyan wrote:
>> This is how I read it:
>> fixedPostVars are not mandatory. And if not found then the segment
>> should be re-applied to the stack.
>
Hi!
Vahan Amirbekyan wrote:
> your suggestion is exactly what I end up doing but I do not like it as
> it limits my options.
There are always limits. fixedPostVars are not really supposed to use _DEFAULT
:)
--
Dmitry Dulepov
In TYPO3 blog: http://dmitry-dulepov.com/article/artificial-intellige
yes, sure, understood.
I just did not get it from the doc. Perhaps it is not that clear spaced.
thanks
Dmitry Dulepov wrote:
> Hi!
>
> Vahan Amirbekyan wrote:
>> your suggestion is exactly what I end up doing but I do not like it as
>> it limits my options.
>
> There are always limits. fixedPost
