Extension requests

Maplib widget/extention
I would like to see a maplib widget/extention to allow easy googlemaps with custom layers embeded within a wiki page Maplib website I noticed that wikia has implemented this idea but have no idea how to bring it over to my wiki which is not hosted by them. http://dev.wikia.com/wiki/List_of_Wikia_Extensions 91.107.96.223 14:32, 26 January 2011 (UTC)!

ScrewTurn Migration Tool
We initially used Screwturn wiki for our internal knowledgebase, since it could be easily installed via IIS. But Screwturn isn't all that good, for reasons I don't need to discuss here. Anyone willing to create a migration tool? I have mediawiki installed, I just don't want to go through the pain of manually migrating each page.

Thanks!

Matthewpace 21:17, 20 September 2010 (UTC)

Pages baselines
I was requested to be able to baseline the page contents (to show a set of specific page versions of the articles in a namespace), one user request for future use of mediawiki in requirement analysis. I could manually copy the top history entry link to another document, but this does not scalate well :-)

Some extension (I couldn't find one) could collect this data for me and save and present them. When the pages change, I would stil have that previously recorder set.

--Cybermandrake 14:41, 15 September 2010 (UTC)

Display categories in search results
I would like to see in which categories an article is in the search results. I think this is not easy because every article has to be opened... but it would be a great feature... --nilsja


 * Yep that would be expensive and maybe not worth it. Remember: Special:Search is the most viewed page on every wiki. --Subfader 00:22, 2 June 2010 (UTC)

Add all pages in Category to your watchlist
I would like an Extension that would give the user the ability to add all pages in a Category to their watchlist. That way documents that have several pages but are in the same Category can be watched or unwatched quickly. --Johnp125 21:48, 10 March 2010 (UTC)

Inputting redirects while creating the main article
It would be nice to have some kind of extension where as I'm creating the page, I could also input multiple ways of getting to the page via redirects. In my case my wiki is related to grammar of a foreign language and there are many ways the user should be able to search for it, and it's a pain creating redirects one at a time.

So as a simple example, lets say I create the article "USA", i finish typing the article, then i have a box where I can enter multiple aliases for the article that become redirects. So I enter [ America ] [ United States of America ] [ US of A ] etc etc

and those all become redirects back to the "USA" page without me creating the redirects seperately one by one. I think this would be really useful for a lot of people. Let me know what you guys think 211.47.112.117 12:54, 31 January 2009 (UTC)


 * I would definitely be able to make use of that when setting up a wiki in it's early stages, such a for all the redirects for, say, Project:Staff, such as: Administrators  , Bureaucrats  , Moderators  , Project:Administrators  , Project:Bureaucrats  , Project:Moderators  , Project:Administrator  , Project:Modorator  , Project:Bureaucrat  , Staff  , Project:Administrator  , Project:Modorator  , Project:Bureaucrat  , and I'm sure there's more. --  Multiple Protection Levels  Talk  22:21, 21 November 2010 (UTC)
 * This sounds nice. I would love to use it. Bud0011 02:10, 22 November 2010 (UTC).

External Link - Redirecting
Is there possible to make one extension for redirecting to external links like www.mediawiki.org!

Code: or THinked nothing like that
 * 1) REDIRECT link title
 * 1) REDIRECT-awayfromwiki link title
 * I think you could maybe create a function in MediaWiki:monobook.js that looks for such redirects and changes window.location. Why would you need something instead of creating a simple link? --Flominator 09:35, 10 September 2007 (UTC)


 * because you want a page to be redirected to an external page. This is useful in calendars extension because when you click an event you can get it to go to an external page rather than just going to an ungly blank page with a link to an external page --211.30.184.13 13:25, 3 January 2010 (UTC)

Create an interwiki link with a destination on example.com and with the 'local' bit set? --Carlb 16:40, 25 September 2009 (UTC)

Delete Vandal - Delete a user and all pages that he edited/created
The purpose of this extension would be to make it easy to remove a vandal and any trace of what he did. I would like an extension that given a user name,
 * will delete all pages that have been created by that user.
 * reverts any edits by that user.
 * blocks or deletes the user
 * Puts him on a banned list (this is not critical since he is using random user names).

I would really like it it to be liked form the "Recent pages" page, along with the (Talk | Block) links.
 * Practically, it is not that esaily achievable I guess. I'm not going to argue the usefulness of it here, just the possibility of performing the tasks yo mentioned:

