Wikitech-l November 2013

128 participants
124 discussions

Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24

Hello, I have been a WP editor since 2006. I hope you can help me. For some reason I no longer have Section Heading titles showing in the Articles. This is true of all Headings including the one that carries the Article subject's name. When there is a Table of Contents, it appears fine and, when I click on a particular Section, it goes to that Section, but all that is there is a straight line separating the Sections. There is also no button to edit a Section. If I edit the page and remove the "== ==" markers from the Section Titles, the Title then shows up, but not as a Section Heading. Also, I don't have any Date separators on my Want List. This started 2 days ago. Any thoughts? Thanks, Marc Riddell [[User:Michael David]]

10 11

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here. tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.) (Is there a place on mw.org to put this tidbit on?) ------- Forwarded message ------- From: "Brian Levine" <support(a)github.com> (GitHub Staff) To: matma.rex(a)gmail.com Cc: Subject: Re: Commits in mirrored repositories not showing up on my profile Date: Tue, 09 Jul 2013 06:47:19 +0200 Hi Bartosz In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit. The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits. Cheers Brian -- Matma Rex

3 3

People with knowledge of English swear words needed :o
by Petr Bena 20 Nov '14

20 Nov '14

Are you good in swearing? WE NEED YOU Huggle 3 comes with vandalism-prediction as it is precaching the diffs even before they are enqueued including their contents. Each edit has so called "score" which is a numerical value that if higher, the edit is more likely a vandalism. If you want to help us improve this feature, it is necessary to define a "score words" list for every wiki where huggle is about to be used, for example on English wiki. Each list has following syntax: (see https://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config&diff=573…) score-words(score): list of words separated by comma, can contain newlines but comma must be present example score-words(200): these, are, some, words, which, presence, of, increases, the, score, each, word, by, 200, So, if you know english better than me, which you likely do, go ahead and improve the configuration file there, no worries, huggle's config parser is very syntax-error proof. If you have any other suggestion how to improve huggle's prediction, go ahead and tell us!

8 8

Re: [Wikitech-l] MediaWiki to Latex Converter
by Fred Bauder 17 Jul '14

17 Jul '14

I have a log of what happens on when the commands: sudo apt-get install mediawiki2latex mediawiki2latex -u https://en.wikipedia.org/wiki/Adam_Ries -o AdamRies.pdf are entered on the command line of ubuntu (13.10) Better than TV... Happy to send it to anyone. Fred

6 11

Changes in API action=parse&mobileformat=...
by Max Semenik 09 Jun '14

09 Jun '14

Hi, in response to bug 54607 [1], we've changed the semantics of the mobileformat parameter to action=parse == Summary == Previously, it used to accept strings 'html' or 'wml', later just 'html' and modify the structure of output (see below). This was problematic because you needed to retrieve the HTML from output in different ways, depending on whether mobileformat is specified or not. Now, mobileformat is a boolean parameter, that is if there's a 'mobileformat' parameter in request, it will be treated as "the output should be mobile-friendly", regardless of value. And the output structure will be the same. For compatibility with older callers, mobileformat=(html|wml) will be special-cased to return the older structure at least for 6 month from now. These changes will start being rolled out to the WMF sites starting from tomorrow, Tuesday October 24th and this process will be complete by October 31st. == Examples == === Non-mobile parse === api.php?action=parse&format=xml { "parse": { "title": "...", "text": { "*": "foo" } } } api.php?action=parse&format=json <?xml version="1.0"?> <api> <parse title="..." displaytitle="..."> <text xml:space="preserve">foo</text> </parse> </api> === Parse that outputs mobile HTML, old style === api.php?action=parse&format=json&mobileformat=html { "parse": { "title": "API", "text": "foo" } } api.php?action=parse&format=xml&mobileformat=html <?xml version="1.0"?> <api> <parse title="..." text="foo" displaytitle="..."> </parse> </api> === Parse that outputs mobile HTML, new style === api.php?action=parse&format=...&mobileformat Same as for non-mobile parses. == FAQ == Q: I didn't use mobileformat before, does anything change for me? A: No. Q: I use mobileformat=html, will my bot/tool be broken now? A: No, you will have 6 months to switch to new style. Q: I'm only planning to use mobileformat, what should I do? A: Just use the new style. Q: How did this format discrepancy appear in the first place? A: To err is human. ----- [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=54607 -- Best regards, Max Semenik ([[User:MaxSem]])

1 1

workflow to add multiple patches to gerrit.wikimedia.org:29418/operations/puppet.git
by Petr Bena 13 May '14

13 May '14

Currently I do: * clone a repo * setup git & hooks # patch 1: * apply my changes * commit * execute git-review # patch 2: * apply my changes * commit FAIL - the new commit it depending on previous commit - I can't push What am I supposed to do in order to push multiple separate patches? GIT-IDIOT way please, no long explanations, just commands and examples. Thanks

6 11

Fate of hierarchical list on Special:Allpages
by Ori Livneh 11 May '14

11 May '14

Following change I189ba71de[0], the hierarchical list in Special:Allpages becomes a simple alphabetic pager if the total number of pages exceeds a safety threshold. The threshold is designed to protect wikis on which the load generated by the process of generating the hierarchical list would be prohibitively expensive (bug 56840[1]). I189ba71de resolved the immediate operational issue, but there is a further question of whether we want to keep the hierarchical list at all, especially given that it cannot be enabled (in its current implementation, at least) on larger installations. >From my perspective, the ideal outcome of this discussion would be that we agree that the hierarchical list is a poor fit for the MediaWiki of today, and we resolve to remove it from core. According to stats.grok.se, enwiki's Special:Allpages receives approximately 158 hits a day.[2] [0]: https://gerrit.wikimedia.org/r/#/c/94690/ [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=56840 [2]: http://stats.grok.se/en/latest90/Special:Allpages --- Ori Livneh ori(a)wikimedia.org

6 7

MediaWiki 1.19.0beta2
by Sam Reed 09 May '14

09 May '14

I'm happy to announce the availability of the second beta release of the new MediaWiki 1.19 release series. Please try it out and let us know what you think. Don't run it on any wikis that you really care about, unless you are both very brave and very confident in your MediaWiki administration skills. MediaWiki 1.19 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.19 file for the full list of changes in this version. Five security issues were discovered. It was discovered that the api had a cross-site request forgery (CSRF) vulnerability in the block/unblock modules. It was possible for a user account with the block privileges to block or unblock another user without providing a token. For more details, see https://bugzilla.wikimedia.org/show_bug.cgi?id=34212 It was discovered that the resource loader can leak certain kinds of private data across domain origin boundaries, by providing the data as an executable JavaScript file. In MediaWiki 1.18 and later, this includes the leaking of CSRF protection tokens. This allows compromise of the wiki's user accounts, say by changing the user's email address and then requesting a password reset. For more details, see https://bugzilla.wikimedia.org/show_bug.cgi?id=34907 Jan Schejbal of Hatforce.com discovered a cross-site request forgery (CSRF) vulnerability in Special:Upload. Modern browsers (since at least as early as December 2010) are able to post file uploads without user interaction, violating previous security assumptions within MediaWiki. Depending on the wiki's configuration, this vulnerability could lead to further compromise, especially on private wikis where the set of allowed file types is broader than on public wikis. Note that CSRF allows compromise of a wiki from an external website even if the wiki is behind a firewall. For more details, see https://bugzilla.wikimedia.org/show_bug.cgi?id=35317 George Argyros and Aggelos Kiayias reported that the method used to generate password reset tokens is not sufficiently secure. Instead we use various more secure random number generators, depending on what is available on the platform. Windows users are strongly advised to install either the openssl extension or the mcrypt extension for PHP so that MediaWiki can take advantage of the cryptographic random number facility provided by Windows. Any extension developers using mt_rand() to generate random numbers in contexts where security is required are encouraged to instead make use of the MWCryptRand class introduced with this release. For more details, see https://bugzilla.wikimedia.org/show_bug.cgi?id=35078 A long-standing bug in the wikitext parser (bug 22555) was discovered to have security implications. In the presence of the popular CharInsert extension, it leads to cross-site scripting (XSS). XSS may be possible with other extensions or perhaps even the MediaWiki core alone, although this is not confirmed at this time. A denial-of-service attack (infinite loop) is also possible regardless of configuration. For more details, see https://bugzilla.wikimedia.org/show_bug.cgi?id=35315 ********************************************************************* What's new? ********************************************************************* MediaWiki 1.19 brings the usual host of various bugfixes and new features. Comprehensive list of what's new is in the release notes. * Bumped MySQL version requirement to 5.0.2. * Disable the partial HTML and MathML rendering options for Math, and render as PNG by default. * MathML mode was so incomplete most people thought it simply didn't work. * New skins/common/*.css files usable by skins instead of having to copy piles of generic styles from MonoBook or Vector's css. * The default user signature now contains a talk link in addition to the user link. * Searching blocked usernames in block log is now clearer. * Better timezone recognition in user preferences. * Extensions can now participate in the extraction of titles from URL paths. * The command-line installer supports various RDBMSes better. * The interwiki links table can now be accessed also when the interwiki cache is used (used in the API and the Interwiki extension). Internationalization - -------------------- * More gender support (for instance in user lists). * Add languages: Canadian English. * Language converter improved, e.g. it now works depending on the page content language. * Time and number-formatting magic words also now depend on the page content language. * Bidirectional support further improved after 1.18. Release notes - ------------- Full release notes: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob_plain;f=RE LEASE-NOTES-1.19;hb=1.19.0beta2 https://www.mediawiki.org/wiki/Release_notes/1.19 Co-inciding with these security releases, the MediaWiki source code repository has moved from SVN (at https://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3) to Git (https://gerrit.wikimedia.org/gitweb/mediawiki/core.git). So the relevant commits for these releases will not be appearing in our SVN repository. If you use SVN checkouts of MediaWiki for version control, you need to migrate these to Git. If you up are using tarballs, there should be no change in the process for you. Please note that any WMF-deployed extensions have also been migrated to Git also, along with some other non WMF-maintained ones. Please bear with us, some of the Git related links for this release may not work instantly, but should later on. To do a simple Git clone, the command is: git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git More information is available at https://www.mediawiki.org/wiki/Git For more help, please visit the #mediawiki IRC channel on freenode.net irc://irc.freenode.net/mediawiki or email The MediaWiki-l mailing list at mediawiki-l(a)lists.wikimedia.org. ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gz Patch to previous version (1.19.0beta1), without interface text: http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gz Interface text changes: http://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patc h.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.tar.gz.si g http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta2.patch.gz. sig http://download.wikimedia.org/mediawiki/1.19/mediawiki-i18n-1.19.0beta2.patc h.gz.sig Public keys: https://secure.wikimedia.org/keys.html

5 5

Engineering Community team updates
by Quim Gil 25 Apr '14

25 Apr '14

Hi, Just like every first Tuesday of the month [1], the Engineering Community team has reviewed and fine tuned the monthly and quarterly plans: https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings With Google Code-in and Outreach Program for Women starting soon, this month is expected to be very busy. We also have our team's quarterly review, which we expect will be useful to sync our longer term plans with our actual activities - see https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goals#Wikimedi… Last week we had the monthly ECT Showcase, just like every last Tuesday of the month [1]. There we presented a selection of tasks completed in October. You can watch the video at http://www.youtube.com/watch?v=Y3Gl-oR2ucU (copy to Commons pending, help welcome). Next week we will have our monthly IRC meeting, just like every second Tuesday of the month. You can propose topics to be discussed at https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings#2013-11-… That is all for now. We will use this thread for future updates. Questions? Just ask. [1] Just joking, we only completed a first iteration. -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

2 9

[RFC] Isolate custom jQuery libraries
by Daniel Friesen 03 Apr '14

03 Apr '14

I've been bothered for awhile by the mess we have in resources/jquery/ – 3rd party libraries, custom libraries we have to maintain, and directly MW related code using mediaWiki.* APIs all mixed together in the same directory. So I went and audited the .js we have inside resources/jquery/ and have wrote up an RFC on it: https://www.mediawiki.org/wiki/Requests_for_comment/Isolate_custom_jQuery_l… -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]

4 4

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 November 2013