Yeah, I am using it in getParameters() because within the context of
semantic search special page I cant use Parser::preprocessToDom() to
parse some of my config parameters. In this case I use some fallback
value for the special page. Otherwise, I think I had to use
Parser::parse() and I am not
Hey,
> It's in SMWParamFormat::doManipulation() where
SMWQueryProcessor::getResultPrinter() is called, but with only one
parameter, while the second parameter is defining the context e.g. whether
the query is coming from an special page. Default is special page, so the
context isn't set to inline
Here's how I suggest solving the problem:
{{#if: {{#ask:[[Category:Images]] [[Belongs to::{{PAGENAME}}]] [[Main::Yes]]
[[Image of::Portrait]]|?}}
| {{#ask:[[Category:Images]] [[Belongs to::{{PAGENAME}}]]
[[Main::Yes]]
[[Image of::Portrait]]|?}}
| {{#formlink: form
I have found the bug now doing some stack trace:
It's in SMWParamFormat::doManipulation() where
SMWQueryProcessor::getResultPrinter() is called, but with only one
parameter, while the second parameter is defining the context e.g.
whether the query is coming from an special page. Default is spec
Dear all,
I am planning to put up funding for a functionality that has been missing for a
long time: I'd like to be able to use the standard MW editor for Text fields in
Semantic Forms.
I know there are some other WYSIWYG editors that are supposed to work, but I'd
rather have something very s
Hi,
I am not the parser functions guru, but in my template for displaying images, I
use the following:
{{#if: {{{Diagramm1|}}}| [[Diagramm::Image:{{{Diagramm1|}}}| ]]
[[Image:{{{Diagramm1|}}}|thumb|800px|left|{{Datei:{{{Diagramm1|}]] |}}
You don't need this: {{Datei:{{{Diagramm1|} it j