1) There is no point in deleting the user account, and, I guess it is enough to block it. As far as I know, MediaWiki doens't support deletion of a user account, because if even a single edit is left by that member, deletion of the account can mess every thing up (read below too).

2) Reverting edits is not easily possible. Suppose that he edits a page and modifies several parts of it. After that, a second user makes some more changes (may be, without reverting the vandal's changes even). Then, we may reach a point where software would be unable to undo vandal's changes (I'm pretty certain everyone of us have faced a "cannot undo this change because conflicting intermediate edits"-like message several times). So as you see, some edits cannot be reverted.

My two cents. Huji 12:31, 2 September 2007 (UTC)


 * Just because intermediate edits have taken place doesn't mean restoring a page to a previous state, with edits after that state, is not perfectly entirely possible since MediaWiki stores each difference between revisions. It's a mindless task of simply removing the unwanted revisions and combining the later revisions together. —Eep² 13:46, 2 September 2007 (UTC)


 * Well, MediaWiki doesn't really store diffs; it only stores revisions. Deleting a revision by a vandal only makes sense if all the changes made by him are reverted; otherwise, after the revision is deleted, it will look like the user who actually edited after the vandal has made the unreverted changes, which is wrong. Reverts are not possible in 100% of cases. That's what I know Huji 18:47, 3 September 2007 (UTC)


 * MediaWiki shows differences which can be used to compare revisions and, hence, remove differences/revisions by (a) certain user(s). —Eep² 02:23, 4 September 2007 (UTC)


 * When you say differences, what is meant? Display of differences is not the same as any merging feature that would need to know what to do with which side of the equation (e.g., what gets included/what gets removed in the merge). In addition, there is the challenge of information that is needed to be kept but is out of order on a given line. MediaWiki does not have this facility, even though it can display differences. --Jeffmcneill 23:57, 21 October 2007 (UTC)


 * The fact that not every change can be rolled back isn't enough to block a "Delete User" feature, be the user a vandal or not. The software can at least tell what it can roll back and what it can't (at least changes that are the latest for a page can certainly be rolled back). If the software can roll back everything, it does so and it deletes the user. Otherwise it could assign its changes that can't be rolled back to some sysop or other moderator account, roll back remaining changes, delete the user and notify the moderator. Lucrus 13:09, 12 February 2008 (UTC)


 * It would seem that the desired functionalities all exist in some form, but just aren't in one central place. The [revert] links to undo each of the users' edits to pages where they had the last word are on special:contributions, the mass-delete is in extension:nuke and the bannination is done from special:blockip. What's needed is to consolidate all of these tasks, so that one visit to special:blockip not only allows an admin to block the user, but also offers pre-checked checkboxes inviting the admin to revert the edits and delete the newly-created pages in the same one step - maybe even giving an option to protect them against re-creation. It would make the task of blocking open spambot proxies a few clicks shorter. --Carlb 17:59, 8 March 2008 (UTC)


 * Additionally, all versions edited by the vandal could get a hint like "the user that edited this version is tagged as vandal, so think twice before trusting its content". [Marc]
 * Hmm, one would think that the summary of the reverting edit would suffice to indicate the user's vandal status. Tisane 06:49, 22 April 2010 (UTC)

Advanced Reading Restriction for Anonymous Users
I am wondering if any extension can restrict the reading right of anonymous users. Examples may be that after specified pages viewing it would auto-direct anonymous users to register or it restricts the reading rate(ie, pages/hr ). I think that would be great to increase the proportion of registered users. Thanks for discussion.
 * Note that those restrictions suck a lot and actually end up in teh other direction. I never register at sites (mostly forums) where content is hidden for visitors. I just leave. --Subfader 09:32, 12 June 2008 (UTC)
 * However,that is why I dont use the original function of the Mediawiki,which can hide the information. I just want to give users a choice. You can just keep anonymous to get all information. For example, after 10 pages viewing, the extension directs user to register. But the anonymous user can go back to the normal page without any difficult.
 * Seconded. I need this too... My wiki-site is used for editing a (big) book for publishing. Registered users (a manually vetted bunch) get to see and edit full pages, and the anonymous visitors don't get anything at the moment. I'd like to change this to present the guests with partial chapters as "teasers" to build-up interest in the book...
 * Hmm, so would you base it on IP address? E.g., a given IP address only gets to view 10 pages? Tisane 06:55, 22 April 2010 (UTC)

Email Client
A extension that makes a special page for a E-mail client.
 * To email what to whom? --Lhridley 15:27, 14 February 2010 (UTC)

Disqus extension
An extension to allow for Disqus comments to be added to a wiki page. Should allow for customization of comment layout through HTML template, CSS file, and extension configuration. Possible solution includes a checkbox on the mediawiki edit form to enable comments on this article or not.
 * See Extension:AvbDisqus, which adds Disqus Comments in any place into any wiki page. Alexey V. Beloblotskiy 11:28, 25 Sep 2009 (UTC)
 * Or see Extension:MpDisqus, which adds Disqus Comments automatically right after each page. --Michael Platzer 15:18, 28 October 2009 (UTC)
 * I created DISQUS widget for Extension:Widgets - http://www.mediawikiwidgets.org/DISQUS --Sergey Chernyshev 17:40, 5 March 2010 (UTC)

Change signatures in old page histories
On an old wiki site I used to run, there was a user who's signature was "FUCK HEIL HITLER!" and we had to manually re-edit the signatures right across the wiki: if there was some way of fixing this with a new special page it would be good. Extension:ReplaceText almost does it, but not quite. I don't know what the SQL is to manually replace every signature, so a new special page would be helpful. --Sunstar NW XP 12:23, 19 October 2008 (UTC)
 * Why is Extension:ReplaceText not working good enough for that? What could a new special page do better? --Subfader 16:52, 19 October 2008 (UTC)

This is a cumbersome method, but when I migrated the content of Libertarian Wiki to Libertapedia, I exported everything into XML files and then did a search and replace to change every instance of "Libertarian Wiki" to "Libertapedia". It took a separate XML file for every namespace, though. Tisane 07:11, 4 April 2010 (UTC)

RSS / E-mail notification for new articles in watched categories
I'd like to see a feature that enables this: Add a catgory page to your watchlist and you receive notifications* about new pages being added to that category. Not about edits, moves or deletitions etc. simply only when a new article is added.

* Notifications: Add a new user prefs under watchlist: Notify me about new articles being added to Categories in my watchlist: [_] via E-mail [_] via my RSS*

That RSS should be a single RSS feed that is linked exactly there in the user. The feed is rsponsable for all additions. The content of the notification should simply be: linked article, date. I saw other wiki RSS feeds before and they failed displaying the page content which uses wiki markup so that would be a bad idea.

I know there is Extension:CategoryWatch but that sends E-mails for everything (edits etc.) like the normal watchlist.


 * It looks like you could combine code from Extension:AutoCreateTalkPage and also the "is-in-category" stuff (next section on this page) and get exactly what you're looking for! Timneu22 13:53, 29 March 2010 (UTC)


 * The hook is the correct one but it doesn't do "exactly" what I need: generating RSS feeds. --Subfader 12:56, 27 April 2010 (UTC)

red links for only sysop
Is it possible so that non registered and user can't see the red links but only the sypop can? Many guests on my website don't like it.

e.g.

Anyone other then sysop sees I like the colour red.

Sysop sees I like the colour red.

Sysop can edit anytime they like. When they edited red the link will be visible to everyone. Sachein 15:53, 24 June 2009 (UTC)


 * You might want to look into MediaWiki permissions. This is already possible.  There is no extension necessary here. 99.249.52.196 12:05, 21 January 2010 (UTC)


 * Shut up anon. That is actually not possible, but I don't recommend an extension like that. It really cuts down on contributing. --Jeffwang16 03:02, 31 December 2010 (UTC)

Mass creating pages
I'd like an extension where I simply type in the page names I want to create: [page1, page2, page3] then a box with the content: [hello world!]

Then it will create the pages: page1, page2, page3 all with the content that says "hello world"

This would be also useful for making redirects instead of creating them individually. However since this is spam sensitive, perhaps maybe it could only be used by sysops or some kind of similar restrictions. --Bluesoju 03:51, 28 June 2009 (UTC)
 * Please see Pywikipediabot/add text.py. JackPotte 05:03, 7 November 2010 (UTC)

Top_Bar
I like the way I can customize sidebar in the mediawiki:sidebar page. I'd like to have another bar for other links to customize that way. With a brand-new bar added I could manage my links better and make some appear at top, while other on the side and also manage different css for the two lists. Wonderfull if the content of that second brand new bar would be namespace-dependent and if the content of the page (mediawiki:topbar) it refers as: ........................ With that array and code like - foreach ($this->data['top_bar'] as $bar => $cont) { -  in the wiki/skins/myskin.php I'll had a nice bar based on namespaces. What the current extension do is changing the current bar, adding new functionality, they don't provide such a new bar...
 * NS_0
 * link_1_url | text_1
 * link_2_url | text_2
 * link_3_url | text_3
 * NS_1
 * link_4_url | text_4
 * link_5_url | text_5
 * I would love to have a second menu bar too. It would be nice to have a topbar. Superxain 14:47, 9 November 2010 (UTC)

Editing pages: visual and code view
MediaWiki software should have an extension which behaves like WordPress (used in creating blog pages). It means, people should have the opportunity to edit pages either visually (WYSIWYG) or edit code in some markup language.

The citing could also be easier. I could click a button in WYSIWYG view, a JavaScript window opens (or something like that...) and I could input the author, the title etc. separately. These ideas were originally proposed by user kanakukk in general discussion about et.wikipedia. --Jaan513 17:31, 23 October 2009 (UTC)
 * Hmm, hasn't Wikia implemented something like that? Tisane 06:45, 22 April 2010 (UTC)

Is there any way to age restrict content?
Including;


 * Having age verification on certain articles, unless a user is logged-in then it could check the users age.
 * For under-age users, or viewers that aren't logged in, having any "Adult" tagged images to generate thumbnails that are a generic image like "ADULTS ONLY".
 * Also allow differing age checks for both images and articles, such as PG, PG-13, and R-Rated.

Smile Lee 11:12, 6 December 2009 (UTC)
 * Perhaps a modification to Extension:ImageFilter is in order? Tisane 06:24, 22 April 2010 (UTC)

Extension:phpMyEdit
Is there someone out there, who can make a functional extension with the program phpMyEdit? I tried to, but I wasn't able to do this. Also I tried to run the script on a different page (subdomain) and build it in with iframe. But there were some problems. The iframe won't show the correct charset (I'm Austrian, so we have several different letters like "ÄäÖö" and so on), links or buttons won't work (just makes a page-reload instead of new database-entry) and so on. All this works if i open the page in an own window/tab. The database is not the same like the mediawiki's (it's still a mysql, but a different server), also there are different tables to read an write. You see the problem? You can also write me an email: stefan at jaritsch dot at 188.45.52.154 02:19, 21 January 2010 (UTC)

Extension for table filter
Hi, i need a extension to build a filter on my wiki tables. who can give me me a help?
 * What are the specifications of what you need? Are you thinking of something along the lines of the kind of filters MS Excel provides? Tisane 06:42, 22 April 2010 (UTC)
 * Here you are:
 * Go to http://tablefilter.free.fr/ and download last version of tablefilter script (actually 1.9.9)
 * Copy TableFilter_EN\filtergrid.css to skins/common/filtergrid.css
 * Copy TableFilter_EN\tablefilter_all_min.js to skins/common/tablefilter_all_min.js
 * Now go to skins/ directory and open yourskin.php file (where yourskin is the name of skin you are using)
 * Search:
 * &lt;script type="&lt;?php $this-&gt;text('jsmimetype') ?&gt;" src="&lt;?php $this-&gt;text('stylepath' ) ?&gt;/common/wikibits.js?&lt;?php echo $GLOBALS['wgStyleVersion'] ?&gt;"&gt;&lt;!-- wikibits js --&gt;&lt;/script&gt;
 * After Add
 * &lt;!-- TABLEFILTER START --&gt;
 * &lt;script type="&lt;?php $this-&gt;text('jsmimetype') ?&gt;" src="&lt;?php $this-&gt;text('stylepath' ) ?&gt;/common/tablefilter_all_min.js"&gt;&lt;/script&gt;
 * &lt;style type="text/css" media="screen"&gt;
 * @import "&lt;?php $this-&gt;text('stylepath' ) ?&gt;/common/filtergrid.css";
 * div#navmenu li a#lnk02{
 * color:#333; font-weight:bold;
 * border-top:2px solid #ff9900;
 * background:#fff;
 * }
 * &lt;/style&gt;
 * &lt;!-- TABLEFILTER END --&gt;
 * Search
 * &lt;?php $this-&gt;html('bodytext') ?&gt;
 * Afer Add
 * &lt;!-- TABLEFILTER START --&gt;
 * &lt;!-- creating fake table to prevent js error --&gt;
 * &lt;table id="wiki_table_filter"&gt;
 * &lt;/table&gt;
 * &lt;!-- initializing the script --&gt;
 * &lt;script language="javascript" type="text/javascript"&gt;
 * //&lt;![CDATA[
 * var wiki_table_filter_Props = {
 * filters_row_index: 1
 * };
 * var wtf = setFilterGrid( "wiki_table_filter",wiki_table_filter_Props );
 * //]]&gt;
 * &lt;/script&gt;
 * &lt;!-- END OF TABLEFILTER --&gt;
 * Close and Save the file.
 * now when in a table you add: id="wiki_table_filter" you have your filtrable table.
 * Close and Save the file.
 * now when in a table you add: id="wiki_table_filter" you have your filtrable table.

Automatically convert wikilinks to permalinks
I'd really like an extension that instantly converts all the wikilinks on a given page to permalinks. The rationale for this is that I have wiki pages reaching end of life that refer to other, active pages - and I want the dead page to link to older versions of the still-active pages, specifically the most up-to-date version at the moment the linking page went dead.

So for example, pressing a button on this page might convert the link Manual:Extensions to Manual:Extensions.

I'd be especially grateful if anyone can point me to an extension that already does this, since I couldn't find one :) Playclever 17:43, 4 March 2010 (UTC)

