This, in a way, contradicts left-to-right-inside-out parsing. For example,
given a table
| *attr* | value=%FOO{exclude="<regex>"}% |
and given that
<regex>
contains a pipe (|) in it. Then this table will
display the table up to the pipe and
%FOO...%
will not be expanded
anymore. I would have expected FOO to be processed before generating the
table markup.
MD
Can you give a real-life example?
My naive try works as expected:
|
foo |
WebChanges
WebSearch
WebStatistics |
...and that's what I would expect from the code. The only exceptions I could think of are undefined TWiki variables, or those plugin variables who
deliberately are expanded no earlier than in
postRenderingHandler
.
--
HJ
Oh - forget what I just said. It works only if the search returns exactly one hit.
Back to status New...
--
HJ
But yet, it's still a RTFM and not a bug.
| *foo* | %SEARCH{"|" format="$topic " nonoise="on" topic="Web*" separator=" "}% |
yields
If done
correctly,
%SEARCH{}%
is expanded before the table, as I would have expected. So again - do you have an example for me to debug?
(Waiting for Feedback - and my apologies for the confusion)
--
HJ
I believe that it was my initial report of this that prompted Michael to post the bug and let me clarify a few points:
- I was referring to variables within TWikiForms, not TWiki tables.
- The specific problem I observerd was when trying to use a bar ("|") within a regex search.
- The table within the topic that defined the TWikiForm displayed fine. The problem was when the form was used by a topic. Then the bar broke the search and consequently, the first part of the search definition was displayed in the TWikiForm. I don't know how to demostrate this here.
LB
I don't believe this is a bug; it's a proposal for a behaviour change, and as such must be disscussed in Codev before re-opening this report (if necessary). Setting to no action
CC