Last modified: 2010-08-30 14:55:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19754, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17754 - Use of $wgParser in query printers not always allowed
Use of $wgParser in query printers not always allowed
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-02 12:50 UTC by Markus Krötzsch
Modified: 2010-08-30 14:55 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Markus Krötzsch 2009-03-02 12:50:39 UTC
Quoting a bug report by Stephan Robotta:

When calling the function SMWQueryProcessor::getResultFromQueryString() with the parameter SMW_OUTPUT_HTML a fatal error ocurres in the parser. This happens when a ask query is done and a table with parameter intro is requested like in:

 {{#ask: [[Category:Content]] 
 | format=table
 | link=all 
 | intro=content in my wiki
 | mainlabel=title
 |}}

At the moment this would happen in the Query Interface of SMW+ only. Within
pages of the wiki, the query output is rendered to wiki text which then later
is rendered to html.

The parser handling in line 161ff in SMW_QueryPrinter.php is needed as well in
the parts for mIntro and mOutro shorly afterwards.
Comment 1 Markus Krötzsch 2010-08-30 14:55:35 UTC
This bug seems to have been fixed since its report, or at least I am unable to reproduce it now. Please re-open with new details if there is still a way to cause this problem.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links