Page MenuHomePhabricator

Enabling SemanticForms extension generates a database query error
Closed, InvalidPublic

Description

Author: duongxvu

Description:
When the SemanticForms extension is enabled, no content isn’t being retrieved at all from the database, and all that is displayed is this error message:

"A database query error has occurred. This may indicate a bug in the software."

When using the PHP debugging tools, these notices appear as well:

• "Notice: Uncommitted DB writes (transaction from DatabaseBase::query (WikiPage::pageData)). in /usr/opspedia/gsddtovsdvap014/var/www/html/wiki/includes/db/Database.php on line 3944"

• "Notice: DB transaction callbacks still pending (from Title::invalidateCache). in /usr/opspedia/gsddtovsdvap014/var/www/html/wiki/includes/db/Database.php on line 3953"

For what it's worth, we are upgrading our MediaWiki installation from version 1.17 to 1.22, and no other extensions besides SemanticMediaWiki have been installed or enabled.


Version: REL1_22-branch
Severity: blocker

Details

Reference
bz61963

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:58 AM
bzimport set Reference to bz61963.

Please add "$wgShowSQLErrors = true;" to your LocalSettings.php, so you can see the actual SQL error.

duongxvu wrote:

I've done that, and received new messages, which I've copy-pasted below.


A database query error has occurred. This may indicate a bug in the software.

Query:
SELECT smw_id,smw_sortkey FROM mw_smw_object_ids WHERE smw_title = 'August_sdnotices' AND smw_namespace = '0' AND smw_iw = '' AND smw_subobject = '' LIMIT 1

Function: SMWSql3SmwIds::getDatabaseIdAndSort

Error: 1146 Table 'gsddtovsdvap014.mw_smw_object_ids' doesn't exist (10.77.8.118)

It looks like you didn't update, or didn't fully update, the database after upgrading SMW - you should run update.php, or run the update from Special:SMWAdmin.

duongxvu wrote:

Running the update from Special:SMWAdmin worked! We had previously tried running update.php several times, and I remember thinking about how odd it was that the update script didn't initialize or upgrade any tables at all at the time.

Thanks very much for your time. I'll close this ticket as resolved now.

Cool! I'm changing this to "invalid", though, just for record-keeping purposes.