Last modified: 2011-11-30 16:15:19 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 8862 - Database error: MySQL returned error "1054: Unknown column 'ipb_anon_only' in 'where clause'
Database error: MySQL returned error "1054: Unknown column 'ipb_anon_only' in...
Status: RESOLVED DUPLICATE of bug 8641
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.9.x
PC Windows XP
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://www.projectbob.org/wiki
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-02 20:14 UTC by Jason Norris
Modified: 2011-11-30 16:15 UTC (History)
0 users

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


Attachments

Description Jason Norris 2007-02-02 20:14:56 UTC
I recently began getting a Database error when I try to edit pages with created
accounts.  The error only comes up when I am logged in as my SysOp account or
other people are logged in as well.

Anon editing works fine with no problems.  Here is the error I'm getting:

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

    SELECT * FROM `wiki_ipblocks` WHERE ipb_address = '76.5.175.172' AND
ipb_auto = '1' AND ipb_anon_only = '0' 

from within function "Block::load". MySQL returned error "1054: Unknown column
'ipb_anon_only' in 'where clause' (wiki.projectbob.org)".

This only started happening recently.  I've tried to restore the database to a
previous date (the last known time I edited) but to no avail.  Any help is
appreciated.
Comment 1 Rob Church 2007-02-02 20:33:23 UTC
Upgrade to 1.9.1 and re-run the update script; there were some bugs in the
update order for the 1.9.0 upgrade, which cause this problem.
Comment 2 Brion Vibber 2007-02-02 21:37:25 UTC

*** This bug has been marked as a duplicate of 8641 ***

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


Navigation
Links