Last modified: 2010-11-12 08:58:21 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 T27890, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25890 - Global "turn new features off" for Vector Skin is not working
Global "turn new features off" for Vector Skin is not working
Status: RESOLVED DUPLICATE of bug 25029
Product: MediaWiki extensions
Classification: Unclassified
UsabilityInitiative (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Trevor Parscal
http://ie.wikipedia.org/w/index.php?t...
: crosswiki
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-12 02:59 UTC by TeleComNasSprVen
Modified: 2010-11-12 08:58 UTC (History)
5 users (show)

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


Attachments

Description TeleComNasSprVen 2010-11-12 02:59:50 UTC
When I go to a Wikimedia wiki, say ie:w for instance, and I use the checkbox under the question "Do you want the features turned off globally?" when entering Special:UsabilityInitiativePrefSwitch in the url above, and try to turn the features off, it gives me an error message:

<blockquote>
Database error
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 "Database::begin". Database returned error ": ".
</blockquote>

The result is that the Vector skin is turned off <em>only for that wiki</em>, and others like or:w still retain their vector skin whenever I visit that site. Is it possible to fix this error?
Comment 1 p858snake 2010-11-12 08:56:49 UTC

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

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


Navigation
Links