MediaWiki-l December 2015

mediawiki-l@lists.wikimedia.org

68 participants
65 discussions

StackExchange drama over proposed MIT/SE crayon license
by Federico Leva (Nemo) 21 Dec '15

21 Dec '15

https://meta.stackexchange.com/questions/271080/the-mit-license-clarity-on-… There are comments from a MediaWiki developer too: https://meta.stackexchange.com/a/271112/ https://meta.stackexchange.com/questions/271080/the-mit-license-clarity-on-… Nemo

3 3

Re: [MediaWiki-l] MP4 Video - MediaWiki-l Digest, Vol 147, Issue 24
by Ray Paseur 21 Dec '15

21 Dec '15

I have not used MP4 files on my own server (bandwidth issues) but I have found the EmbedVideo Extension to work well. Implementation details are mostly left to the video service (YouTube, Vimeo, etc). May be worth a look.

1 0

MediaWiki sizing
by vasli.slavik＠gmail.com 21 Dec '15

21 Dec '15

Hello! Does anybody have information about sizing of MediaWiki, i.e. if I have 1000 users per day how much RAM/CPU do I need to run MediaWiki? Moreover, when I have 10000 users per day, how much RAM/CPU is needed in this case? And when I have 20000 users per day how much RAM/CPU is needed in this case? Does anybody knows where to get such information? Any ideas about how to calculate this? Best regards, Vasli Slavik

2 2

Problem with autoconfirmed user rights
by 2007 20 Dec '15

20 Dec '15

It recently came to my attention that users of my wiki cannot edit/create their user and talk pages and it's probably been this way for some time and I didn't realize it til now. It's using v1.24.4 They have the following permissions. $wgGroupPermissions['autoconfirmed']['read'] = true; $wgGroupPermissions['autoconfirmed']['edit'] = true; $wgGroupPermissions['autoconfirmed']['createpage'] = true; $wgGroupPermissions['autoconfirmed']['createtalk'] = true; $wgGroupPermissions['autoconfirmed']['upload'] = true; $wgGroupPermissions['autoconfirmed']['reupload'] = true; $wgGroupPermissions['autoconfirmed']['reupload-shared'] = true; $wgGroupPermissions['autoconfirmed']['move'] = false; $wgGroupPermissions['autoconfirmed']['minoredit'] = false; $wgGroupPermissions['autoconfirmed']['createaccount'] = false; $wgGroupPermissions['autoconfirmed']['editprotected'] = false; $wgGroupPermissions['autoconfirmed']['editsemiprotected'] = false; Any thoughts on how to fix this? Thanks Adrian

3 9

[Semanti Forms] How to hardcode values based on which form is used to create/edit an item
by Ed 19 Dec '15

19 Dec '15

Hi all, I'm using Cargo with Semantic Forms. The cargo table is defined in one template and attached in others. Each has it own form as they represent subtypes. How can I hardcode the subtype so that when I query the cargo table holding all the subtypes the info is available? In one of the forms, I tried with {{{field|SubType|mandatory|default="TypeA"}}} and it works. However, when I hide it {{{field|SubType|mandatory|default="TypeA"|hidden}}} it does not. Thoughts? Thanks!

2 2

Re: [MediaWiki-l] MediaWiki-l Digest, Vol 147, Issue 21
by David Shaw 18 Dec '15

18 Dec '15

Requirements: a simple installer and a one click maintainer for all! === Every legacy software reaches a dead end without its adherents noticing. In the case of Drupal and WordPress, both decided they had to make an architectural break with the past, with Drupal 8 and WordPress Calypso respectively. WordPress has leaped Drupal by implementing a full node.js REST model, but it had the advantage of the Ghost fork that did this several years ago. Drupal is a step behind, they decided structured content was more important and were late to the JSON game. Their Rest is a bit of an add-on layer. For MW, one possibility is to add a MEAN stack in front for content delivery. Use angular to develop a fully responsive/adaptive Web Application. Use the legacy code for authoring and content management. Add a REST layer to dump content into Mongo at the front end. Over time, convert the back end to Javascript. David

1 0

[MediaWiki-announce] Security Release: 1.26.1, 1.25.4, 1.24.5 and 1.23.12
by Chad 17 Dec '15

17 Dec '15