Form to add information
I would love to see an easier way to add information to a page. I run a Wiki for people to add their biographical data and there is a set format we use. It would be great if we could have a form they could fill out and it would add the information to a page or create a page (if it does not exist) without me having to do anything.

Example:

Bishop John Doe wants to add his information. The page to add his information is title Current_Bishops_D. There are three entries in the page already. Bishop John David, Bishop James Davidson and Bishop Chris Dubbs. Bishop Doe fills out the form to add his information and it automatically places his information in alphabetical order by last name on the page without removing the existing three entries.

This is the current format of the entries:

== The Most Rev. Bishop's Full Name == Title, [Website address Church Name] Street or Mailing Address City, State Zip Code Phone Number: Email Address: [mailto:Email Address Repeat Email Address here] Current Public Ministry: Born: Date of Birth Faith of Origin: Name Entered Autocephalous Movement: Year Occupation: If you have one besides the ministry Education: Ordinations: Last Updated: Today's Date
 * Title, [Website Address Church Name], City, State
 * Degree, Seminary, Year
 * Deacon, Date, by Bp. Name and Bp. If Needed.
 * Presbyter/Priest, Date, by Bp. Name and Bp. If Needed.
 * Bishop, Date, by Bp. Name and Bp. Name.

There would also need to be a way to call a different form for three separate sets of pages. I tried to use Semantic Forms, but after trying for days to understand the process, I gave up. Any help on this would be greatly appreciated. --70.152.170.211 01:02, 11 March 2010 (UTC)

