MediaWiki-l July 2014

mediawiki-l@lists.wikimedia.org

68 participants
47 discussions

Lis tes messages avant qu'ils ne soient effacés!
by Badoo 31 Dec '23

31 Dec '23

Lis ton message de Nganguem Victor avant qu'il ne soit effacé! Pour lire ton message, suis simplement ce lien: http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6 D'autres personnes sont aussi présentes: Oded (Tel Aviv, Israël) Priya (Udaipur, Inde) RajaYogi BK (Udaipur, Inde) Karuna (Udaipur, Inde) Chika Reginald Onyia (Pnompen', Cambodge) ...Qui d'autre? http://eu1.badoo.com/chatnoirxx/in/p4hxwt052ok/?lang_id=6 Les liens ne fonctionnent pas dans ce message? Copie les dans la barre d'adresse de ton navigateur. Tu as reçu cet email suite à un message envoyé par Nganguem Victor de notre système. S'il s'agit d'une erreur, ignore simplement cet email. La requête sera alors effacée du système. Amuse-toi bien ! L'équipe Badoo Courrier automatique de Badoo suite à l'envoi d'un message à ton attention sur Badoo. Les réponses ne sont ni stockées, ni traitées. Si tu ne veux plus recevoir de message de Badoo, fais-le nous savoir: http://eu1.badoo.com/impersonation.phtml?lang_id=6&mail_code=65&email=media…

3 2

Wikibase on third-party wikis
by Till Kraemer 26 Sep '16

26 Sep '16

Hi, I'm trying to use Wikibase on my pool wiki and language wikis. In my pool wiki, I can create properties and items, but I can't add site links to them. ID: "Q1", site id: "cswiki", site link: "article name" gives me the error "The specified article could not be found on the corresponding site." even though that article exists on cswiki. I also can't access data from the language wikis. If I use {{#property:P1}} in an article on cswiki, nothing shows up. I downloaded Wikidata-refs-heads-master.tar.gz and extracted it to the extension folder of my pool wiki and language wikis. My LocalSettings.php of the pool wiki looks like this: # Wikibase $wgEnableWikibaseRepo = true; $wgEnableWikibaseClient = false; $wmgUseWikibaseRepo = true; $wmgUseWikibaseClient = false; require_once __DIR__ . "/extensions/Wikidata/Wikidata.php"; require_once __DIR__ . "/extensions/Wikidata/extensions/Wikibase/repo/ExampleSettings.php"; # SiteMatrix Extension require_once "$IP/extensions/SiteMatrix/SiteMatrix.php"; $wgLocalDatabases = array( 'cswiki', 'dewiki', 'enwiki', 'eswiki', 'frwiki', 'huwiki', 'hywiki', 'itwiki', 'nlwiki', 'plwiki', 'poolwiki', 'ptwiki', 'ruwiki', 'srwiki', 'svwiki' ); My LocalSettings.php of the language wikis (cs for example) look like this: # Wikibase Extension $wgEnableWikibaseRepo = false; $wgEnableWikibaseClient = true; $wmgUseWikibaseRepo = false; $wmgUseWikibaseClient = true; require_once __DIR__ . "/extensions/Wikidata/Wikidata.php"; # Settings $wgWBSettings['repoUrl'] = 'http://pool.mypedia.com'; $wgWBSettings['repoScriptPath'] = '/w'; $wgWBSettings['repoArticlePath'] = '/wiki/$1'; $wgWBSettings['siteGlobalID'] = 'cswiki'; $wgWBSettings['repoDatabase'] = 'poolwiki'; $wgWBSettings['changesDatabase'] = 'poolwiki'; # Optional $wgWBSettings['siteGroup'] = 'mypedia'; $wgWBSettings['sort'] = 'code'; //optional $wgWBSettings['sortPrepend'] = array( 'cs' ); In populateSitesTable.php, I changed "https://meta.wikimedia.org/w/api.php" to "http://pool.mypedia.com/w/api.php" and "$validGroups = array( 'wikipedia', 'wikivoyage', 'wikiquote', 'wiktionary','wikibooks', 'wikisource', 'wikiversity', 'wikinews' );" to "$validGroups = array( 'mypedia' );" Do I need to change "$wikiId = $this->getOption( 'wiki' );" too, since it says "wiki" is expanded to "wikipedia"? Table "sites" in the poolwiki database looks like this: site_id | site_global_key | site_type | site_group | site_source | site_language | site_protocol | site_domain | site_data | site_forward | site_config 1 | cswiki | mediawiki | mypedia | local | cs | http:// | com.mypedia.cs. | a:1:{s:5:"paths";a:2:{s:9:"file_path";s:5:"/w/$1";s:9:"page_path";s:8:"/wiki/$1";}} | 0 | a:0:{} [...] 15 | poolwiki | mediawiki | pool | local | en | http:// | com.mypedia.pool. | a:1:{s:5:"paths";a:2:{s:9:"file_path";s:5:"/w/$1";s:9:"page_path";s:8:"/wiki/$1";}} | 0 | a:0:{} I changed site_group "wikipedia" to "mypedia" and added data for site_protocol and site_domain by hand. I noticed that the script path is "/w/$1" here, while $wgScriptPath in LocalSettings.php is actually "/w", could that cause any problems? And should I change site_group of the pool to mypedia like I did with the language wikis or isn't that necessary? Wikibase DataModel 0.8, Wikibase Repository 0.5 alpha, WikibaseLib 0.5 alpha and Wikidata show up in Special:Version of the pool wiki. Wikibase Client 0.5 alpha, Wikibase DataModel 0.8, WikibaseLib 0.5 alpha and Wikidata show up in Special:Version of the language wikis. Any help would be really appreciated! Thanks and cheers, Till

1 1

File descriptions aren't fetched
by Till Kraemer 26 Sep '16

26 Sep '16

Hi, I'm running multiple language wikis and one pool wiki. The problem is that no file descriptions are fetched in the language wikis although $wgFetchCommonsDescriptions is set to true. LocalSettings.php of the language wikis: $wgUseSharedUploads = true; $wgSharedUploadPath = 'http://pool.example.com/w/images'; $wgSharedUploadDirectory = '/path/to/pool/w/images/'; $wgHashedSharedUploadDirectory = true; $wgFetchCommonsDescriptions = true; $wgSharedUploadDBname = 'poolwiki'; # DB-Name of PoolWiki #$wgSharedUploadDBprefix = 'wiki_'; # Table name prefix for PoolWiki $wgRepositoryBaseUrl = "http://pool.example.com/wiki/Image:"; ForeignAPIRepo used to work fine before, but since I switched from Apache to Nginx, no images show up anymore in the language wikis. This is how my LocalSettings.php used to look like: $wgForeignFileRepos[] = array( 'class' => 'ForeignAPIRepo', 'name' => 'pool', 'apibase' => 'http://pool.example.com/w/api.php', 'fetchDescription' => true, // Optional 'descriptionCacheExpiry' => 43200, // 12 hours, optional (values are seconds) 'apiThumbCacheExpiry' => 0, // required for local thumb caching ); I also tried to set 'name' => 'poolwiki', (name of the pool database) but that doesn't work either. I also re-started Memcached and I even deleted a file description page from the CloudFlare cache, but still no file description can be seen :/ My software: MediaWiki: 1.22.0 PHP: 5.3.27 (fpm-fcgi) MySQL: 5.1.70-log Any help would be über-cool. Thanks and cheers, Till

1 3

[BREAKING CHANGE] Upcoming jQuery upgrade: Removing jQuery Migrate
by Krinkle 02 Dec '14

02 Dec '14

Hey all, TL;DR: * We did not make the breaking change last week for Wikimedia; it is postponed. * MediaWiki 1.24.0 will ship with jQuery Migrate switched off. * Wikimedia & non-Wikimedia wikis can enable jQuery Migrate if needed. * When MediaWiki 1.24 is released, we will switch off jQuery Migrate for Wikimedia wikis. As we said last month, we are upgrading MediaWiki's jQuery to version 1.11.x [1], which removes some long-deprecated functions. These were done in phase one [2] and two [3] as of last week. However, we have held off with phase 3 (removing the jQuery Migrate plugin) for a while to give migration a little more time. The amount of migration work necessary has been much less than I anticipated. Very few scripts have actually needed changing, probably because these features have been deprecated for quite a while now. Some of newer developers may never have even known of these APIs. Having said that, it does take a while for a message like this to spread out to some members of our large community. While those wiki scripts and gadgets which have active maintainers have been looked into, and (where needed) updated accordingly, a large number of gadgets and scripts in the cluster of Wikimedia wikis have not yet had a chance to get a grip on this, let alone extensions and wikis outside of Wikimedia. While I don't want to set another deadline, I think it makes sense to ship the jQuery Migrate plugin for one release (with MediaWiki 1.24), and then remove it in MediaWiki 1.25. This will give all wikis' communities and extension authors a few more months until the MediaWiki 1.24 branch point (in Autumn 2014) before they will need to make adjustments to work with MediaWiki master. MediaWiki 1.24.0 stable will disable support for legacy jQuery by default. If you find you have scripts, gadgets or extensions still using legacy jQuery APIs, you can enable them with a simple line in LocalSettings.php: $wgIncludejQueryMigrate = true; And of course when you find you need to do this, please make an effort to ensure the maintainers of those items still using these legacy features are aware of this so they may patch the code accordingly (using the upgrade guide[4] and my earlier announcement [5]). When MediaWiki 1.24 is released, we will switch off jQuery Migrate for Wikimedia wikis. — Krinkle [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=44740 [2] https://gerrit.wikimedia.org/r/#/c/131494/ [3] https://gerrit.wikimedia.org/r/#/c/133477/ [4] http://jquery.com/upgrade-guide/1.9/ [5] http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg75735.html On 7 May 2014, at 18:29, Krinkle <krinklemail(a)gmail.com> wrote: > Hey all, > > TL;DR: jQuery will soon be upgraded from v1.8.3 to v1.11.x (the latest). This > major release removes deprecated functionality. Please migrate away from this > deprecated functionality as soon as possible. > > It's been a long time coming but we're now finally upgrading the jQuery package > that ships with MediaWiki. > > We used to regularly upgrade jQuery in the past, but got stuck at v1.8 a couple > of years ago due to lack of time and concern about disruption. Because of this, > many developers have needed to work around bugs that were already fixed in later > versions of jQuery. Thankfully, jQuery v1.9 (and its v2 counterpart) has been > the first release in jQuery history that needed an upgrade guide[1][2]. It's a > major release that cleans up deprecated and dubious functionality. > > Migration of existing code in extensions, gadgets, and user & site scripts > should be trivial (swapping one method for another, maybe with a slight change > to the parameters passed). This is all documented in the upgrade guide[1][2]. > The upgrade guide may look scary (as it lists many of your favourite methods), > but they are mostly just addressing edge cases. > > == Call to action == > > This is a call for you, to: > > 1) Get familiar with http://jquery.com/upgrade-guide/1.9/. > > 2) Start migrating your code. > > jQuery v1.9 is about removing deprecated functionality. The new functionality is > already present in jQuery 1.8 or, in some cases, earlier. > > 3) Look out for deprecation warnings. > > Once instrumentation has begun, using "?debug=true" will log jQuery deprecation > warnings to the console. Look for ones marked "JQMIGRATE" [7]. You might also > find deprecation notices from mediawiki.js, for more about those see the mail > from last October [8]. > > == Plan == > > 1) Instrumentation and logging > > The first phase is to instrument jQuery to work out all the areas which will > need work. I have started work on loading jQuery Migrate alongside the current > version of jQuery. I expect that to land in master this week [6], and roll out on > Wikimedia wikis the week after. This will enable you to detect usage of most > deprecated functionality through your browser console. Don't forget the upgrade > guide[1], as Migrate cannot detect everything. > > 2) Upgrade and Migrate > > After this, the actual upgrade will take place, whilst Migrate stays. This > should not break anything since Migrate covers almost all functionality that > will be removed. The instrumentation and logging will remain during this phase; > the only effective change at this point is whatever jQuery didn't think was > worth covering in Migrate or were just one of many bug fixes. > > 3) Finalise upgrade > > Finally, we will remove the migration plugin (both the Migrate compatibility > layer and its instrumentation). This will bring us to a clean version of latest > jQuery v1.x without compatibility hacks. > > > A rough timeline: > > * 12 May 2014 (1.24wmf4 [9]): Phase 1 – Instrumentation and logging starts. This > will run for 4 weeks (until June 9). > > * 19 May 2014 (1.24wmf5): Phase 2 – "Upgrade and Migrate". This will run for 3 > weeks (upto June 9). The instrumentation continues during this period. > > * 1 June 2014 (1.24wmf7) Finalise upgrade. > > > == FAQ == > > Q: The upgrade guide is for jQuery v1.9, what about jQuery v1.10 and v1.11? > > A: Those are regular updates that only fix bugs and/or introduce non-breaking > enhancements. Like jQuery v1.7 and v1.8, we can upgrade to those without any > hassle. We'll be fast-forwarding straight from v1.8 to v1.11. > > > Q: What about the jQuery Migrate plugin? > > A: jQuery developed a plugin that adds back some of the removed features (not > all, consult the upgrade guide[2] for details). It also logs usage of these to > the console. > > > Q: When will the upgrade happen? > > A: In the next few weeks, once we are happy that the impact is reasonably low. > An update will be sent to wikitech-l just before this is done as a final reminder. > This will be well before the MediaWiki 1.24 branch point for extension authors > looking to maintain compatibility. > > > Q: When are we moving to jQuery v2.x? > > A: We are not currently planing to do this. Despite the name, jQuery v2.x > doesn't contain any new features compared to jQuery v1 [3]. The main difference > is in the reduced support for different browsers and environments; most > noticeably, jQuery 2.x drops support for Internet Explorer 8 and below, which > MediaWiki is still supporting for now, and is outside the scope of this work. > Both v1 and v2 continue to enjoy simultaneous releases for bug fixes and new > features. For example, jQuery released v1.11 and v2.1 together[4][5]. > > -- Krinkle > > [1] http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate- > final-released/ > [2] http://jquery.com/upgrade-guide/1.9/ > [3] http://blog.jquery.com/2013/04/18/jquery-2-0-released/ > [4] http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/ > [5] http://blog.jquery.com/2013/05/24/jquery-1-10-0-and-2-0-1-released/ > [6] https://gerrit.wikimedia.org/r/131494 > [7] https://github.com/jquery/jquery-migrate/blob/master/warnings.md > [8] http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg72198.html > [9] https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap >

