Last modified: 2008-12-05 19:05:24 UTC
After upgrading SMW to version 1.2.1, I could update the base SMW_refreshData.php without problem. But after configuring the SPARQL endpoint (described on http://semantic-mediawiki.org/wiki/Help:SPARQL_endpoint ), I cannot anymore run SMW_refreshData.php (yes, I initialized the database through wiki/Special:SMWAdmin) I get the following error: # php SMW_refreshData.php Refreshing all semantic data in the database! Processing pages from ID 0 to ID 82 ... Fatal error: Call to a member function find() on a non-object in /var/www/mediawiki_svn/extensions/SemanticMediaWiki/includes/storage/SMW_RAPStore.php on line 340 (the database seems to work, as I can create a new property and I see it in the 'statements' mysql table).
Denny maintains the RAP store, maybe he can help. Anyway, semantic-web.org runs on SMWRAPStore2 and I use refreshData there regularly. Maybe you should try switching to RAPStore2 anyway (the SQL2 backend is better). To do that, follow the migration steps as explained on http://semantic-mediawiki.org/wiki/Help:Installation_1.2#Upgrading_to_the_new_store
After svn updating to the latest version: Semantic MediaWiki (Version 1.4b-SVN) I'm consistently seeing this error even when using RAPStore2 php runJobs.php 2008-10-08 12:50:11 0 SMWUpdateJob 7300001 Fatal error: Call to a member function find() on a non-object in /root/dev/phase3/extensions/SemanticMediaWiki/includes/storage/SMW_RAPStore2.php on line 273
And now it has appeared again when trying to save a page after making an edit from the webbrowser. Fatal error: Call to a member function find() on a non-object in /root/dev/phase3/extensions/SemanticMediaWiki/includes/storage/SMW_RAPStore2.php on line 273 For the moment I've commented out #$smwgDefaultStore = "SMWRAPStore2"; aware that this means my RAP will begin to get out of date with wiki content.
I still do not see Denny commenting on this ... Anyway, it seems likely that there will be better RDF storage binding in upcoming SMWs. RAP, in particular, will probably vanish, since it is no longer actively developed. Maybe Denny could provide some details.
I've continued to stay up to the recent releases, and did find all issues happily gone since the recent 1.4 release.