Login Seguro
Seria interesante una extension que realize un login seguro sin necesidad de utilizar SSL (https), que sea de la misma forma que realiza el login los foros del tipo SMF o PHPBB. Una opcion es con un token del tipo Cliente (JavaScript) --> md5hash(password_cliente+tokensession)=md5hash(password_database+tokensession) <-- Servidor (php). El tokensession es un valor aleatorio que se envia en el formulario del login (varia cada vez qeu se loguea) y el ciente envia un hash que se verifica con el hash calculado por el servidor. Esto seria una solucion a posibles sniffeos de trafico dado que el password viaja en texto claro.

Adding References
I think it would be much more simple to add references if it would be possible to add them in a pop-up window (like Wikipedia beta almost allows me to do). --Kanakukk 20:20, 20 March 2010 (UTC).

Removing References (easier copy-paste)
There should be a button which allows me to remove all references. Since I copy-paste texts from wikipedia often, it is quite annoying to remove reference-numbers ([1], [2]..). --Kanakukk 20:20, 20 March 2010 (UTC).
 * I suppose it would be easy to write a script to remove ref opening and closing tags and anything in between. As for adding references, what about wikipedia:Wikipedia:RefToolbar? Tisane 06:26, 22 April 2010 (UTC)

Photobucket/Imageshack uploader
An uploader to replace Special:Upload to a certain pre-existing imageshack/photobucket account, specified by an admin/whoever has access to LocalSettings. For wiki's with limited storage. Extension also tells server where image is located, so can be added like normal images? --81.111.4.175 20:33, 27 March 2010 (UTC)

