MediaWiki-l July 2010

mediawiki-l@lists.wikimedia.org

87 participants
93 discussions

Welcome to mediawiki-l (weekly posting)
by river＠nightshade.toolserver.org 29 Jul '10

29 Jul '10

Welcome to mediawiki-l. This mailing list exists for discussion and questions about the MediaWiki software[0]. Important MediaWiki-related announcements (such as new versions) are also posted to this list. Other resources. If you only wish to receive announcements, you should subscribe to mediawiki-announce[1] instead. MediaWiki development discussion, and all Wikimedia technical questions, should be directed to the wikitech-l[2] mailing list. Several other MediaWiki-related lists exist: - mediawiki-api[5] for API discussions, - mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise, - mediawiki-cvs[7] for notification of commits to the Subversion repository, - mediawiki-i18n[8] for discussion of MediaWiki internationalisation support, - wikibugs-l[9] for notification of changes to the bug tracker. List administrivia (unsubscribing, list archives). To unsubscribe from this mailing list, visit [12]. Archives of previous postings can be found at [3]. This list is also gatewayed to the Gmane NNTP server[4], which you can use to read and post to the list. Posting to the list. Before posting to this list, please read the MediaWiki FAQ[10]. Many common questions are answered here. You may also search the list archives to see if your question has been asked before. Please try to ask your question in a way that enables people to answer you. Provide all relevant details, explain your problem clearly, etc. You may wish to read [13], which explains how to ask questions well. To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a public list, so you should not include confidential information in mails you send. When replying to an existing thread, use the "Reply" or "Followup" feature of your mail client, so that clients that understand threading can sort your message properly. When quoting other messages, please use the "inline" quoting style[11], for clarity. When creating a new thread, do not reply to an existing message and change the subject. This will confuse peoples' mail readers, and will result in fewer people reading your mail. Instead, compose a new message for your post. Messages posted to the list have the "Reply-To" header set to the mailing list, which means that by default, replies will go to the entire list. If you are posting a reply which is only interesting to the original poster, and not the list in general, you should change the reply to only go to that person. This avoids cluttering the list with irrelevant traffic. About this message. This message is posted to the list once per week by <river(a)wikimedia.org>. Please contact me if you have any questions or concerns about this mailing. References. [0] http://www.mediawiki.org/ [1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce [2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l [3] http://lists.wikimedia.org/pipermail/mediawiki-l/ [4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki [5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api [6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise [7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs [8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n [9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l [10] http://www.mediawiki.org/wiki/FAQ [11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying [12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l [13] http://www.catb.org/~esr/faqs/smart-questions.html

1 0

Easy creation of page sequences
by Jean-Marc van Leerdam 28 Jul '10

28 Jul '10

