Last modified: 2010-08-29 16:47:27 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 T26363, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24363 - rebuildall.php job fails with fatal error in SMW_SQLStore2.php
rebuildall.php job fails with fatal error in SMW_SQLStore2.php
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All Linux
: Normal major (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-13 12:17 UTC by Rob Challen
Modified: 2010-08-29 16:47 UTC (History)
1 user (show)

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


Attachments

Description Rob Challen 2010-07-13 12:17:08 UTC
Following these instructions:

http://www.mediawiki.org/wiki/Manual:Moving_a_wiki
http://lists.wikimedia.org/pipermail/mediawiki-l/2008-August/028294.html

resulted in a wiki where the pages all were reproduced, their history could be reviewed but had no displayable content but in them, and could not be edited. Presumably because of some breakage between the version numbering.

Calling a rebuildall.php or a SMW_refreshData.php on the migrated wiki does not seem to work. 

PHP Fatal error:  Call to a member function isValid() on a non-object in /usr/local/apache2/htdocs/informatics/extensions/SemanticMediaWiki/includes/storage/SMW_SQLStore2.php on line 776

Version details:
MediaWiki 1.15.1
PHP 5.3.0 (apache2handler)
MySQL 5.1.37
Semantic MediaWiki (Version 1.5.1.1)
Comment 1 David Gerard 2010-07-13 13:04:40 UTC
Note - I'm working with Rob on this one (I'm the sysadmin for the server we're trying to put it on). The MySQL is actually 5.0.77 and the PHP is 5.1.6, both the system packages from RHEL 5.5.
Comment 2 Rob Challen 2010-07-13 17:12:37 UTC
The root cause looks like it is a Latin1 / UTF8 encoding mix up during the database dump (ahem). Will try and confirm whether the problem persists when we have corrected this.
Comment 3 Markus Krötzsch 2010-08-29 16:47:27 UTC
The root cause for the problem showing up, however, was a wrong check in SMW: it was ensured that the value was not "null" but it should have been checked that it was not "false". So the above error is now fixed (hence the topic of this bug, which I close now). The fix will be released in SMW 1.5.2.

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


Navigation
Links