Paypal Integration
I need an extension which can integrate articles with paypal. ie at the end of each article ( only article namespaces ), there should be a button which says Bid and the highest bid pays for the article

I am trying to turn a wiki into an article selling market. So it should have a 1) local money handling system ( my clients write article and users buy the content and that amount is transfered to the authors account, with a little bit fees incurred, which goes into my pocket. 2) Paypal Integration with bidding made available. Here, users bid for articles and they mention how much they are willing to offer . The writer is capable of accepting that bid or wait for another user to bid . 3) All users needs to have an account to participate.

and more ..............

I want it to be something like constant-content.com but basically a wiki. I am willing to pay about $100 to those who are interested in working on this extension. Please contact me by donateroid@gmail.com
 * None of these extensions give you the functionality you need, eh? Tisane 06:36, 22 April 2010 (UTC)

No, all of them are donate buttons and they aren't at all what I am looking for at the moment. 117.204.82.81 02:32, 24 April 2010 (UTC)


 * Extension:SecureHTML --Subfader 13:14, 27 April 2010 (UTC)

Custom WavPlayer
Hi there. I've been looking around, but unfortunately I cannot find what I'm after. I'm trying to find an extension that can play wavs when you click on some text. This'll be for TF2 Wiki and we have things called 'voice commands'. At the moment, we're merely linking to the sound file's external link, and I feel this is unacceptable. I'd rather have an embedded player.

