Item13871: Literal search for SEARCH macro is incorrectly parsed.
Priority: Normal
Current State: Confirmed
Released In: 2.2.0
Target Release: minor
Applies To: Engine
Component: SEARCH
Branches:
Literal search for %SEARCH{ picks up the 2nd argument as the search string.
%SEARCH{
"%SEARCH{"
type="literal"
scope="text"
web="Tasks"
excludetopic="Item*"
casesensitive="on"
order="topic"
limit="100"
pager="off"
}%
results in a search on
type=literal
%SEARCH{
"
Number of topics: 0
Removing the { from the search string, it then works.
--
GeorgeClark - 26 Nov 2015
I'm not really certain if this is a bug, or just an artefact of our inside-out left-right expansion. The "inner macro" is correctly formed. Just because the macro is inside quotes won't stop it from being expanded.
%SEARCH{"
type="literal"
scope="text"
web="Tasks"
excludetopic="Item*"
casesensitive="on"
order="topic"
limit="100"
pager="off"
}%
Deferring for someone who knows, or 2.2.
--
GeorgeClark - 06 Jan 2016