1 1

Can an extension automatically add wiki pages
by Sigbert Klinke 11 Aug '14

11 Aug '14

Hi, for my extension I also deliver some test pages. Currently I'am exporting the test pages into a XML file and the wiki adminstrator could import them with importDump.php. Is there a way that the extension automatically integrates some pages into the wiki (of course into my own namespace)? Thanks in advance Sigbert

5 5

Active Directory Integration for Access Management
by Kevin Holleran 04 Aug '14

04 Aug '14

Good afternoon, I was wondering if this was possible before I invest a lot of time into it. I am using an instance of MediaWiki as an internal knowledge base. I have a variety of categories for different functions. I was wondering if I could do one of the following: 1.) Integrate with Active Directory. If the user is in the Wiki-ReadOnly group, they can only read pages and NOT change them. If they are in the Wiki-Write group, they can read & edit pages. OR (the gold state) 2.) Have different read and write groups for each category. For instance, I use the wiki to document how we go about malware analysis and would like some people to be able to see this to use as a reference when working a case, but most people do not need to see this. Is this possible? Thanks! Kevin

3 6

ExtensionDistributor updates on mediawiki.org
by Legoktm 31 Jul '14

31 Jul '14

Hi, Tomorrow a major update[1] will be deployed for the ExtensionDistributor extension on mediawiki.org. We will start fetching branch information directly from Gerrit instead of relying on Github. Additionally, tarballs will be served from extdist.wmflabs.org[2] instead of using Github. There will be a few differences, namely that tarballs are only generated every hour, instead of on the fly like Github did. These tarballs will include submodules inside tarballs for extensions like VisualEditor (bug 44022[3]). If you notice any issues or have any ideas for enhancements, please file a bug in Bugzilla[4]. Additionally, I'd like to thank ^demon and YuviPanda for their help in putting this service together. -- Legoktm [1] https://gerrit.wikimedia.org/r/#/c/149474/ [2] https://extdist.wmflabs.org/dist/ [3] https://bugzilla.wikimedia.org/show_bug.cgi?id=44022 [4] https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions…

