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 special page, so the context isn't set to inline for the result printing!
Daniel Daniel Werner wrote: > Hi, > > I am just programming some changes to one of my SMW result formats, and > was wondering about some functionality being broken. I figured out this > is due to my update to SMW 1.6.2 and it seems like > SMWResultPrinter::$mInline is always false for inline queries! > > I don't know where the object is created and the $inline parameter is > given to the constructor, but the but must be there since there isn't > anything wrong with the constructor itself and it worked fine in SMW 1.6.1 > > Can anyone confirm this perhaps or even knows where the bug lays? > > Daniel ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