If you could take this page as an example, I'd like the line, "Medic!", for example, to have a little image beside it (Decided by the installer), then when the user clicks on the icon or the word, a small player appears beneath the word that buffers then plays the file.

Prefered syntax would be something like, or similar. So for the above "Medic!" example, the syntax would be

Please see this image for an example of what I would like.

If you could help me I'd be much obliged. Thanks. Smashman 21:15, 21 April 2010 (UTC)


 * Take one of the player-extensions (e.g. Extension:Player) and combine it with Extension:ToggleDisplay. This should get you exactly, what you want. Sidcom 10:45, 27 April 2010 (UTC)

CKEditor
What about an extension so you can use the CKEditor in MediaWiki. See http://ckeditor.com/ --Emilkris33 19:41, 11 May 2010 (UTC) Yes, Please enable Mediawiki users to use ckeditor - integrate ckeditor into mediawiki or an extension please - thanks We want the way to integrate ckeditor, thanks very much. We're also waiting for the possibility to integrate the CKEditor into our mediawiki

Frontpage Slideshow for Mediawiki(?)
Is there any solution for MediaWiki to make the main page with an slideshow like Frontpage Slideshow (Joomla)?? Chernobyl 00:25, 10 June 2010 (UTC)

mediawiki doesn't have workable rating tool yet
it's quite a surprise that mediawiki still doesn't have a workable rating tool which can display the list of best rated articles, best rated of 7 days, a month and all time.

Extension:Rating_Bar's author spent a great effort on making similar thing, but unfortunately the extension seems to be still in very beta stage...with too many bugs to fix. Looking forward to seeing an hero to solve this problem. --Dullmau 19:24, 23 June 2010 (UTC)
 * Was lookging for a rating tool earlier today funnily enough... 92.15.89.110 02:16, 27 June 2010 (UTC)

Using sortkey as the displayed title in categories
Basically, in a category, have a magic word that can be added to it to make the sort keys become the displayed titles within a category. Ex: Category:X has the magic word '__SORTKEYASTITLE__' (or similar) in it. If article 'Y' has in it, it is listed (and sorted) under the title 'Some article' and before the entry for 'Y'; instead of being listed before 'Y' but still as the title 'Z' (without __SORTKEYASTITLE__). If you don't understand, I can try to explain it again. Rabbitfang 20:42, 27 July 2010 (UTC)
 * Extension:PeopleCategories should do what you want, but it uses an array to specify categories rather than a magic word. Reach Out to the Truth 04:56, 29 July 2010 (UTC)

summation of all members in a category and all subcategories
the extension i am looking for / proposing is one that could perform a summation of all sub-categories under a given root category; up to a given depth limit.

