Template talk:Extension
 Archives |
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Author/username field is broken | 0 | 20:27, 1 December 2011 |
| Add parameter to indicate whether DB update is needed post extension installation | 3 | 14:28, 11 November 2011 |
| issues | 1 | 01:36, 18 October 2011 |
| What is "nousage" for | 1 | 09:22, 17 October 2011 |
| Support for multiple authors | 0 | 08:52, 17 October 2011 |
| Missing link | 0 | 08:43, 17 October 2011 |
| User rights documentation | 2 | 08:42, 17 October 2011 |
| typo | 1 | 08:40, 17 October 2011 |
See https://www.mediawiki.org/w/index.php?title=Extension%3ASoundManager2Button&action=historysubmit&diff=459466&oldid=459459 -- the author had to add another string to get the authorship to show up, even though the documentation says, "If omitted then the 'username' field will be used (if present)." Please fix either the documentation or the functionality.
<Wikinaut> yvipanda: does it need to run update.php after installation ? (this is not mentioned on http://www.mediawiki.org/wiki/Extension:ShortUrl ) <Reedy> Yes <Reedy> That's somewhat stndard practise <Wikinaut> Reedy, standard, yes/no, then please modify the Template:Extension info box, so that "php update.php" needed yes/no can be quickly indentified
Kthx.
Hi, having this parameter was a very good idea. However I suggest to remove the explanation "php update.php needed after installation" from display. I takes heaps of space. I think everyone may just click on the link which takes one directly to the documentation of the parameter and its implications. Cheers
Adding
1.15 to
|compatibility = 1.15
makes:
- the word "compatibility" not show up and
- check usage (experimental) appears outside of the template at the top of the page.
That's not how it works. It's supposed to accept a {{Extension Testing}} table. But the project died in 2009, and I don't think I've seen anyone use the field correctly since then. Since it causes breakage when used improperly, I'd prefer to kill the field, or at list stop mentioning it in the {{Extension}} documentation to discourage its use.
There is an optional parameter in the template for "nousage", which it appears is supposed to be set to "yes" or "no"; what is the purpose of it? It's not documented anywhere.
It would be nice if we added a couple of more username/author combos for extensions that have more than one, So we can define them separately instead of just just sticking them in the one author field.
in the section "Content Parameters"->Types->Interface->special, the external link to the SpecialPage.php is broken. i am not sure where should it link to.
User rights documentation
I've created Category:Extensions which add rights. Currently, additional user rights are not documented anywhere, and this can be very confusing (see e.g. Extension:AbuseFilter) because you have to look for a wiki where the right is available and check Special:ListGroupRights. Hopefully, all rights descriptions are in Mediawiki:Right-<rightname> messages, so I think that we could use the rights parameter to automatically list them with {{int:Right-<rightname>}}. To pass the list, we could either split the parameter in rights1, rights2 etc. or use the #titleparts "string parser & converter" (rights=name1/name2/name3 etc.); to add additional notes, I wonder if we should create a rightsnote1,2... or a single rightsnotes parameter.
Right away I found two extensions that were using the rights field incorrectly, so I fixed them. I also found Extension:Ajax though, which has None entered into the rights and parameters field. Should that be removed to prevent the incorrect appearance of the extension adding user rights when it really doesn't?
Rights descriptions may not fit into the infobox well. "Perform captcha triggering actions without having to go through the captcha", which appears to be the longest extension-based right description on this wiki, spans two lines when I stick into the existing rights field. If there are several rights, or the descriptions are particularly long, that may get unwieldy. Also, getting the rights descriptions from messages is not something that will work in a lot of cases, because only a small amount of the extensions listed here are actually installed on MediaWiki.org. Perhaps it's best to just discuss the added rights in the extension documentation, as people are already being encouraged to do.
To avoid at least a part of the duplicated work, we could create a template which creates a table with names, description and notes, where the description is taken directly from system messages if you say the template to do so (when the extension is installed here). What do you think?
In russian version of the template the word 'status' is spelt 'statut', it should be either correctly spelt in english or yet better it should be translated into russian ('статус').
So nobody with the rights is interested in changing this? Beta M 15:43, 4 February 2010 (UTC)
