Last modified: 2013-04-13 19:49:08 UTC
I've tried a couple of times to turn off the new features globally by clicking the checkbox in the form. All the times, after some seconds, I get an error message: Ha ocurrido un error de sintaxis en una consulta a la base de datos. Esto puede indicar un error en el software. La última consulta a la base de datos que se intentó fue: (Consulta SQL oculta) dentro de la función "Database::begin". El error devuelto ": ". My preferences are in Spanish, a rouge translation might be: An error pending a database query has occured. This might indicate a sofware error. The last database query attempted was: (SQL query hidden) inside the function "Database::begin". Error received was ": ". As a result, the features can not be globally dissabled as desired. Thank you for your time. - DF.
*** Bug 25078 has been marked as a duplicate of this bug. ***
Screenshot from a dewiki user: http://img829.imageshack.us/img829/8497/wikisqlerror.png Full error message: "TABLE PRIMARY KEY INVALID".
Ironic, isn't it. A form giving feedback about the usability has a bug in it which inhibits its usability :) I am also getting this at en.wp, so I'll be watching it too.
in the Special:UsabilityInitiativePrefSwitch, when using the "prefswitch-survey-global[]" setting. It can be reproduced every time so far when being in Vector and trying to 'take me back'. -- 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 ": ". -- http://i.imgur.com/mFmz9.png Page loads for a couple of seconds then shows the above error: Server load html comment: <!-- Served by srv159 in 35.660 secs. -->
Hm... I wish I didn't do the above Somehow it DID switch me on all wikis to Monobook (albeit it did show the previously reported error still). But... how do I switch back ? Will this become an option aswell (after this bug is fixed).
I confirm that the feature is still broken. I've tried it two or three times but today I went to en.wikisource and I had Vector enabled, but there was the "try new features" button instead of the "take me back" one. So I've tried again from the just newly created bjn.wikipedia.org: same error (Database::begin, «Can't connect to MySQL server on '10.0.6.38' (4) (10.0.6.37)») and <!-- Served by srv272 in 13.839 secs. -->.
Changing to Low/Major because the feature isn't working (almost) at all, but it's low priority (you can live without it and it's only for a small subset of users).
By the way, the third/fourth attempt mentioned above didn't work either; I still had Vector on fr.source.
*** Bug 25890 has been marked as a duplicate of this bug. ***
(In reply to comment #7) > Changing to Low/Major because the feature isn't working (almost) at all, but > it's low priority (you can live without it and it's only for a small subset of > users). Switch back to normal. Now I even get an error without checking the box for globally dissabling the new features. It is annoying, and none of my global scripts for maintenance / steward work are working because of the skin update. I also confirm c6. I have the new features activated in some wikis but the "take me back" button isn't shown.
(In reply to comment #10) > I have the new features activated in some wikis but the > "take me back" button isn't shown. It's been disabled since some time ago, but the special page is still available (with the same errors). It was worse before because you had a "try new features" button even when you were using Vector. ;-)
Moving relation to bug 14950 from Block to Depends on.
*** Bug 27293 has been marked as a duplicate of this bug. ***
*** Bug 27304 has been marked as a duplicate of this bug. ***
Now it gives random errors, probably because some table was deleted or not created on some new wikis test2.wikipedia.org: «from within function "PrefSwitchSurvey::save". Database returned error "1146: Table 'test2wiki.prefswitch_survey' doesn't exist (10.0.6.49)"». te.wikisource.org: «దీనిని "PrefSwitchSurvey::save" అనే ఫంక్షను నుండి వచ్చింది. డేటాబేసు ఇచ్చిన లోప-సమాచారం "1054: Unknown column 'pss_user_text' in 'field list' (10.0.6.49)"».
I assume this is why http://en.wikipedia.org/wiki/Special:PrefSwitch currently displays Invalid message parameter Backtrace: #0 /usr/local/apache/common-local/php-1.19/includes/Message.php(505): Message->extractParam(Array) #1 /usr/local/apache/common-local/php-1.19/includes/Message.php(373): Message->replaceParameters('Remember that w...', 'before') #2 /usr/local/apache/common-local/php-1.19/includes/Message.php(431): Message->toString() #3 /usr/local/apache/common-local/php-1.19/includes/OutputPage.php(3435): Message->plain() #4 /usr/local/apache/common-local/php-1.19/includes/OutputPage.php(3423): OutputPage->addWikiMsgArray('prefswitch-jswa...', Array) #5 /usr/local/apache/common-local/php-1.19/extensions/PrefSwitch/SpecialPrefSwitch.php(262): OutputPage->addWikiMsg('prefswitch-jswa...', 'Markhurd', 'monobook', Array) #6 /usr/local/apache/common-local/php-1.19/extensions/PrefSwitch/SpecialPrefSwitch.php(171): SpecialPrefSwitch->render('main') #7 /usr/local/apache/common-local/php-1.19/includes/SpecialPageFactory.php(476): SpecialPrefSwitch->execute(NULL) #8 /usr/local/apache/common-local/php-1.19/includes/Wiki.php(263): SpecialPageFactory::executePath(Object(Title), Object(RequestContext)) #9 /usr/local/apache/common-local/php-1.19/includes/Wiki.php(593): MediaWiki->performRequest() #10 /usr/local/apache/common-local/php-1.19/includes/Wiki.php(503): MediaWiki->main() #11 /usr/local/apache/common-local/php-1.19/index.php(58): MediaWiki->run() #12 /usr/local/apache/common-local/live-1.5/index.php(3): require('/usr/local/apac...') #13 {main} when I'm logged in.
Actually that fatal looks like another bug, I suppose because you're already using monobook. I've just tried Special:PrefSwitch on a wiki I've never visited before and it's at least displayed correctly.
Lowering priority as the special page is disabled now.
Trevor: This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED. In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help! [assigned>=1y]
I'm closing this since the feature that gave this error no longer exists as far as I can see in the special pages index, so there's nothing to fix. Best regards.
