Last modified: 2009-11-03 16:50: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 T23098, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21098 - Error with inverse nary properties.
Error with inverse nary properties.
Status: RESOLVED FIXED
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-10-11 15:02 UTC by David Severwright
Modified: 2009-11-03 16:50 UTC (History)
0 users

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


Attachments

Description David Severwright 2009-10-11 15:02:26 UTC
When trying to do inverse queries on nary properties I get the following error:
Fatal error: Call to undefined method SMWWikiPageValue::acceptQuerySyntax() in .../extensions/SemanticMediaWiki/includes/SMW_QueryParser.php on line 345
This happens both with inline queries and Special:Ask

The nary property in question had [[has type::page,number,number,number]], it works fine for properties with just a single type.
It seems to only error when the inverse property is compared against a specific value, using a wildcard makes no error, but also finds no results.

Versions:
MediaWiki  r57640
SMW        r56952
PHP        5.2.10 (cgi)
MySQL      5.0.81-community
It's running on a fairly standard cpanel server.

An example of this can be seen with the query [[-TestNary::NaryTest]] on sandbox.semantic-mediawiki.org.
Comment 1 Markus Krötzsch 2009-11-03 16:50:35 UTC
Right. Queries that use inverse properties of types other than Page are not supported by SMW (displaying data values as query results is not properly supported in many places). But of course this should not lead to an error. This has been corrected in SVN now.

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


Navigation
Links