Last modified: 2009-11-02 19:23:15 UTC
Catchable fatal error: Argument 1 passed to SMWResultArray::SMWResultArray() must be an instance of SMWWikiPageValue, array given, called in /.../httpdocs/extensions/SemanticDrilldown/specials/SD_BrowseData.php on line 954 and defined in /.../httpdocs/extensions/SemanticMediaWiki/includes/storage/SMW_QueryResult.php on line 182 When trying to open pages like Spezial:BrowseData from Semantic Drilldown Catchable fatal error: Argument 2 passed to SMWSQLStore2::getPropertyValues() must be an instance of SMWPropertyValue, null given, called in /.../httpdocs/extensions/SemanticMediaWiki/includes/storage/SMW_QueryResult.php on line 268 and defined in /.../httpdocs/extensions/SemanticMediaWiki/includes/storage/SMW_SQLStore2.php on line 339 When trying to open page with semantic Query http://www.wecowi.de/view/WeCoWi:Attribut
The API of SMWResultArray has changed in SMW 1.5, and SemanticDrilldown is not yet updated to be compatible with these changes. This is normal, since SMW 1.5 is not released yet and it will take some time until all extensions are compatible. Please read the manual of SemanticDrilldown to find out which version of SMW you can use with it right now. Explanation of changes in SMW: query result now are no longer pre-fetched but rather pulled from the store when needed. This eliminates the need ot have all data for a complex and very long query output in memory at the same time. To enable this, some changes had to be made in the infrastructure, though all get-functions are still the same (so all printers work as before, where some can be implemented more efficiently using the new getResults() ). I am reassigning this bug to SD, but I add the warning that some additional changes in SMWResultArray may happen in the next week. I was not aware that any extension did actually access this part of SMW directly, or I would have sent out a note to the developers.
A fix to handle the changes in SMW 1.5 is now checked in to the version of Semantic Drilldown on SVN. By the way, I don't know how the new SMW code works, but it's amazing!
This was fixed in version 0.6.1 - the handling still isn't perfect, but it (I believe) no longer leads to any error messages.