4 3

Parsoid tests failed
by Shai Katz 31 Jul '14

31 Jul '14

Hi, I'm trying to setup visual editor and part of that is to install Parsoid. After installating I'm moving to /usr/lib/parsoid/src directory and I run "npm test" Some of tests are passed but many of them failed. I've tried to progress with the installation but "edit" button is not responding, I believe it related with the tests fails. Someone can help me to troubleshoot that? Thanks.

1 0

MediaWiki Security and Maintenance Releases: 1.19.18, 1.22.9 and 1.23.2
by Markus Glaser 30 Jul '14

30 Jul '14

Hello everyone, I would like to announce the release of MediaWiki 1.23.2, 1.22.9 and 1.19.18. This is a regular security and maintenance release. Download links are given at the end of this email. == Security == * (bug 68187) SECURITY: Prepend jsonp callback with comment. * (bug 66608) SECURITY: Fix for XSS issue in bug 66608: Generate the URL used for loading a new page in Javascript,instead of relying on the URL in the link that has been clicked. * (bug 65778) SECURITY: Copy prevent-clickjacking between OutputPage and ParserOutput. == Bugfixes in 1.23.2 == * (bug 68313) Preferences: Turn stubthreshold back into a combo box. * (bug 65214) Fix initSiteStats.php maintenance script. * (bug 67594) Special:ActiveUsers: Fix to work with PostgreSQL. == Bugfixes in 1.22.9 == * (bug 59147) The img_metadata field was not being decoded from bytea into text. Full release notes for 1.23.2: <https://www.mediawiki.org/wiki/Release_notes/1.23> Full release notes for 1.22.9: <https://www.mediawiki.org/wiki/Release_notes/1.22> Full release notes for 1.19.18: <https://www.mediawiki.org/wiki/Release_notes/1.19> Public keys: <https://www.mediawiki.org/keys/keys.html> ********************************************************************** 1.23.2 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.2.tar.gz Patch to previous version (1.23.1): https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.2.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.2.tar.gz.… https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.2.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.2.patch.gz.sig Note: There is no i18n patch as there are no changes in translation. ********************************************************************** 1.22.9 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.9.tar.gz Patch to previous version (1.22.8): https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.9.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.22/mediawiki-core-1.22.9.tar.gz.… https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.9.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.22/mediawiki-1.22.9.patch.gz.sig Note: There is no i18n patch as there are no changes in translation. ********************************************************************** 1.19.18 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.18.tar.gz Patch to previous version (1.19.17): https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.18.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.19/mediawiki-core-1.19.18.tar.gz… https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.18.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.19/mediawiki-1.19.18.patch.gz.sig Note: There is no i18n patch as there are no changes in translation. Markus Glaser (Release Management Team) P.S.: If you are interested in shaping the future of MediaWiki, come join our session about a MediaWiki user group at Wikimania: http://wikimania2014.wikimedia.org/wiki/Submissions/How_about_a_MediaWiki_C… . Email us at glaser(a)hallowelt.biz or mah(a)nichework.com if you would like to participate remotely.

1 0

Mediawiki error creating thumbnail invalid thumbnail parameters
by Seitz Andreas 30 Jul '14

30 Jul '14

Hi, i have a Problem with the Mediawiki Version 1.23.1. (PHPV. 5.5.9; mysql:5.6.16) After the Update from 1.15.4 to 1.23.1 some Thumbnails displays a Error: "error creating thumbnail invalid thumbnail parameters". On the 1.15.4 it works but in the new Version not. The JPG is 3MB and 4320x3240. When I resize the image to 1024 x 768 it works! I read on a Blog that i set in the localsettings.php "$wgMaxShellMemory = 300000;" ->But it doesen´t work too Have anywhere an idea of this Problem? Greetings Andy

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l July 2014