Wikitech-l December 2013

wikitech-l@lists.wikimedia.org

125 participants
119 discussions

Preferences not being saved on MW 1.22 when using shared databaes
by Jack Phoenix 08 Dec '13

08 Dec '13

Hi all, We at ShoutWiki (http://www.shoutwiki.com/) updated from MediaWiki 1.21 to MediaWiki 1.22 earlier today. The upgrade went mostly smoothly, save for some smaller issues, but afterwards we ran into one major issue: user preferences are not being saved. When a user updates their preferences via [[Special:Preferences]], the special page claims that the changes were saved correctly, but this is not the case. It seems that the only entries saved to user_properties are 'variant' and 'watchlisttoken'. Setting a preference via eval.php seems to work: > $u = User::newFromName( 'Jack Phoenix' ); $u->setOption( 'signature', 'set via a CLI script' ); $u->saveSettings(); $dbw = wfGetDB( DB_MASTER ); $dbw->commit(); echo $u->getOption( 'signature' ); set via a CLI script > $u = User::newFromName( 'Jack Phoenix' ); echo $u->getOption( 'signature' ); set via a CLI script ...but this is an optical illusion. Visiting any wiki page seems to reset the preferences to their defaults. We've diffed /includes/specials/SpecialPreferences.php, /includes/Preferences.php and /includes/User.php but nothing overly suspicious has come up. ShoutWiki uses quite many extensions (see, for example, http://www.shoutwiki.com/wiki/Special:Version), some of which are yet to be released, but as far as I'm able to see, none of these mess with the preferences stuff. Unlike the defaults in /includes/DefaultSettings.php, the user_properties table is _not_ shared on ShoutWiki. Our essential configuration files are also published online at http://www.shoutwiki.com/conf/ . Needless to say that this bug doesn't seem to manifest itself at least on my local development setup, only on production. Anyone got any clues as to what might be causing this and how to fix it? If we're not able to fix this soon, we're forced to roll back the 1.22 change, because our users are rather fond of their preferences, obviously. Thanks and regards, -- Jack Phoenix MediaWiki developer

1 1

MWHttpRequest not work for mwv1.22
by Sen 08 Dec '13

08 Dec '13

i glad the new v1.22 is come out,but after upgrade,my code is not function any more,what happen in here $authUrl = "xxxx datamarket.accesscontrol.windows.net/v2/OAuth2-13/ "; $options = array(); $options['method'] = 'POST'; $options['timeout'] = $this->config['timeout']; $options['postData'] = array( 'grant_type' => "client_credentials", 'scope' => "http://api.microsofttranslator.com", 'client_id' => $clientID, 'client_secret' => $clientSecret ); $options['postData'] = $params; $req = MWHttpRequest::factory($authUrl, $options); $status = $req->execute(); after upgrade mw 1.22 i got this error [error] PHP Warning: curl_setopt_array() [<a href='function.curl-setopt-array'>function.curl-setopt-array</a>]: Array keys must be CURLOPT constants or equivalent integer values in ...

1 1

MediaWiki 1.22.0 released
by Markus Glaser 07 Dec '13

07 Dec '13

Dear all, I am happy to announce the availability of the first stable release of the new MediaWiki 1.22 release series. MediaWiki 1.22 is a large release that contains many new features and bug fixes. This is a summary of the major changes of interest to users. You can consult the RELEASE-NOTES-1.22 file for the full list of changes in this version. Our thanks to everyone who helped to improve MediaWiki by testing the release candidates and submitting bug reports. == What's new? == MediaWiki 1.22 includes all changes released in the smaller 1.22wmfX software deployments to Wikimedia sites. === Anti-spam and countervandalism improvements === We're improving countervandalism and anti-spam features: * The patrolling system has been improved to make the "mark as patrolled" link available on any patrollable page or revision, without having to go to Special:RecentChanges or Special:NewPages. It is no longer necessary to look up the "rcid" URI parameter from these special pages. (Bug 15936) * Extension:SimpleAntiSpam, a small but harmless shield against the simplest forms of spambots, has been merged into core. ===Editing improvements=== * When comparing revisions in the history or when previewing changes while editing, "(No difference)" is now shown in place of a diff when the revisions are identical. (Bug 14431) * After a successful edit, the confirmation message "Your edit was saved." is now shown. Formerly a separate extension (Extension:PostEdit), this feature is now part of the core software. (Bug 48276) ===Upgrades to Vector and other skins=== The old Vector extension has been merged into core, and the extension has been discontinued. The new version includes several improvements to both the Vector skin and cross-skin features. (Bug 45051) If you were previously using the Vector extension, you must uninstall it (the extension, not the skin) before upgrading to 1.22. All skins: * Section edit links are now displayed next to their respective headings rather than along the opposite side of the page. (Bug 41729) * Lists of templates and categories used on the page, displayed below the edit form, are now collapsible. The area with license information, edit summary, and related functionality below the edit field has received a minor graphical lift. (Bug 43689) * An "edit warning" is now displayed when the user attempts to leave the edit page with unsaved changes, on browsers supporting dialogs. * Vector skin only: ** Navigation menu subsections are now collapsible. ** Page tabs can now dynamically fold into a dropdown menu when the browser window isn't wide enough to fit them. ===Support for Composer=== The Composer PHP dependency manager can now be used to install some extensions. It solves many common problems, including finding where to download an extension, resolving all of its dependencies and libraries, and selecting the right versions. Most MediaWiki extensions do not currently support Composer, but this is expected to change. ==Upgrade notices for MediaWiki administrators== As with every release, there are some routine maintenance and upgrade tasks that go beyond the primary installation process. ===PHP JSON extension now required=== Though the minimum PHP version is still 5.3.2, MediaWiki now requires either the native JSON extension or the pecl-json-c fork. Most servers already have this PHP extension installed and enabled. However, if you administer your own server, and the MediaWiki installer says you don't have this extension: * If you compiled PHP yourself with the --disable-all configure option, you may have to recompile with --enable-json. * On Red Hat or CentOS, check for the line extension=json.so in /etc/php.ini or /etc/php.d/json.ini. * Ubuntu 13.10, Fedora 19, and other recent Linux distributions package pecl-json-c separately, under names such as php5-json (Ubuntu universe) and php-pecl-jsonc (Fedora). They no longer include the original JSON extension because of licensing concerns. === Several ancient skins removed === On April 1, 2013, several ancient skins were removed from core (not an April Fools' joke): Chick, Classic, MySkin, Nostalgia and Simple. Nostalgia was the phase I/UseModWiki-like skin, and Classic was the main skin before the introduction of the default MonoBook in MediaWiki 1.3 on May 22, 2004. Dating back to February 2002 both skins existed over a year before MediaWiki got its name. === Blank system messages must be deleted === Blanking a system message (editing it on wiki to remove all content) will no longer restore the default value for the message, but instead make it show as an empty string in the interface (fixing Bug 14176, "Add ability to disable MediaWiki messages"). If you have blank messages on your wiki (check Special:AllMessages), you must delete them unless you want them to display as empty. ===Protection rights usage has changed=== A new setting ($wgCascadingRestrictionLevels) was added for enabling cascading protection for protection levels other than "Allow only administrators" (Bug 47617). Shortly afterward, the way the "editprotected" and "autoconfirmed" rights work was changed. In particular, the "autoconfirmed" right is now only used for rate limiting, not page protection. If your wiki has custom user groups with the "autoconfirmed" right, you may need to grant those groups the new "editsemiprotected" right when you upgrade. ===Special:Disambiguations has been removed=== Special:Disambiguations, a page that listed "Pages linking to disambiguation pages", has been removed (Bug 35981). If your wiki used this feature, consider using Extension:Disambiguator. Switching to the new extension is easy and generally only requires a small change to a single template. === Bundled extensions === Newly bundled for 1.22: * SimpleAntiSpam Full release notes: https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.22.0/RELEASE-NOTES-1.… https://www.mediawiki.org/wiki/Release_notes/1.22 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0.tar.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0.tar.gz.sig Public keys: https://www.mediawiki.org/keys/keys.html ---- Markus (mglaser)

6 6

MessageBuilder interface
by Jeroen De Dauw 07 Dec '13

07 Dec '13

Hey, A while back I created a properly segregated interface for turning message keys into messages. Since I've seen someone create almost the exact same thing, and now ended up needing such an interface in another project as well, I decided to put this into its own little library. https://github.com/JeroenDeDauw/i18n At this time, only msgText is exposed in the general interface, as this is the only thing I've needed so far. This can easily be extended for other use cases though. Just released version 0.1 of this library, which is fully tested, and is installable via Composer. Hope this is of use to some people, and of great amusement to those who do not understand interface segregation and IoC. Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 --

1 0

Italian Wikipedia complements search results with Wikidata based functionality
by Gerard Meijssen 06 Dec '13

06 Dec '13

Hoi, The Italian Wikipedia is the first project where people who use search will find results added from Wikidata. As you may know, Wikidata knows has more items with a label in a language than a Wikipedia has articles. With the Wikidata based functionality people will gain several functionalities that are new to them - a link to Commons categories for a subject - a link to Wikipedia articles in other languages - a link to the Wikidata item - visualisation care of the "Reasonator" When there are multiple items found in the search request, disambiguation will be provided based on the statements available on the items. Obviously as more labels are available in a language for statements, the experience will improve. This is a really exciting new development and I want to thank Magnus and Nemo for making it possible. I hope and expect that many Wikipedias will follow the example of the Italian Wikipedia. Particularly the smaller Wikipedias have much to gain from this new functionality. Thanks, GerardM

9 17

Language Engineering IRC Office Hour on December 11, 2013 (Wednesday) at 1700 UTC
by Runa Bhattacharjee 06 Dec '13

06 Dec '13

[x-posted] Hello, The Wikimedia Language Engineering team will be hosting an IRC office hour on Wednesday, December 11, 2013 between 17:00 - 18:00 UTC on #wikimedia-office. (See below for timezone conversion and other details.) We will be talking about some of our recent and upcoming projects and then taking questions for the remaining time. Questions and any other concerns can also be sent to me directly before the event. See you there! Thanks Runa === Event Details === What: WMF Language Engineering Office hour When: December 11, 2013 (Wednesday). 1700-1800 UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131211T1700 Where: IRC Channel #wikimedia-office on FreeNode -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation

1 0

1.22.0rc3 ready for download
by Mark A. Hershberger 06 Dec '13

06 Dec '13

We've put together RC3 for 1.22.0. Please test the tarball and report any bugs you find on Bugzilla: http://bugzilla.wikimedia.org/ Assuming there are no show-stopping bugs reported with this RC, we'll be making a release this Friday, December 6, with only the version number included here changed. Here are a list of changes made since the last RC. (Links for download follow this list.) https://gerrit.wikimedia.org/r/95952 Add ar_id and el_id sequences for PostgreSQL -- saper https://gerrit.wikimedia.org/r/96994 Fix login with temporary password with $wgSecureLogin = true -- Alexandre Emsenhuber https://gerrit.wikimedia.org/r/96994 Restore Signupstart and Signupend messages for account creation -- Mark A. Hershberger Full release notes: https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.22.0rc3/RELEASE-NOTES… https://www.mediawiki.org/wiki/Release_notes/1.22 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0rc3.tar.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.22/mediawiki-core-1.22.0rc3.tar.g… http://download.wikimedia.org/mediawiki/1.22/mediawiki-1.22.0rc3.tar.gz.sig Public keys: https://www.mediawiki.org/keys/keys.html

7 11

Redirecting obsolete "mobile." and "wap." domains
by Yuri Astrakhan 05 Dec '13

05 Dec '13

This morning Faidon has deployed a patch<https://gerrit.wikimedia.org/r/#/c/99394/1/templates/varnish/mobile-fronten…>to redirect wap.and mobile. subdomains (see also this patch <https://gerrit.wikimedia.org/r/#/c/98058> for the apache side handling), but later due to some cencerns the change has been reverted. Are there any reasons for us to keep the current wap & mobile subdomains handling, or everyone is ok with obsoleting them this way? Thx

3 2

Uninstalling hooks for tests?
by Marcin Cieslak 05 Dec '13

05 Dec '13

I am not very happy about this but we came to the case where it might be useful to explicitly uninstall some hook(s) for out unit tests. You might want to checkout MediaWikiTestCase::uninstallHook https://gerrit.wikimedia.org/r/#/c/99349/ I am not happy about blurring differences between unit and integration testing, but breaking core with extensions and vice versa is sometimes useful. //Saper

4 4

Re: [Wikitech-l] [Labs-l] (Update) HTTP on tools.wmflabs.org temporarily disabled
by Marc A. Pelletier 05 Dec '13

05 Dec '13

More news: It turns out the DDOS was inadvertent and caused by an ill-considered addition to several projects rather than malice: a script hosted on tool labs intended to tie Wikidata to search results was made to load on every page view rather than just upon searching, causing every hit to a page on the projects to cause the user's client to connect to tool labs. Obviously, tool labs does not scale well to that many requests. :-) It will probably take several hours for things to return to normal as we hunt down and remove those loads and cached versions expire from endusers' caches. -- Marc _______________________________________________ Labs-l mailing list Labs-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/labs-l

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l December 2013