Last modified: 2010-05-15 15:48:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8807 - wiki_redirect Errors on Page Edits Following Upgrade to 1.9
wiki_redirect Errors on Page Edits Following Upgrade to 1.9
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
Macintosh Mac OS X 10.0
: High critical with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-01-28 14:40 UTC by Dennis
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Description Dennis 2007-01-28 14:40:38 UTC
Following an upgrade to 1.9, I can no longer edit my wiki pages. I get an error
that reads:

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:

    (SQL query hidden)

from within function "Article::updateRedirectOn". MySQL returned error "1146:
Table 'tewiki.wiki_redirect' doesn't exist (".

Under the Special:Version page I have listed:

MediaWiki: 1.9.0
PHP: 5.1.2
MySQL: 5.0.24a-standard-log

My Wiki allows me to SEE everything I've done before (300+ pages) but I can't
add any new content since the upgrade. Any ideas what I should do at this point?
Any help would be appreciated. Thanks.
Comment 1 Rob Church 2007-01-28 14:43:43 UTC
As I recall, there were some problems with the sequence of updates which have
been corrected in 1.9.1. Please upgrade to 1.9.1 and run the
maintenance/update.php script again, to see if the problem is fixed.

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