If this does in fact become a proposal, then I would like it to have the following settings:
 * $root_count = {true | false}
 * include the members of the root in the count


 * $depth = {1, 2, 3, ...., max(int)-1 }
 * maximum depth of recursive calls it needs to go for; defaults to 1.


 * $subcategories = {true | false}
 * include # of subcategories of a category in it's count.
 * May count a subcategory and it's members together....should this be avoided?

Bud0011 23:29, 4 August 2010 (UTC)

Display categories added by templates
Include a list of the categories added in templates. I can think of 3 ways to do this: Duskey 06:52, 5 September 2010 (UTC)
 * 1) Include the templated categories in the bottom category display and color their background color (other than grey) and show the templates adding them on mouseover.
 * 2) A simple tree list at the bottom of a previwed page similar to the list showing templates used a preview. Adding any categories they include under them would be sweet.
 * 3) A list in the editing tools widget, like so:
 * Template 1
 * Category 1
 * Category 2
 * Template 2
 * Category 3

Display named references
Display a list of named references in the article with the ability to jump between them and go to the "parent" named reference. Duskey 06:52, 5 September 2010 (UTC)

Category request
Hi, I would like an extension that displays articles in a category listing in a manner that removes anything before : in a title.

In other words if I have an article titled Mediawiki:How to install, and it is categorized under Mediawiki. I would like it to be displayed in the category list as How to install. In short omitting the : and everything before it. Not deleting it, just removing it from the display.

Thank you.


 * That can already be implemented, and does not require another extension. Just use, which automatically sorts it by the name of the article after the namespace (such as MediaWiki:). —MC10 (T•C•L)  05:21, 3 November 2010 (UTC)


 * I'm not talking about sorting after the namespace. Let me show you. Here is a category listing of a bunch of tutorials for a software program called Ableton Live. http://en.wikiaudio.org/Category:Ableton_Live    - I want to have a way to keep Ableton Live: in the title of these articles, but I don't want it displayed in the category. It's simply ugly. Thank you67.169.112.215

Repeating thing
Hi. I'd like to request something like because currently that is not possible other than using: which does work on this template(test it) or use but the first one only limits to 99 repeatings, as after that, starts to show, and if 1 is removed and 0 is replaced, (text to be replaced)E+(text)(text) shows.

Anyway, something like #repeat would be very useful in my opinion. I hope this is possible.Joeytje50 13:34, 5 November 2010 (UTC)

Upgrading SpecialUploadLocal
See: Extension_talk:SpecialUploadLocal we need a new version for 1.16. thank you. Adamtheclown 08:06, 15 November 2010 (UTC)

Duplicate File Namespace
Hi,

would it be possible to create a new Namespace that does exactly the same things than "File:" namespace, but treated as a différent namespace in all Mediawiki process. The goal would be, used with Extension:Lockdown, to completely hide this namespace from non-authorized users.

For example, I uplaod an file as usual,  , and everybody can see it.

But, if I upload a file with this extension (and if I have the corresponding right),  , only the authorized users can see it (both in the description page and if put in a non-protected page).

I've found Extension:NSFileRepo but I'm not sure that this is I need. Any idea ?

? Dr Brains 8 Doléances 8 07:05, 26 November 2010 (UTC)

Categorize usage of a MagicWord
Hi, I would like to know how it is possible to automatically categorize pages that use a particular MagicWord, like it is (was) done on Wikipedia for __INDEX__ and __NOINDEX__. I have'nt found the way to do that in the MW source code.

On my wiki, I've installed Extension:UserFunctions and Extension:Parser Functions. As it is an opened wiki, they can be used to hide vandalism from sysops. Modify Extension:UserFunctions (who is quite simple) to add a category on the pages using it would help sysops to found this kind of abuses.

This could be an option by setting a bolean variable in localsettings.php.

Is someone can do that ? Or at least tell me how to do ?