I would like to announce the release of MediaWiki 1.26.1, 1.25.4, 1.24.5, and 1.23.12. These releases fix five security issues in core, in addition to other bug fixes. Download links are given at the end of this email == Security fixes == (T117899) SECURITY: $wgArticlePath can no longer be set to relative paths that do not begin with a slash. This enabled trivial XSS attacks. Configuration values such as "http://my.wiki.com/wiki/$1" are fine, as are "/wiki/$1". A value such as "$1" or "wiki/$1" is not and will now throw an error (T119309) SECURITY: Use hash_compare() for edit token comparison (T118032) SECURITY: Don't allow cURL to interpret POST parameters starting with '@' as file uploads (T115522) SECURITY: Passwords generated by User::randomPassword() can no longer be shorter than $wgMinimalPasswordLength (T97897) SECURITY: Improve IP parsing and trimming. Previous behavior could result in improper blocks being issued (T109724) SECURITY: Special:MyPage, Special:MyTalk, Special:MyContributions and related pages no longer use HTTP redirects and are now redirected by MediaWiki == Note about EOL of 1.24.x == Please note that 1.24.5 marks the end of support for the 1.24.x series of releases. Technically this ended a few weeks ago with the release of 1.26.0 but we dropped one final release of 1.24.x here to give it a nicer send off for those who have not yet upgraded. == Release notes == Full release notes for 1.26.1: <https://www.mediawiki.org/wiki/Release_notes/1.26> Full release notes for 1.25.4: <https://www.mediawiki.org/wiki/Release_notes/1.25> Full release notes for 1.24.5: <https://www.mediawiki.org/wiki/Release_notes/1.24> Full release notes for 1.23.12: <https://www.mediawiki.org/wiki/Release_notes/1.23> For information about how to upgrade, see <https://www.mediawiki.org/wiki/Manual:Upgrading> ********************************************************************** 1.26.1 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.1.tar.gz https://releases.wikimedia.org/mediawiki/1.26/mediawiki-core-1.26.1.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.1.patch.gz https://releases.wikimedia.org/mediawiki/1.26/mediawiki-i18n-1.26.1.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.1.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.1.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.26/mediawiki-core-1.26.1.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.25.4 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.4.tar.gz https://releases.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.4.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.4.patch.gz https://releases.wikimedia.org/mediawiki/1.25/mediawiki-i18n-1.25.4.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.4.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.4.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.4.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.24.5 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.24/mediawiki-1.24.5.tar.gz https://releases.wikimedia.org/mediawiki/1.24/mediawiki-core-1.24.5.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.24/mediawiki-1.24.5.patch.gz https://releases.wikimedia.org/mediawiki/1.24/mediawiki-i18n-1.24.5.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.24/mediawiki-1.24.5.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.24/mediawiki-1.24.5.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.24/mediawiki-core-1.24.5.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.23.12 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.12.tar.gz https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.12.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.12.patch.gz https://releases.wikimedia.org/mediawiki/1.23/mediawiki-i18n-1.23.12.patch.… GPG signatures: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.12.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.12.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.12.tar.gz… Public keys: https://www.mediawiki.org/keys/keys.html -Chad H. & Chris S. _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

1 0

npm start command for ContentTranslation
by Andrew Geary 17 Dec '15

17 Dec '15

I am trying to install ContentTranslation on our MediaWiki site. I am having trouble getting past the installation where I run the command "npm start" for the cxserver that is needed in partnership with the extension. The process takes hours and never seems to complete, consistently showing variations of the following: {"name":"mediawiki-contenttranslation.heap.rss","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.rss:62722048","method":"timing","value":62722048,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.rss:62722048","time":"2015-12-17T21:33:38.678Z","v":0} {"name":"mediawiki-contenttranslation.heap.total","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.total:52044288","method":"timing","value":52044288,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.total:52044288","time":"2015-12-17T21:33:38.679Z","v":0} {"name":"mediawiki-contenttranslation.heap.used","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.used:19116472","method":"timing","value":19116472,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.used:19116472","time":"2015-12-17T21:33:38.680Z","v":0} Do I need to give the process more time? Is there something else I can do to fix the issue? I have yet to get past this step in the installation process setting up the cxserver. We run Mediawiki 1.26, PHP 5.5.9, MySQL 5.5.46. Thank you in advance. Best, Andrew Andrew Geary SEG Wiki editor Society of Exploration Geophysicists (SEG) 8801 South Yale, Suite 500 / Tulsa, OK 74137 USA 504-407-1303 ageary(a)seg.org www.seg.org

2 1

Fwd: IRC office hours: Shared hosting
by Nick Wilson (Quiddity) 17 Dec '15

17 Dec '15

As part of T113210 [1], which is a broader discussion on track for the developer summit, I am hosting two IRC office hours back to back [2] on December 21st from 20:00 UTC to 22:00 UTC. The previous office hour [3] focused on ways to reconnect to the shared hosting community. This time two very different topics will be discussed. *The open questions in the descriptions below are by no means meant to be exhaustive, nor are they expected to be fully answered by the end of those office hours. They are just examples to clarify the context of the titles.* *Shared hosting technical alternatives* During the last office hour on the topic of non-technical mediawiki installs, people seemed very eager to discuss new technical solutions that could offer a viable alternative to shared hosting. Could new technologies like containers allow for performance/cost ratios comparable to shared hosting? If not, how big would the penalty be? How much maintenance would we have to do to keep deployment on such platforms up to date? Shared hosting has always suffered from the fact that it's not used at the WMF and therefore only maintained on a volunteer basis. How would things be different with new tech? *Shared hosting support definition* Shared hosting usage is already a reality and we should do a better job accounting for it. Currently mediawiki contributors have no visibility in what should be supported and to what degree. Our browser support is graded and very clear, meanwhile our server-side support is not: https://www.mediawiki.org/wiki/Compatibility Should we model our server-side compatibility guidelines on the graded system we have for browsers? If so, what would that look like? How could we break down "shared hosting support" into more discreet server-side capabilities? [1] https://phabricator.wikimedia.org/T113210 [2] https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours [3] https://tools.wmflabs.org/meetbot/wikimedia-office/2015/wikimedia-office.20… -- [fwding message from wikitech-l and other lists]

1 0

changing the text in the search bar
by Andrew Geary 17 Dec '15

17 Dec '15

I want to modify the term "Search" in the standard search bar that would apply across all skins. Any suggestions? Thanks. Best, Andrew Andrew Geary SEG Wiki editor Society of Exploration Geophysicists (SEG) 8801 South Yale, Suite 500 / Tulsa, OK 74137 USA 504-407-1303 ageary(a)seg.org www.seg.org

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 December 2015