Hi, I have been trying to create a maintainable way of grouping pages together and allowing readers to page through them in sequence. Most samples I've seen use templates that require you to supply the 'previous' and 'next' page. This however results in three page edits to insert a new page between two existing pages and does not guarantee that your prev-sequence is identical to the next-sequence... Being a programmer, that is way too much duplicate and error-prone work for me ;-) There must be a better way to do this and I was hoping to solve it with a plain MW installation (with ParserFunctions and DynamicPageList at the moment). Given an 'index' page that holds a list of all page titles in the preferred order, isn't it possible to create a template that selects the correct previous and next page title given the current page title? I get stuck in getting the correct lines from the index page. DPL can select based on section name (= page title), but then the contents of that index section must be the prev/next links themselves: =First Page= Prev [[Second Page|Next]] =Second Page= [[First Page|Prev]] [[Third Page|Next]] =Third Page= .. etc. This works, except that it is still a lot of duplication of page names (but the edits are contained in a single page, big plus). I hoped to simplify the index page by creating a template that writes the section header and prev/next links, but then DPL no longer recognizes the sections :-( Apparently DPL 'sees' the page text before the templates are called ({{Page|Prev page|Page title|Next page}}: {{Page||First Page|Second Page}} {{Page|First Page|Second Page|Third Page}} {{Page|Second Page|Third Page|Fourth Page}} Basically my questions are: 1. Am I completely off track here? 2. Can DPL be coerced to evaluate templates before looking at the page 3. Can DPL (or another extension) select the text from a section before/after a matched section? 4. Is it possible to determine the section sequence number given the section name (so 'Second Page' results in 2, allowing me to use DPL to retrieve the name of section 2 -/- 1 and 2 + 1 to create the prev/next links? Apologies for the long post, hopefully someone can point me to some good resources (I've been to Meta, Wikibooks, Medawiki.org but could very well have overlooked something there as the amount of info is a bit overwhelming and it is difficult to judge how up to date it is). -- Regards, Jean-Marc

11 16

Maps and Semantic Maps 0.6.5 released
by Jeroen De Dauw 28 Jul '10

28 Jul '10

Hey, Maps [0] and Semantic Maps [1] 0.6.5 are now available for download [2]. This release contains mainly internal changes to improve code modularity and fix some security concerns. Several bugs have been fixed as well, and a new hook has been added to Semantic Maps. Everyone running 0.6.2 or older is advised to upgrade as soon as possible. More information can be found in this blog post [3]. [0] https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Maps [1] https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Semantic_Ma… [2] http://mapping.referata.com/wiki/Help:Download [3] http://blog.bn2vs.com/2010/07/28/maps-and-semantic-maps-0-6-5-released/ Cheers -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! --

1 0

lsearchd daemon quitting when I close terminal.
by Adam Meyer 28 Jul '10

28 Jul '10

Im running the lsearchd daemon by just running .lsearchd in the terminal - and it all works. But when I close that window, it stops. How did I run it in silent mode, or as background, or some way that is not dependent on my window staying open? Thanks!

6 6

format transcluded pages
by Scheid, Bernhard 28 Jul '10

28 Jul '10

Hi, another very specific problem/question: I would like to transclude talkpages from certain pages but I do not want that they influence the behaviour of the the TOC list of the main article. Is there a way to format the headings of transcluded pages in such way that they do not appear in the TOC list of their new evironment? Ideally, I would like to be able to transform ==...== into '''...''' if the page is transcluded.I tried to achieve that by using the DPL extension, but as far as I know now there is no provision for such a case, since you cannot influence the behavious of all headings and sub-headings at random. Is there another solution/extension/hack? Thx in advance B.

2 2

MediaWiki security release: 1.16.0 and 1.15.5
by Tim Starling 28 Jul '10

28 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a security and bugfix release of MediaWiki 1.16.0 and MediaWiki 1.15.5. Download links are given at the end of this email. A data leakage vulnerability was discovered, affecting MediaWiki 1.8 and later. Public caching headers were incorrectly set on API responses containing private data. By means of a CSRF-style attack, this can lead to the disclosure of various types of private data stored on a wiki. All users are advised to upgrade. Full details can be found at: https://bugzilla.wikimedia.org/show_bug.cgi?id=24565 A cross-site scripting (XSS) vulnerability was discovered in profileinfo.php. The vulnerability is only exposed when the script is explicitly enabled in LocalSettings.php, with $wgEnableProfileInfo = true. A register_globals arbitrary inclusion vulnerability was discovered in the 1.16 beta release series, in MediaWikiParserTest.php. This vulnerability does not affect any stable MediaWiki release. It only affects wikis which have PHP's register_globals feature enabled, despite our strong advice to the contrary. Apache installations with AllowOverride enabled may be protected against this vulnerability, since there is a .htaccess file with "Deny from all" in the relevant path. In both releases, the interface text was updated with new translations from translatewiki.net. Full release notes for 1.15.5: <http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_15_5/phase3/RELEASE-NO…> Full release notes for 1.16.0: <http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_16_0/phase3/RELEASE-NO…> Upgrade FAQ: http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading ********************************************************************** We are proud to announce the first stable release of the 1.16 series. Selected changes that may be of interest since MediaWiki 1.15 are: * Watchlists now have RSS/Atom feeds. RSS feeds generally are now hidden, since Atom is a better protocol and is supported by virtually all clients. * It's now possible to block users from sending email via Special:Emailuser. * The maintenance script system was overhauled. Most maintenance scripts now have a useful help page when you run them with --help. * AdminSettings.php is no longer required in order to run maintenance scripts. You can just set $wgDBadminuser and $wgDBadminpassword in your LocalSettings.php instead. * The preferences system was overhauled. Preferences are stored in a more compact format. Changes to site default preferences will automatically affect all users who have not chosen a different preference. * Support for SQLite was improved. Some broken features were fixed, and it now has an efficient full-text search. * The user groups ACL system was improved by allowing rights to be revoked, instead of just granted. * A new localisation caching system was introduced, which will make MediaWiki faster for almost everyone, especially when lots of extensions are enabled. By default, this new system makes a lot of database queries. If your database is particularly slow, or if your system administrator limits your query count, or if you want to squeeze as much performance as possible out of Mediawiki, set $wgCacheDirectory to a writable path on the local filesystem. Make sure you have the DBA extension for PHP installed, this will improve performance further. ********************************************************************** 1.15.5 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.5.tar.gz Patch to previous version (1.15.4), without interface text: http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.5.patch.gz Interface text changes: http://download.wikimedia.org/mediawiki/1.15/mediawiki-i18n-1.15.5.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.5.tar.gz.sig http://download.wikimedia.org/mediawiki/1.15/mediawiki-1.15.5.patch.gz.sig http://download.wikimedia.org/mediawiki/1.15/mediawiki-i18n-1.15.5.patch.gz… Public keys: https://secure.wikimedia.org/keys.html ********************************************************************** 1.16.0 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.16/mediawiki-1.16.0.tar.gz Patch to previous version (1.16.0beta3), without interface text: http://download.wikimedia.org/mediawiki/1.16/mediawiki-1.16.0.patch.gz Interface text changes: http://download.wikimedia.org/mediawiki/1.16/mediawiki-i18n-1.16.0.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.16/mediawiki-1.16.0.tar.gz.sig http://download.wikimedia.org/mediawiki/1.16/mediawiki-1.16.0.patch.gz.sig http://download.wikimedia.org/mediawiki/1.16/mediawiki-i18n-1.16.0.patch.gz… Public keys: https://secure.wikimedia.org/keys.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxP4e8ACgkQgkA+Wfn4zXkWIgCgmr9dHmPtQqk+2bdQaHkLGss3 7W8AoJqgkJsurVVzWFBkr3TgrswsWzcd =L7ad -----END PGP SIGNATURE-----

1 0

disable entire namespace
by Steve VanSlyck 27 Jul '10

27 Jul '10

Is there a way, on installation of a new wiki, to completely disable the talk namespace? No talk pages, "not nowhere, not nohow," as the wizard said.

4 6

Over ride user settings - How?
by Adam Meyer 27 Jul '10

27 Jul '10

I just added a lot of pages to a name space, and I need to enable users to search that name space by default. I added that namespace as a default to search - And this works for guests. But all users who are logged in are using their personal settings and this name space is not selected. How would I go about enabling search in this namespace for all users? It is fine if I need to do it through SQL. Thank you, Adam

2 2

Template value inside custom tag - not working
by Adam Meyer 26 Jul '10

26 Jul '10

I have a custom tag called code with an attribute of p. <code p="test" /> I have a template called code that is very simple <code p="{{{1}}}" /> [[Category:Has Code]] when I do this {{code|test}} It does not render as <code p="test" /> but as <code p="{{{1}}}" /> Any ideas why? Thanks, -Adam

2 3

special button in the edit area
by Scheid, Bernhard 26 Jul '10

26 Jul '10

Hi, I would like to add a function/button to the edit window: like the "nowiki" or "italics" button it should create typographical hyphens (“...”) in the textarea. How could that be done? Or is there some extension to do that? Thx Bernhard

6 11

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

2025

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 2010