? Dr Brains 8 Doléances 8 10:07, 8 December 2010 (UTC)
 * Do you mean, like DEFAULTSORT or something else? Bud0011 18:30, 8 December 2010 (UTC).
 * No.
 * I mean like __INDEX__ and __NOINDEX__, who categorize the pages where they are used in Category:Indexed pages or category:Non indexed pages (but I think this feature has been disabled in Wikipedia projets for __NOINDEX__ ), or like __HIDDENCAT__ who categorise the category in Category:Hidden categories.
 * That I want is, if someone use any of the MagicWords of Extension:UserFunctions, the page is automatically added in a category named Category:Page using UserFunctions (or any other title defined by a Mediawiki: message).
 * Is it possible ?
 * ? Dr Brains 8 Doléances 8 22:38, 8 December 2010 (UTC)
 * Ok, so then what function would marking it as "INDEX" or "NOINDEX" provide? (i don't know if it is possible, but if i get more details on what you are trying to do, i may be able to point to a solution). Bud0011 05:06, 9 December 2010 (UTC).
 * Quite all the functions provided by Extension:UserFunctions would add the page where they are used in Category:Page using UserFunctions (ar another name) (The ultimate goal is to use Special:Recentchangeslinked/Category:Page using UserFunctions as a watchlist to see possible abuses).
 * (I am repeating because as you can see following my sign, english is not my mother tongue and I don't know if I explain my goal correctly).
 * As __INDEX__, __NOINDEX__ and __HIDDENCAT__ automatically had a category when they are used, I assume that there is somewhere in Mediawiki source code a native function to do it, but I didn't found it (MW 1.15.0). I searched in /includes/MagicWords.php but I saw no variable or function meaning that the defined magicwords would automatically add a category or not. Perhaps in /includes/parser/ files ?
 * ? Dr Brains 8 Doléances 8 14:05, 9 December 2010 (UTC)
 * Mmmh, I've found function doDoubleUnderscore( $text ) in /includes/parser/Parser.php (~2/3).
 * Whith 'hiddentcat', it gives $this->mOutput->setProperty( 'hiddencat', 'y' );
 * With 'index' and 'noindex', it gives $this->mOutput->setIndexPolicy( '(no)index' );
 * So I assume the solution is somewhere in theses functions, setProperty and/or setIndexPolicy.
 * ? Dr Brains 8 Doléances 8 14:21, 9 December 2010 (UTC)


 * I believe Parser->addTrackingCategory adds the cateogry. Parser->doDoubleUnderscore shows how to call it. —Emufarmers(T 18:50, 9 December 2010 (UTC)
 * Nice. I think those will be helpful. Bud0011 19:02, 9 December 2010 (UTC).
 * I do not have addTrackingCategory I have addCategory (MW 1.15.0) :


 * I've tried to copy this in the first UserFunction (ifanon), but it doesn't work. Any suggestion about how to do it ?
 * ? Dr Brains 8 Doléances 8 00:51, 12 December 2010 (UTC)
 * Sorry, but this is beyond the help i can give. Bud0011 07:53, 12 December 2010 (UTC).

User vigilance
Unused high privilege accounts are a security risk, as demonstrated by this case. How about an extension that monitors high privilege accounts? If a say an admin does not access logged-in or logs in within the expiry time of their cookies, an email notification is sent to them and they are to respond to email somehow, and log in, otherwise those privileges are automatically revoked. MyrtonosGive me new messages 14:00, 19 December 2010 (UTC)
 * I like it, but i don't like the "automatically revoking" part. That should still be in the hands of a human. Bud0011 22:40, 19 December 2010 (UTC).
 * I don't understand why you prefer desyopping to be in human hands. With this extension, it would still be possible for users with the desysop-permission assigned to revoke a users administrator privileges whenever they take the action to do so. But with the extension installed, if a high privilege user if offline for more than the expiry time of the cookies, an automatic email notification is sent, and since they are desysoped if they don't respond and log-in within a set time, I don't see why it shouldn't be automated. The prevention of an automatic desysop is in human hands, this is a failsafe measure. --MyrtonosGive me new messages 06:45, 20 December 2010 (UTC)

Email blacklisting
While there exits an extension wich can block creation of username in violation of a username policy, there doesn't seem to be one for blacklisting emails. The idea would be that a user who specifies a blacklisted email address, they are not email confirmed, and cannot do anything that requires one to specify a valid email address. Part of the reason why this might be a good idea is that some wikis require email confirmation to edit pages, and having an email address like Sneakmail enabled might, in some cases go against the intent of this restriction. MyrtonosTry liquid theads 09:46, 18 January 2011 (UTC)


 * $wgSpamRegex should be used on account registration. https://bugzilla.wikimedia.org/show_bug.cgi?id=26808 --Subfader 19:59, 19 January 2011 (UTC)