Last modified: 2010-05-15 15:41:09 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 6959 - Database syntax error loading SpecialNewImages
Database syntax error loading SpecialNewImages
Status: RESOLVED DUPLICATE of bug 6956
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC Windows XP
: Normal critical (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-08-09 15:18 UTC by James Mitchell
Modified: 2010-05-15 15:41 UTC (History)
0 users

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


Description James Mitchell 2006-08-09 15:18:05 UTC
1st off my system is running

MediaWiki: 1.7.1 
PHP: 5.1.4-0.1 (cgi-fcgi) 
MySQL: 5.0.22-Debian_3-log 

I get the following error when loading the Special:Newimages (Gallery of new 

"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 "wfSpecialNewImages". MySQL returned error "1064: You 
have an error in your SQL syntax; check the manual that corresponds to your 
MySQL server version for the right syntax to use near ') WHERE ug_group IS 
NULL ORDER BY img_timestamp DESC LIMIT 1' at line 1 (localhost)"."

Can anyone help as this is a important feature for my wiki site
Comment 1 Jimmy Collins 2006-08-09 21:38:31 UTC

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

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