Extension requests

__NEWSECTIONLINK__

Warning: There's no guarantee anyone will ever see anything posted on this page, unless you go find them and steer them to it.

This is not a good place to post if you are hoping that someone else will implement your idea. In fact, you probably shouldn't post here at all.

It would be good if people interested in actually working on things could go through this page, pick out things that look worthwhile, and:
 * 1) Move them to Bugzilla where progress can be tracked
 * 2) Start working on them!

Statistics and timelines
I have a wiki that contains a lot of pages for education, I would love to have several statistics collected from this. That is stuff like:
 * Ratings of the materials
 * Use statistics - who used this, for how many students, and when

The "ideal" would be - an auto template that could be used much like a rating tool, only it would record the user, the data and the number of students, and possibly an evaluation. And based on this one should be able to extract timelinedata - for the teacher, for the specific page etc.

Guess that the current timeline extension would do well - but can I collect/extract such data and call the timline extension dynamically? --Asset 20:55, 16 November 2008 (UTC)

Media Category
is there extensions for creating a gallery off a category who includes media?
 * Images or images

--Zizanzu 14:28, 4 August 2008 (UTC)?

Programming Documentation and Extensions to copy from

 * Category:Ajax_extensions other ajax features
 * Extension:Link_Suggest, add a feature to the edit window and allows you to change the text.....
 * Extension:Lockdown, can be used to control usage?

Simple Download System
I've looked everywhere and cannot find a download system like paFileDB for mediawiki! Now I'm not looking for something like paFileDB, although I wouldn't mind it. I was looking for something a little simpler that can be easily be designed without to much trouble!

I developed a proposal which you can download in .pdf format http://www.designermotion.com/projects/web/mediawiki/docs/mediawiki_proposal_extension_download-v1.pdf

I'm hoping someone will be interested in creating such an extension as I'm planning to add over 400 download pages to my wiki.

Thanks for your time--unknown 02:04, 9 June 2008 (UTC)

Dynamic page update from other pages
Let's say on one page, we'll see page "Renee", I have the following wiki stuff (displayed in code here):

===Year 1=== *Spring: Development :Practice in dev :Exposure in component *Summer: Visit :Practice in dev :Exposure in area *Autumn: Teaching :Practice in dev :Exposure in teaching *Winter: Development :Practice in dev :Exposure in component ===Year 2=== *Spring: Teaching :Practice in dev :Exposure in Teaching *Summer: Visit :Practice in dev :Exposure in area *Autumn: Teaching :Practice in dev :Exposure in teaching *Winter: Development :Practice in dev :Exposure in component

Just to give a rough example, at least. Now, let's say this goes on for some 20 years, and with potential to keep on going. It is also repeated (but with differences in what happens year to year) in other pages, like "Jariya", "Lea", "Nike", etc. Now, I want to know if there is an extension that can take the seasonal advancement, interwiki-style, and place them in a single page, we'll say "Advancement", with an output kinda like this:

===Year 1=== ====Spring==== *Renee: Development :Practice in dev :Exposure in component *Jariya: Teaching :Practice in teaching :Exposure in influence *Nike: etc etc

Now, I originally used Labeled section transclusion by wrapping everyone's year 1 spring as 'year1spr', then 'year1sum', then 'year1aut' and 'year1win', then 'year2spr'.... you get the idea, and including the transclusion on the advancement page. It worked, however, adding a new name is a pain. You need to write the new name, write the new transclusions, and when you have 10 years and growing of transclusions to rewrite from 'year1spr' to 'year3spr', then 4, 5, 6... then repeat for the other 3 seasons, it's annoying and not very efficient.

What I'd like to know is if there is an extension that could do what I'd like more easily? Especially if it could do it dynamically and automatically update like Transclusions did, but without needing to add 40 tweaked lines when adding someone or removing/renaming someone?

I thought I could maybe use the MySQL extension and have a DB with the changes in them, but that doesn't seem like it'll work too great overtime.
 * Thanks

Game rating system (0% => 100%)
Does anyone know if there is a little extention that makes it possible to display a rating for a game, like normal gameratings, from 0 to 100%? And a little thing to let anyone give a rating (with IP check)?
 * Uhh, use the page history and a template - that should be enough. Tohd8BohaithuGh1 (talk | contribs) 01:48, 4 November 2008 (UTC)
 * Use the search --Subfader 20:38, 5 November 2008 (UTC)

Google AJAX extension
An Extension that gets google search results with AJAX API presented by Google. The results should be gathered with wiki markups. For example with a text britney, the extension must turn the Google results within the page. --88.229.252.158 07:46, 13 January 2007

Display Name
There should exist an extension to allow the admins or maybe even the users to select which name is displayed. Currently the username is used, but why not have an extension that allows all references to a username also allow for reference to a the Nickname, or the Real Name. (Example: Recent Changes page lists lots of users, but the admins could force it to display the Real Names instead of the usernames, or if the localsettings variable isn't set to force it, let the users select which name is displayed). --71.145.131.12 22:21, 14 January 2007

Extensions to Enable Wiki of 3D Geometrical Models
Hi, we would like to create a Wiki of 3D geometrical models which are built with a product called Zometool. We already have the software to build the models and are working on a browser plug-in which will allow users to manipulate these models in their browser window. We would need for users to be able to:

a) Publish their models on the wiki (even if they're noobs).

b) Access the browser plug-in from the wiki so they can see/manipulate the models in the wiki article.

The publishing aspect would require functionality similar to that requested by Blckdmnd99 in "File Upload as Part of Article Creation" and also Barrylb's "New Article Form".

The modeling program would export jpegs, csv files with a description of certain model parameters (number of parts, etc.) and the model file itself. Ideally, this would be transformed into part of a wiki article which would include the jpegs, a table with the required parts for assembling that specific model, categories (taken from the csv) and a link to the 3D model file itself.

The plug-in access, I would imagine, would be similar to adding quicktime or flash compatibility.

If anyone is interested in helping us out with this we would be willing to pay for the functionality.

Thanks, --Carlos 07:36, 30 January 2007 (edit) (undo) Zomenut


 * I already have something similar in Java called Wiki3D that might help you getting started. It is all open sourced under the BSD license.
 * Regards, Luc

Internal Article Social Tagging
I would like an extension that puts a "Digg"-like tag on each page. By tagging those pages, there would be a special page or extension that allows those articles to be dynamically presented in order of votes. This is not the same as presenting a link to Digg itself or any other social bookmarking sites. This feature would allow a MediaWiki wiki to have its own pages rated by readers and then have a summary page that showed the relative rankings.

Cladograms
An extension to create graphic cladograms. This, with the right options, could have other obvious applications such as family trees (and similar material) and sports brackets. This could be based on PhpSyntaxTree and EasyTimeline, both of which propose more or less similar possibilities. en:User:Circeus --08:06, 26 June 2007


 * see Extension:CategoryTree if you can model your data using categories. --Purodha Blissenbach 10:16, 8 September 2007 (UTC)

Drop Down Box
I would love to have an extension that allows a drop down menu. Not to redirect to a different page, but just to change the status of item. If this is not enough information, feel free to drop me a line as this is quite important. 129.57.10.6 19:34, 19 July 2007 (UTC)

gibsonmarshall_sg@yahoo.com

Easier automatic categorization
Extension:CategoryHook can do automatic categorization but it requires esoteric PHP coding and isn't very user-friendly. I'd like a more GUI-centered approach for, oh, 90% of users out there... -Eep² 03:01, 24 July 2007 (UTC)

Multi-select namespace search
When searching, instead of all the checkboxes, which are nerve-wracking to select/deselect, why not a multi-select menu? -Eep² 03:19, 25 July 2007 (UTC)


 * My attempt: Extension:Multi-select Namespace Search--unfortunately, it doesn't work. :/ -Eep² 17:22, 26 July 2007 (UTC)


 * It works now (for a few weeks, actually, with the help of another user), but it's not a proper extension and just a hack. If someone can "extensionize" it, that'd be super. —Eep² 12:03, 15 August 2007 (UTC)

Media Player
I'm Want to Suggest on Extension who allows To look at Videos And Listen on Music This is Because i'm looked long for one Extension who can this!. And its 2 different formats i'm want to have in this extension Formats: .mp3 .ogg


 * Check Category:Media handling extensions. -Eep² 22:07, 13 August 2007 (UTC)


 * Tryed but No one of them works - --62.128.243.228 11:19, 14 August 2007 (UTC)


 * You tried Extension:Mp3 and Extension:Player? —Eep² 12:20, 14 August 2007 (UTC)

Yes, And Many Others - --62.128.243.228 13:11, 14 August 2007 (UTC)
 * What happened? --Flominator 13:30, 15 August 2007 (UTC)

Some of them dident show, And the one named player Did show but dident play it --62.128.243.228 14:19, 16 August 2007 (UTC)
 * Are you sure that your browser supports it? --Flominator 10:34, 20 August 2007 (UTC)

Automatic Linking (with Bug)
I'd really like to have an extension that allows automatic linking as an option (because I can't ask all of my users to know of and link to every other page that exists in the wiki on their own... Can this be done?  If anyone knows of a current way to do this please reply to this thread.  Thanks. --129.111.144.30 17:49, 28 March 2007 (UTC)


 * See Extension:AutoLink. 89.52.129.174 12:25, 3 August 2007 (UTC)


 * There is a realy little bug in that Extension:AutoLink - but I don't know PHP to repair it. 89.52.146.8 07:03, 6 August 2007 (UTC)
 * Try Extension talk:AutoLink. --Flominator 12:10, 15 August 2007 (UTC)


 * I did it with no success. Only [ ] has to be added to the to the mapIgnoringBlocks. But I don't now how to do it. Is here someone who knows php?89.52.137.94 06:59, 21 August 2007 (UTC)


 * Do you mean a single set of brackets? If so, I added it (but haven't tested it) to extension:AutoLink. —Eep² 07:40, 21 August 2007 (UTC)

Auto short URL links
You enter http://www.mediawiki.org/w/index.php?title=Project:Extension_requests&action=edit&section=new to an edit page and the system makes the article display mediawiki.org just as if you'd have entered mediawiki.org. Shouldn't affect existing [url Alt text] entries but all URLs that are eneterd as above --Subfader 13:50, 22 August 2007 (UTC)

Frappr Extension
I assume its really easy, but I don't know php. I'd really like to be able to embed a frappr (www.frappr.com) map into my wiki so that users can mark where they are from. If this is more simple than I realize please just email me. dave at consumersolidarity.org

75.111.44.66 02:24, 30 August 2007 (UTC)
 * it seems to be shockwave flash, so Extension:Flash ought to work. --Flominator 09:38, 10 September 2007 (UTC)

Advanced Linking
Tags:  - Start tag to activate the code  - End tag for the end of the code - The tag will be replaced with typed text in The text field, This tag gonna get the filepath who is typed in the text field - the tag will be replaced with typed text in the domainname text filed

Code:  url=http://www. / Action= (&action=edit&section=new) To Edit the page | (noaction) For no Action Pagebeforenter= Yes or no Linktext=Pagename Image= YPagename or no text Category= name Namespace= Namespace name

Actions: &action=edit&section=new - For editing a wiki page noaction - If no is the action the text in the field willl be produeced in the link as notext

Other Commands Pagebeforenter - you will enter a page with some information for the link place, And a directly link with the text enter Linktext - if you select no pagebforenter you will get a link text like this link yourlinktext Namespace - Choose the namespace Category - Choose the category Image - Image:file.format if you have a image you will use with the directly link or a link to the dynamic page pagebeforeenter!...

Parameters url=http://www. / Action= (&action=edit&section=new) To Edit the page | (noaction) For no Action Pagebeforenter= Yes or no Linktext=Pagename Category= name Namespace= Namespace name Image= Pagename or no text

This Idea is by Zizanzu

Can this be a good idea?.it need to be little imrpoved but a good start

WhosOnline extension
I'm not sure if this request fits here fully or not. Anyways, I was trying to help someone over IRC to make Extension:Whos_online work on MediaWiki 1.10.x and we ended up here: code on Pasty.net

The code is corrected, in regards to using the correct table and generating the correct text in $output variable. However, the way $wgOut->parse is used, makes some gibberish text to be added to the page. I didn't know how to fix it, so I though I might ask others for help here. Practically, it may be only a few seconds for a developer to figure out what the problem is. Huji 20:41, 31 August 2007 (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)

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]

Slideshow with Lightbox
I'd love to see an extension that would allow to activate a slideshow with Lightbox like the one working on this page :
 * Dialogues en Humanité - Galerie

--Dieudo 14:10, 3 September 2007 (UTC)


 * My Lightbox2 hack can do this. It works best for only one image gallery; if there are multiple galleries, Lightbox will think they're part of the same slideshow. &#x2014;alxndr&#x00a0; (t) 21:30, 19 September 2007 (UTC)
 * Hack is now an extension: LightboxThumbs. &#x2014;alxndr&#x00a0; (t) 05:04, 23 September 2007 (UTC)

Watching Subpages
I'd like to see an extension that would add all subpages to your watchlist when the main page is added. In otherwords, if I were to add MAINPAGE to the watchlist, it would also include MAINPAGE/subpage in the watchlist and all associated talk pages.--Dukeruckley 15:18, 3 September 2007 (UTC)

Category And Namespace...

 * Category
 * Category logo (upload image called Categorylogo:categoryname.png, The logo will be showne when your viewing a page with a namespace who have a logo (if not a logo,it will display wikilogo)
 * Category Css (viewed from [[Mediawiki:skin/category:categoryname.css, if your viewing this category you get that css)
 * Categorysidebar (And it wil come up a sidebar for the category in chossed place (it should be possible to writting nothing like __Categorysidebar__ in the sidebar for current place you gonna addig)
 * If you type down nothing like you will get displayed how many pages in this Chossed Category


 * Namespace
 * Namespace logo (upload image called NS:namespacename.png Or Namespace:namespacename.png, The logo will be showen when your vieweing a page with a Namespace with a A Logo i(ff not a logo it will display wiki logo))
 * Namespace Css (Made in Mediawiki:skin/Namespace:Namespacename.css )
 * Namespace Sidebar (And it wil come up a sidebar for the category in chossed place (it should be possible to writting nothing like __NAMESPACEsidebar__ in the sidebar for current place you gonna addig
 * Recent changes on Namespace
 * If you type down nothing like you will get displayed how many pages in this namespace


 * News
 * A Option for turning up Message box in the localsettings.php £wguse Messagebox= True/false; (Extension:Message_Box)

Here is some ideas i have for future extensions and Mediawiki!.... - --Zizanzu 13:11, 6 September 2007 (UTC)

Lossless rotation of images
As requested here an extension that is able to rotate images like the one on flickr. --Flominator 09:31, 10 September 2007 (UTC)
 * Commons:User:Rotatebot meanwhile does this. --Flominator 14:46, 25 January 2008 (UTC)


 * I strongly support this request. I think it would be even better if not the file itself would be rotated, but if you could chose the orientation like the image size wherever you embed the image. Don't know if that is possible, but it would be really helpful. --Gollum 23:18, 22 February 2008 (UTC)


 * MediaWiki uses external utilities such as gd or ImageMagick to resize images. All of these have capabilities and functionality beyond that which MediaWiki currently exposes; for instance "ImageMagick supports about 100 image formats and can perform impressive operations such as creating images from scratch; changing colours; stretching, rotating, and overlaying images; and overlaying text on images."
 * The images are normally handled by core MediaWiki code (not extensions), but there are exceptions - such as extensions which use images as clickable links or embed external content. Perhaps there's something there that could be used as a starting point for new code? --Carlb 18:18, 8 March 2008 (UTC)

we need this

 * It would be a real asset to be able to temporary crop or rotate an image already on the Wiki. A tag could control how an existing image appears so we can make it appear rotated or indeed cropped or lightened to show an image. This way one image could be used instead of having to upload several. This would make it easier for non-graphic users to manipulate images. All very easy to do via Imagemagick.


 * Something like
 *  or  


 * How about it MediaWiki? --Stuart Halliday 12:05, 19 October 2008 (UTC)

User Notification on Article Edit
This would be the inverse of the watch feature, in that the article text would define one or more usernames to notify whenever the article is changed. This is a "PUSH" as opposed to watching being a "PULL". It would be very useful for meeting minutes which might contain action items or other information subject to change. The entire group would receive an e-mail notification as if they had selected that article to watch. The wiki text for this might be:

 User:Username1 User:Username2 User:Username3

This would also cause the listed user's names to be shown on the page, in a box similar to the Table of Contents box but with a specified caption, to serve as a reminder that these users are to be notified of changes. Bill Johnson 02:51, 13 September 2007 (UTC)


 * After some further searching, this appears similar to Extension:Todo Tasks. Possibly that extension could be used along with a different template to achieve the above result. Bill Johnson 03:07, 13 September 2007 (UTC)

Review Date
An extension to whereby you can add a tag onto a article:-

25.12.2010

then create either a special page or a section on the Main Page of the wiki showing articles past or near their review date.

Useful when creating documentation for a particular project or something that needs to be regularly checked for relevance / accuracy. --Nomis35 10:24, 19 September 2007 (UTC)
 * You could just create a template and add that to the article. The Review template would contain a date-parser function so that if the date given by the article (25.12.2010 in this case) was today or in the past, it would add  to the article. Then keep tabs on that category and you'll always see what articles need to be reviewed. After review, change the review date in the  call and the article will drop out of the category until the new review date comes up. --Jonathan Kovaciny 22:38, 4 October 2007 (UTC)

Thanks for the suggestion, I'll have a go and see what happens.--Nomis35 19:13, 5 October 2007 (UTC)


 * I suggest using Semantic MediaWiki. It lets you define dates and can show a timeline (and much, much more very useful things). See for an example. --Tbleher 10:06, 14 February 2008 (UTC)

Viewcount by Date
A list of page views per day for each page, so I can know whether or not to rearrange the structure of my wiki.
 * You'd probably get more useful information by adding Google Analytics or another tracking service to your site. You can just add the tracking code to the bottom of /skins/MonoBook.php and that will cover nearly all of your users. Add it to the other skins if you think they're being used a lot. --Jonathan Kovaciny 22:32, 4 October 2007 (UTC)

Search statistics
Is there any decent method of tracking searches being run? I want a list, ordered by decreasing frequency, of the things my users have typed into the search box. I also want to be able to split this list into those terms for which there is an existing article, and those for which there is not. This would be immensely helpful in making sure that my users are finding the information they're looking for. This extension would also help contributors determine the desire for articles which don't exist yet.

For example, let's say that banana, for which I have an excellent article, was entered 139 times in the last 30 days. However, without this extension, I don't know that bananna is entered 15 times and banananas is entered 4 times on my site, but I have redirects in place for neither of these, so all of these searches end up with no useful results. I can correct this problem once this extension has brought it to my attention. I also learn that 430 people searched for kiwi, and I don't even have an article for that yet! --Jonathan Kovaciny 23:56, 4 October 2007 (UTC)
 * I wrote a quick and dirty hack that logs every search with search term, ip address, search method and time. Unfortunately there is currently no hook available when the search is started :( I will have a look at how my hack is working for some days and I'm going to post it afterwards. --Flominator 07:32, 11 October 2007 (UTC)
 * Any luck? --Jonathan Kovaciny 14:34, 24 October 2007 (UTC)
 * Try Extension:Log Searches for starters ... as I said ... dirty hack! --Flominator 09:21, 25 October 2007 (UTC)
 * Has there been any progress on this? Frankly I'm amazed MW has no built in search statistics page yet. --134.129.146.183 07:05, 16 October 2008 (UTC)
 * There is also a similar Extension:SearchLog. Don't know of any developments for a core MW special page --Zven 11:12, 16 October 2008 (UTC)

Watermark
I need hack (extension), who can automaticaly add watermark on every pictur that has been bigger as 300 x 300 pixel. Thank you. --88.222.212.231 15:00, 7 October 2007 (UTC)
 * I don't think anyone believing in open source software will support such suggestions. --Flominator 18:39, 7 October 2007 (UTC)
 * :/ --88.222.212.231 12:51, 11 October 2007 (UTC)


 * Flo, I fail to see the dichotomy between open content licensing of images and adding a small watermark credit line to such images to ensure they are actually attributed as their license requires. It is an uncontested fact that open content images are rampantly used without any attribution at all, to the great angst of creators, and that this has resulted in a strong disincentive for semi-pro and pro photographers and other image creators to release free images at all.  If the watermark were minimalistic, a credit line, this extension would substantially increase the overall amount of high quality free content material available, because it would give a better assurance to such creators that they will actually be attributed if they release free images.  You might say this extension is exactly what a lot are waiting for, even. Stephen Ewen 10:08, 8 November 2007 (UTC)


 * Not every wiki is used in an "open" format anyway. There are many applications where an open format is totally inappropriate (propitiatory in-house documentation, etc).70.103.216.66 21:06, 2 December 2007 (UTC)


 * This is a good idea. my wiki uses copyright and PD images. Imagemagick which Mediawiki uses can easily do this. I'd like to see a crop, rotate, gamma correct images in a wiki and a general purpose tag to get Imagemagick to control the display of images would cover all these bases. Be nice if it was built into MediaWiki as standard. I mean it uses Imagemagick already! :-) --Stuart Halliday 12:12, 19 October 2008 (UTC)

three tracking pages
There are often articles I don't want to keep on a watch list, but sometimes want to check up on. I envision these similar to Special:Contributions. First, Special:Created (for articles that the user created), Special:Contributionsunchanged (for articles where the user's edit serves as the most recent version), and Special:Articlestouched (like Special:Contributions with duplicates removed). Feel free to choose better names, though. ? ChristTrekker 15:10, 12 October 2007 (UTC)
 * These all sound quite useful. Good ideas. --Jonathan Kovaciny 15:13, 12 October 2007 (UTC)
 * What about putting such articles on a page and checking them via "related changes"? --213.182.155.146 13:15, 14 October 2007 (UTC)
 * That's manual updating of another "watch list", which is what I am hoping to avoid. These are the sort of things many people will often want to keep an eye on from time to time, but not so much that they want to be continually receiving notices like you do with watched pages.  It ought to be straightforward (almost trivial) to implement, yet extremely convenient. ? ChristTrekker 18:04, 24 October 2007 (UTC)

Filter content by IP/hostname
I would like a way to display different content based on whether the user is coming from within or outside of my LAN, based on their IP. Something like this:

This is page content that shows up for everyone. This is page content that shows up only for visitors outside the designated IP ranges. This is page content that shows up only for visitors inside the designated IP ranges. Here is some more page content that everyone sees.

This is not intended to be a security measure, since the user could edit the page and see all of the content, but just one to make it easier to tell the user things that apply only to them. For example, my internal audience might know exactly which building to go to for an event, but the external audience might need more detailed information, maps, full phone numbers instead of just an extension, and so on. Is this even possible? Would there be a way to still cache pages? --Jonathan Kovaciny 14:43, 24 October 2007 (UTC)

RSS / Atom Feeds on Related changes
Although you can subscribe to a feed on Recent changes and New pages, it would be very helpful to support feeds from Related changes pages. In particular, the Related changes from a Category page would allow a user to receive a feed for all changes made to articles within a specified category. Bill Johnson 19:01, 27 November 2007 (UTC)
 * I also think it might be useful (actually, I has been asked this functionnality, for a corporate use) Gizmhail 14:54, 20 February 2008 (UTC)

automated e-mail obfuscation
I'd love to see an extension that automatically obfuscates any e-mail address included in an article. Maybe replacing all (or some) of the letters with images and/or HTML code. Other methods exist too... 70.103.216.66 21:04, 2 December 2007 (UTC)

Brainstorm feature
It will be very cool to have such feature in MediaWiki as it was done in Britannica.



''A “brainstorm” feature maps relationships between ideas, subjects, and people as you go through the encyclopedia. It is fascinating to browse through subjects and watch a virtual brainstorm of related subjects coalesce around chosen articles, leading you to additional interesting paths to take.''

Screenshot (poor, though) is there:

For what you are looking for first we need the semantic version of MediaWiki which is Extension:Semantic_MediaWiki. For SMW there are also extension and you need the MOCA Extention. See an implementation example on

Machine Translation Feature
Add a mechanism that sends the substantive content of an article to an online translation service (like Google Translate or Babelfish).

Bonus points if the translated text could somehow be integrated back into the original page, with a clear indication to the user that an automated translation has been performed.

Block certain E-mail address domains
Dunno if this really needs an extension or if it could be set in SpecialUserlogin.php.

I've set that users need to confirm their e-mail address in order to edit pages. Now it would be nice to block some free spam domains like spam.la. Possibilities:
 * do not send such confirmation mails to blocked domains
 * do not allow to enter blocked domains in Create Account and User Preferences

Thought about entering such a domain to $wgSpamRegex but it only controls page edits. Subfader

Block account creation if E-Mail address already exists
Have problem with a spam bot using the same mail address to create fake accounts for an attack session. Subfader

Category navigation - Change order
I'd like to see an extension that gives you a little more features to the category listings, esp. when there are more than 200 subcategories or articles listed. E.g. switch order (ASC, DESC), or a drop-down menue to choose the number of listed items instead of 200 default for all and everyone. Subfader
 * Could maybe be done via Javascript. --Flominator 11:44, 27 January 2008 (UTC)
 * Yeah I dunno how but I do know it's not hard to set up. It should be possible to also set a standard order in the category. (E.g. a special categoy page which I want to order descending instead of ascending as per default. --Subfader 12:29, 14 February 2008 (UTC)

Flexible Watchlists
I'd love to see an extension that allows flexible lists just like the watchlist but without displaying the latest changes, e-mail notification on changes etc., primarily just to list the articles I have added to the list.

Example: Many wikis are about collectable things. Let's assume a wiki about those pokemon cards. Each article of the main namespace stands for one unique pokemon card. Now it would be great if users could keep track of which they already have and which they want. So I imagine new tabs where the "watch" is located reading sth like: [own] [want].

So combined with that, those lists should be located on top aswell where "my watchlist" is atm. In this example it would be "my collection" and "my wantlist". I could also imagine a list for "my favourite articles". Such a list itself should primarily list the articles which were added to it. Now even more awesome would be to search inside such personal list :)

Such a feature could also come with some added value for all users by giving out statistic lists like:

On each article page: "X users own this" or "X users want this" or "X users boomarked this" etc. or "Hitlists" like most owned or most wanted. Or for personal use: List all articles not in my collection or not in my wantlist...

The names for those lists should be easily changable at one place of the code (sth like $list1name= and $list2name=). Note that eachlist has 2 names; one for adding it to the list and one name to display the list. Flexible names would be important cos of the different use of the wikis which may use it. E.g. in my wiki articles are not called articles. Or in the pokemon wiki "artcile" could be called "card page" etc.

I hope I could demonstrate the variety of possibilities by such felxible watchlists. If anyone has an idea how to set this up, pls let me know!

It would be great if such an extension would work on my MW 1.8.2 ;) --Subfader 11:54, 10 February 2008 (UTC)

Search this category
Had the idea when testing Extension:Multi-Category Search. So a simple search box will pop up on every category page. It searches like the standard search, but it only considers articles in the according category. Combined with that a new search field could be added on the Multi-Category Search on top for normal text search... I post here cos I doubt the devs read their extension talk page. --Subfader 01:52, 1 March 2008 (UTC)

Limit edits per minute for new users
I am looking for a way of limiting the number of edits new users (say for the first week or two) can create per minute. I am also looking for some way of identifying accounts that don't make any edits at all during that period. Any help is gratefully appreciated! 217.65.158.124 10:13, 11 March 2008 (UTC)
 * For the first part, you can use $wgRateLimits with, for example,  to allow new users (i.e. non autoconfirmed) to make 2 edits in one minute. This require caching, see $wgMainCacheType.
 * For the second part, you can run the  script in the maintenance directory (it won't remove the account by default, it will just show it), but it lists all account that didn't make edits at all. i Alex  11:43, 11 March 2008 (UTC)

Encrypt / decrypt wiki content
Is it possible to create a MediaWiki extension which ables :

- to encrypt content with a public key on edit

- to decrypt content with a private key on display ? (I guess the user have to be prompted once to give the key)

Maybe such an extension already exists ?

Second question : Is it best to encrypt/decrypt client side with javascript for server performance reasons ?

Thanks for your help.

Vincent - 83.137.240.218 12:45, 11 March 2008 (UTC)

Register your collection / Bookmark Wiki pages
I partake in maintaining a wiki about comicbooks. Most (but not all) pages on the wiki detail individual comicbooks. I would love to let users register their comicbook collection on the wiki, by adding such pages to a list stored in their profile. Both for their own leisure, and if they want to: to show off to others.

So what I'd love is a "register your collection" extension that:
 * when installed adds a tab to the tabrow called "Add this to your collection". When the tab is clicked -- like when "Watch" is clicked it turns to "Unwatch" -- it turns into "Remove from collection".
 * adds an extra link to the top-right user area, called "my collection", which lists bookmarked pages.
 * adds a tag called, for instance, " ", which users can add to their user pages. When doing that, other users would be able to see their collection.
 * adds a tag called, for instance, " ", which must be added to all pages that describe collectible items.
 * because a single page could possibly detail two or more different editions of the same collectible, it would be nice to be able to distinguish betweeen editions by inserting two tags. For instance, , and .

I'm sure wikis such as Memory Alpha and Wookieepedia would love to let their users register their collection on their wikis, so I'm convinced there's an audience for this type of extension. Finally, I imagine the extension could also easily be used simply as a bookmarking extension. Your thoughts, and possibly your skills, are very welcome. Joen 19:42, 11 March 2008 (UTC)


 * I want something similar: Extension_requests --Subfader 17:33, 6 April 2008 (UTC)

Private Messages system
Could be based on Extension:MediaWiki Bulletin Board. But I hate this extension cos the devs don't seem to care much about it. The PM system should use the following features additionally to what MWBB already features: --Subfader 11:37, 16 March 2008 (UTC)
 * load edit toolbar like on a normal edit page, including preview
 * Inbox and Outbox (for sent messages)
 * On a reply: load old message(s) like forum quotes, leave space on top of the edit field for the new reply (to force "latest on top" order)
 * Option to delete selected messages in Inbox and Outbox

Slideshare
Slideshare Extension 124.176.23.250 12:51, 17 March 2008 (UTC)

Email Article to a Friend
How about having an extension that will allow users to email articles to a friend? This can be achieved by having a small icon appear at the top right corner of each article. Once that icon is clicked the user can input his/her friends' emails. A link to the article is then sent to the list of friends.
 * Take a look HERE or HERE --Aroekene 14:35, 27 October 2008 (UTC)

Proper Ajax Rating
Extension:AjaxRatingScript is full of bugs and most people are not able to install it. Devs are only communicating on their own wiki which is horror. So pls don't tell me to suggest it there.

I'd like a rating system that is fully integrated in the wiki:
 * Option for admin to decide if only logged in users can rate or everybody (while considering only registered users is more safe against abuse)
 * Each rating section on an article page should have some link "Details" (link to different page or better as collapsible NavFrame)
 * See who else voted how (with linked users name and his ratings)
 * Update your vote: see your own rating (simply bold in above "users who rated" list) and enable updating it by simply rating again
 * Special page for
 * "Best rated articles" listing the best 50 | 100 | 250 | 500 rated articles of the wiki
 * Unrated articles
 * Integration on user profile: A user should be able to add some code on his profile page so "My favourites" are displayed: (5 | 10 | 25 | 50) best rated atricles by User...
 * Option for admin to display the rating behind article links on categories. Combined with that: Option to sort articles in a category by rating
 * Some smart way to delete all votes by abusers (e.g. users who obviously rate everything worst or best to manipulate results)
 * Why not consider Extension:JSKitRating ? Jean-Lou Dupont 13:01, 4 April 2008 (UTC)
 * Cos I never saw exmaples using it and it cannot do what I requested above. --Subfader 09:56, 5 April 2008 (UTC)

User View Statistics
When establishing a new wiki it is useful to be able to gauge user uptake. Extension:Contribution Scores is great for giving a good overview of user edits but gives no appreciation of user view activity. Extension:UserPageViewTracker is too detailed in that it breaks down the stats on a per page basis making it difficult to compare all users. A simple view count for each registered user would be very useful. I would like to see this as an additional column in the report output by Extension:Contribution Scores. A helpful addition would be to also provide a count of page views for all unregistered users i.e. a single total NOT per IP address! A final possible enhancement would be to allow break down of the stats by namespace (so long as it didn't impact performance too much). --Phil 10:55, 4 April 2008 (UTC)

Simplified New Pages Embeding
First of, excuse me if something to do this already exists. Ive looked all over the site and google without luck. Im after an extension to embed a summery of the Special:Newpages on the main page of my wiki.

I know it is possible to limit the number of records displayed by using however it still provides alot of information that is unnecessary on the main page.

At present information is displayed in the normal format;

''05:30, 3 April 2008 ? Sandbox(hist) ?[746 bytes] ?Dargrotek (Talk | contribs) (create''')

However on a main page that can be very cluttering and want to change the format to something similar to the following.

''3 April 2008 -? "Sandbox" Created by ?Dargrotek''

Also the ability to limit what type of pages are displayed as well would be extremely usefull so that new images wont show up and so on. Can anyone help or point me in the direction of an existing extension? --Dargrotek 19:19, 4 April 2008 (UTC) return "{$time} {$dm}{$plink} ({$hist}) {$dm}[{$length}] {$dm}{$ulink} {$comment}"; and change to sth like return "{$time} {$plink} created by {$ulink};"; --Subfader 20:56, 9 April 2008 (UTC)
 * First off, images etc don't show up using . Hack /includes/SpecialNewpages.php to remove useless info. Not recommended but easy: In your case find

Word substitution
I need an extension to do the same as Extension:AutoLink but that would be able to point to external pages. The best thing I think would be an extension that:
 * 1) when an article is saved
 * 2) it parses the 'to-be-saved' text searching for strings existing in a dictionary
 * 3) if such a string is found in the 'to-be-saved' text it gets substituted with the 'translation' of it from the dictionary

I'll try to make myself clear with an example:

wikipedia//[en.wikipedia.org wikipedia] yahoo//[www.yahoo.com yahoo] hello//greetings whatever you want to translate//whatever you want to have instead Thank you,
 * I save an article containing the following text: bla hello bla bla wikipedia bla bla bla
 * I then have a dictionary say called mediawiki:substitution containing the following:
 * the resulting page should be: bla greetings bla bla [en.wikipedia.org wikipedia] bla bla bla

--DonGiulio 20:35, 16 April 2008 (UTC)


 * Check what Extension:AutoLink can do for you. --Subfader 09:36, 9 May 2008 (UTC)

AJAX Capability Testing
We have $wgUseAjax to determine if AJAX is used on this wiki. But it would be nice to have a function that other extensions can call to check whether AJAX is likely to work.

If $wgUseAjax is off, this function would always give false. If it is on, the extension would add an option to the user preferences: "Use AJAX: yes/no/autodetect" (with autodetect being the default, I'd guess). If this was set to auto, the extension would first check the browser identification against a known list (maybe), and then if unsure it would send the user a simple chunk of javascript which calls an Ajax function to say "yes it works", and this data could be stored in session and/or cookie.

It could also be useful to have such an extension which knows (or can test) the different capabilities of different browsers, such that other extensions could check the availability of certain javascript functions. (For example, I believe I read that if sent an XML document as an ajax response, some browsers will parse it into a document object, but some don't have this functionality. In this case, it would be useful for an extension author to have a function they can call to determine which javascript to send the client) Of course in the case of $wgUseAjax being off or the user disabling javascript in their preferences, these functions could return false even if the client is actually capable.

MrAngel 16:30, 20 April 2008 (UTC)

Search results direct link
The Search button returns a list of all articles that include the term in the search box, and the list items include wikilinks to the pages. In order to find the search phrase, however, the user must follow the link to the page and then search again, either manually or with the browser's Find function. It would be helpful if the user could link directly to the first occurrence of the term in each page listing. --Furboy 18:18, 18 April 2008 (UTC)
 * Have you seen Help:Search (GO function) and Extension:GoToCategory? --Subfader 16:23, 20 April 2008 (UTC)
 * Neither of these seem to do what he was asking for. However, it sounds like it should be a fairly simple extension to write. I'll see what I can do if I have time tonight MrAngel 16:33, 20 April 2008 (UTC)
 * The extension would require you to take the target page and drop an anchor on that search term - I'll be interested to see the implementation. ;-)  Tim Laqua talk 02:11, 21 April 2008 (UTC)
 * Highlighting the search terms and wrapping anchors around the first instance isn't a big deal ... a crude implementation could do it using an OutputPageBeforeHTML handler, just run a preg_replace over the page text to insert anchors and highlighting. (I'm sure there's more refined ways to do it if you look)
 * The place I'm falling down is making the search results page generate links which contain the search terms. So far, the only solution I can find involves inserting a new hook in SpecialSearch::showHit (after line 364 in SpecialSearch.php, I added one line)

wfRunHooks('RenderSearchResult', &$link, &$t, &$extract, $size)
 * I'd rather not play with the core code, but I don't see any existing hooks which could enable this
 * -- MrAngel 18:45, 23 April 2008 (UTC)

Page creation in extention code
Hi, I'm writing an extension and I need to create a category and add some wikitext in it directly in the php code of my extention. I tried Article::doEdit, and the code below : But I always get an error... (MyExtention::getContent undefined for Article::doEdit and T_PAAMAYIM_NEKUDOTAYIM for the second case). I don't know if it's a good place to post this problem but I didn't know where to post it.

Regards, --Teriblus 08:40, 24 April 2008 (UTC)


 * I think you mean $newcategory->doEdit ? --MrAngel 09:09, 24 April 2008 (UTC)


 * Thanks, It's ok now ! --Teriblus 09:33, 24 April 2008 (UTC)

MapLib extension
is posible to create a extension to add a iframe from MapLib like 999999999 to do a:

<iframe src=" http://www.maplib.net/fullmap.php?id= 999999999" scrolling="no" frameborder="0" style="width:400px;height:400px;border:0px">

thanks.


 * Seems like a fairly simple extension, should only take a few minutes. I'll get back to you later today. --MrAngel 01:15, 20 June 2008 (UTC)

Per user Statistics
Is possible to add a tab in user page with statistics like edit count, creation count, age, and so on, and also something like a personal page in which a user can descrive his preferences or other features

Homepage/Portal
I'd like to see an extension that gives a wiki the ability to allow its users to personalize the main page. The content included within the main page modules could be either controlled by the site admin/bureaucrat, or if they allow, could include custom user made modules...

The idea is to make the main page look as professional as possible, allowing user personalization to entice them to use it more regularly as their 'home page', thus further contribute to the wiki and engage with the community.

A perfect example of what I am talking about is the BBC site, with its movable and configurable modules.

Desired features:
 * Designed for the main page
 * Ajax modules movable, collapsible and able to be added/removed as chosen by user
 * User settings remember user preferences
 * Admin/bureaucrat acceptance required for user made custom modules (if allowed at all)
 * Admin/bureaucrat control over allowing users to create and add their own custom modules
 * Admin/bureaucrat control over what modules have to be displayed no matter what
 * Content much still be readable/search-able by search engines

Examples of what is available, but meet different needs, but if combined, could make a user personalized homepage/portal
 * My Portal - Portal extension, poorly supported and based on user special page as opposed to main page.
 * Andy's Skin - A skin using ajax that allows for users to move boxes, minimize/maximize them, and add favorites.
 * Wikia Userboxes Extension - A extension that gives a user the ability to make custom modules for their user page

This I believe would take wikis the next step in personalization and presentation/skinning.

--HTPCnz 03:33, 22 May 2008 (UTC)

Save all the Content
I search a solution to save all the content from my wiki with the ending ".pdf". (Like Extensios.pdf) I imagine like i click on the "Save all!"-Button and all the Content is saved with the correct title in a folder on my server. (sorry but my bad english)

--83.76.88.30 06:41, 22 May 2008 (UTC)
 * Backing up the complete site on your server is not enough? --Subfader 12:37, 22 May 2008 (UTC)


 * My problem is the content should be portable for everyone in our team when he/she doesn't have internet--83.76.88.30 12:42, 22 May 2008 (UTC)

'grab my edits'
I'd like to see an extension to allow a user to retroactively claim responsibility for their edits in case they forgot to login.

Essentially, you'd have a "claim my edits" tickbox on the login page, which associates your username with any anonymous edits coming from your IP address since you last logged in. (I'm currently doing this on my wiki by manually hacking the database)
 * This is sort of possible with Extension:ChangeAuthor, although it requires a sysop to go and change the author manually. --Catrope 23:40, 29 October 2008 (UTC)

AJAX autocomplete
I'd like to see an extension that autocompletes page names. This is on my to-do list, but I'll post here in case it already exists, or someone has ideas to do it in a better way.

When you type ' {{ ', it would produce a little pop-up box (preferably below the cursor) listing all the templates, most commonly used first. As you start typing a template name, it acts as a filter on the list. Each list entry would be clickable to complete it, and would also have "view template" (in popup window) and "edit template" links next to it. Once the user has typed ' {{templatename| ' or clicked one in the list, a popup appears listing common parameters for that template (possibly just searching the template for all {{{.*}}} blocks, possibly something a little more complex).

Similarly, typing ' [[ ' would produce a popup list of pages. If the list of all pages is too long, it would only show pages which link to this one, until the user has typed enough letters to allow a sensible-sized list (or until they click a 'find all options' button).


 * --MrAngel 15:38, 4 June 2008 (UTC)

An extension is available on wikia, it's called LinkSuggest. I've contacted the author Inez Korczynski who told me it's going to be released soon. Cheers

Addthis Social Boomarking
Extension:Social Bookmarking uses Addthis but the solutions is very unhandy. --Subfader 07:47, 6 June 2008 (UTC)
 * I'd like to see the Addthis button below the toolbox and for every page or defined namespaces.
 * Enable via gadget for those who want to use it. Cos I think what keeps most admins from installing a social bookmarking feature is that it's annoying for those who don't use this. The extra loads for Addthis interrupts loading the wiki page (just like google ads do sometimes). Yes there other extensions with static buttons but Addthis is more complete (I don't need to worry about adding new sites) and is pretty handy.
 * Additionally, when you have an account there it gives you click statistics(!). So adding / using the original script (with the addthis account name) in the extension is essential for me.


 * Don't know if this will suit you, but maybe a possibility...
 * Widget:Addthis
 * You would need Extension:SecureWidgets for it to work.
 * --HTPCnz 06:59, 7 June 2008 (UTC)


 * Thanks, but I want it appear on every page when user enables the gadget. --Subfader 08:34, 7 June 2008 (UTC)
 * Use Extension:HeaderFooter perhaps? Jean-Lou Dupont 18:17, 12 June 2008 (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.

Gadget: User Sidebar
A Gadget that (if enabled) will override the MediaWiki:Sidebar config with the user's very own config.

The user's config list could be stored in a users subpage, e.g. in User: /Sidebar. A problem might be what the sidebar displays after enabling the gadget and the user's config page doesn't exist yet. A workaround could be: If enabled, use MediaWiki:Sidebar when User: /Sidebar doesn't exist / is empty (User could clear). It could also created automatically (with default content) when a new user registers (using Extension:NewUserMessage) and to let a bot add it to the existing accounts. See also Extension:SidebarEx, Extension:SysopSidebar    --Subfader 12:34, 22 June 2008 (UTC)

Email Client
A extension that makes a special page for a E-mail client.

Images in categories
The problem: When you categorize images into the same categories as articles they're listed on the category page as "Media files" below the articles. There's nothing wrong about it. The problem is the counting and the navigation of both. The standard limit of 200 = articles + files. E.g. you have 183 articles and 30 images in the same category: On the bottom you'll have 17 images (200-183) reading "next 200" or you have 250 artciles and some images. The images won't appear until you click "next 200". How am I supposed to know there are images in the category when opening it?

Possible solutions: Split the counting and navigation --Subfader 19:06, 23 June 2008 (UTC)
 * List all images below the articles. When browsing next 200 articles, only list the rest of the articles.
 * List all images independetly from the article navigation but in a kinda iframe with vertical scrollbar. The frame could be 5 image boxes wide and 2 image boxes high and placed above the article links section.
 * Split up article and image count and navigation. E.g. 500 articles and 500 images: When browsing forward to articles 401-500 still show images 1-200. When browsing now images 201-400 still keep articles 401-500. For a better navigation it may good to only list like 40 images but 200 article links.
 * This sounds more like a MediaWiki feature request/bug report than an extension request. Please file this at BugZilla. --Catrope 23:44, 29 October 2008 (UTC)
 * Done. --Subfader 20:07, 5 November 2008 (UTC)

User friendly way to flag/request pages
The problem: I am trying to develop a super user-friendly way for users to flag a page for review, and separately, request a page that doesn't exist (not create it per se, but request the page to be created by someone else). I realize this is as easy as adding some kind of "review" or "request" template to a page but what if I assume most of my users are not wiki-proficient. Is there a very simple way (ie clicking one button) for users to flag a page for review/request a page that does not exist yet.

Possible solutions: Ideally any solution would require no editing on behalf of a user - just one click. Thanks!

Move pages via find / replace
A special page lists a find and a replace input box. The extension finds the page titles with the given word and moves the pages to the new title which replaced the word with the new one. The result should be a valid move (with redirect). Extension:Replace Text does that for page content but not for titles. --Subfader 11:56, 28 June 2008 (UTC)

Support docbook
Like some feature in docbookwiki.

Related news extension request
Information of what extension will do: http://code.google.com/p/mediawiki/issues/detail?id=20 Hope someone develop it. Thanks

Template Extension
is there an extension that can get me all the important templates like Infoboxes and tables, stuff like that.. I've tried importing those pages from wikipedia and other Wiki's but on the page it just has.. well alot of stuff that should not be there so is there an extension for that or how do i do this? --70.100.80.125 18:28, 3 July 2008 (UTC)

Search Extension
As in our wiki we link not only images, but also some files .doc or .ppt or .pdf, is there an extension that makes it possible to search also into these files? Cattest 09:03, 7 July 2008 (UTC)

WhiteBoard Extension
A simple freehand drawing tool, like a whiteboard, where authors can draw pictures. Minimum tool bar: freehand pencil, shapes, and Text tools. Newly created image file can be saved on the server and indexed. Old images can be added to or edited. Real-time multi-client draw control, to show many clients the image as it is being drawn, and who has the pen. Eventually multiple clients could draw at the same time.

Edit Preview Redirect List
I was editing my wiki when I got an idea. What about having an extension that lists the any redirect pages that are linked to on the current page when previewing an edit? I couldn't seem to find an existing extension like this. Sound good?--Mjr162006 22:56, 13 July 2008 (UTC)


 * So no one wants to comment on this idea? The people at my wiki think it's an awesome idea. What's so wrong with it that people don't think it's worth their time?--Matt 16:50, 20 October 2008 (UTC)


 * WHat's the benefit of seeing the redirected from article names when editing an article? --Subfader 18:41, 5 November 2008 (UTC)

Indent first line
In formal writing, the first line of every paragraph is indented. However, the only options are either to use 8 HTML spaces or to use another line for separating paragraphs. However, the first one is messy and the second is harder to read. So my idea is for a special symbol (like [ind] or [indt]) to be automatically replaced by 8 HTML spaces or equivalent indent. Or simply make the ":" character indent ONLY the first line. (By the way, I'm requesting this as a result of "problems" at Novelas.)
 * You can use CSS to solve this. Just modify your default style sheet or add a template like this <p style="text-indent: 2em">... --Benjamin Garn 19:03, 10 October 2008 (UTC)

Move section to Sub-Page
Does anyone have any suggestions to make the task of migrating large pages to sub pages? I've seen talk of a bot which could break up a page based on H2 level tags, but can't find the source of it anywhere.

I would imagine an extra button on the edit section page "Make this section a sub-page". Then the full section contents would be pushed as a sub-page of the current page (with title=heading of the current section), and the full text of the current section would be replaced by a transclusion of the new page.

Easier select and copy method
I have noticed whenever some people have to copy a long code written on a wiki page, they have to wait a very long time for the whole code to be selected. So I am proposing a new button with an opacity of 50% on the top right corner of any code on a wiki page. Its function would be to select the code and copy it in a click. You can't use control + A for this since this method highlights everything on the page. This extension should be called Extension:Autocopy. Worth looking into. --'<font face="freestyle script"> Truetech  <font face="Imapct">  (Talk)     MediaWiki Support Team '' 23:30, 4 September 2008 (UTC)
 * Hard to find a solution working on all browsers...--Subfader 19:59, 5 November 2008 (UTC)

Record Search Queries
I'm sure this isn't too hard to implement, but I'm drawing a blank on this one. I think a feature rich version of this would be very helpful to any mediawiki owner.

The reason I would like something like this:


 * Build more pages based off of what people are looking for
 * Create a list of commonly searched for phrases to help noobs
 * creates a page full of key words (and misspellings) that get indexed by search engines
 * Helps you learn more about your users

anyone willing to help out, please feel free to hit me up on my talk page.

-Theothertom 18:03, 9 September 2008 (UTC)

Groupselection + Accountcreation
I'm not so good in php and so on. Maybe someone can help me. I need an extension which allowes me to select groups I want to be in while I'm creating an account

example: A company with 3 groups (group1, group2 and group3) A new user wants to create an account in the company he's in group1 so he wants to select group1 in the account creation.

Sorry for my bad english :D


 * What's the point if he belongs to group 1 but can chose group 3 anyway. What differs for the groups? --Subfader 19:56, 5 November 2008 (UTC)

Allow user to delete only files he uploaded himself
I'd like to see a wg that allows the group User to delete files the user uploaded himself (not other User's files). --Subfader 22:04, 23 September 2008 (UTC)
 * So if the user uploaded the file the [delete] button will appear on top so he can delete the complete thing like a sysop. Maybe disable deleting (with a message) if the file is still used on other pages. -Subfader 14:01, 3 October 2008 (UTC)
 * Take a look at This Extension.--Aroekene 14:39, 27 October
 * Hmh thanks, if i use $wgGroupPermissions['user']['delete'] = true; and exclude all namespaces except Image, every user can delete every image page. --Subfader 17:05, 27 October 2008 (UTC)

Blanking historical page versions
I would appreciate an extension that allows the blanking of page versions, or more generally replace them with a chosen text like '(vandal)', while completely removing the orginal content from the database. This both for individual edits and for all edits by one user, and preferably also with the option to permanently remove a version if it is the last version of a page. We've had a lot of mass vandalism lately that inflated our database. Regards, Guido den Broeder 16:39, 27 September 2008 (UTC)


 * MW 1.12+ have the script maintenance/deleteOldRevisions.php for older versions check Extension:SpecialDeleteOldRevisions. --Subfader 15:32, 28 September 2008 (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.

What Links Here extension
A simple extension adding a box at the bottom of article with a list of max. (parameter=10) articles linking here.

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)

Making new pages even easier with a Wizard
I'd like to see a Extension where the Editor is given a column of text fields and drop down menus for the person to select the page title, headings, etc. where they just fill in text and submit the form. The wiki then takes this input and generates a new page.

Templates are all very well, but they require a user to go to the right one and then cut and paste from it into the new page. Why give them less work by offering a simple drop down menu to select a template and then the Extension takes the == headers == from the template and shows them a column of text fields they can fill in. From my (very) limited experience in PHP this should be possible?

On my Wiki, the potential Editors often find the aspect of opening a new page and then having to open the templates page separately and cutting and pasting a bit 'frightening'. Let's make the Editors job even easier? --Stuart Halliday 10:51, 20 October 2008 (UTC)


 * Take a look HERE. --Aroekene 12:57, 27 October 2008 (UTC)


 * Extension:CreateArticle adds inputboxes (for the title) with connected load-default settings to chose a Template to be loaded by default when creating the new article. Requires you to set up a page with all inputboxes each defining a template to be loaded. --Subfader 19:48, 5 November 2008 (UTC)

List Redirects Expansion
I had an idea just now. How about the Special:ListRedirects page is changed a little to add links next to them just like the page Special:MostLinked has. That will make fixing redirecting links a lot easier and would save a lot of time. That is what I use the list redirects page for anyway.--Matt 19:49, 21 October 2008 (UTC)
 * Why fix Redirects? MW 1.13 has "Redirect fixer" bot-user anyway. Don't ask me how it works. No info. --Subfader 19:52, 5 November 2008 (UTC)


 * Not all wikis use bots. And bots don't fix redirects as well as human users. Each case is unique. And the piped links need to be different depending on the context. A bot just can't handle that properly.Matt 20:03, 5 November 2008 (UTC)


 * As said, don't ask me about that bot. Check your userlist ;) I guess it's the "Update any redirects that point to the original title" option when you move a page, which is logical: Create an article A, move it to B, move B to C. With the option ticked A will be fixed to redirect to C instead of B. The double-redirects are avoided. So again, why do you want to fix redirects? Nobody sees them, except for old links from external sites. But double-redirects are fixed (imo) in 1.13 --Subfader 20:12, 5 November 2008 (UTC)


 * Not the redirects themselves. But the pages linking to redirects. Those are all over the place in just about any wiki.--Matt 20:19, 5 November 2008 (UTC)


 * Why bother, they're invisible and treated as such. --Subfader 20:22, 5 November 2008 (UTC)


 * Professionalism for one thing. They are not invisible. Once followed, it shows under the title that you were redirected. It isn't like it would be that hard to implement anyway. All the needed coding already exists.--Matt 21:05, 5 November 2008 (UTC)

Exclude Redirects from Search Suggest
Is there a way redirect pages could be excluded from Search Suggest? --Resplendent 04:39, 22 October 2008 (UTC)

Extension:Backup wiki
This extension would allow anyone to download a backup the wiki, presuming it is enabled. This extension could allow for different things to be included in the backup. It could allow for everything to be downloaded/backup'ed, or just certain parts of the wiki. It would be like database dumps (and could perhaps use this), but hopefully, it would be a bit more shiny.

Extension:Restore wiki
This extension could be installed and in conjunction with the extension "backup wiki" it would allow for users with the highest level access to easily restore a wiki. For example, if I had used "Backup wiki" extension to do a complete backup of whatever wiki (let's say it had its last dump four days ago), then using this extensions I could in theory easily create a complete new fork of the other wiki quite easily.

Export entire article
I would like an extension that can export entire article with pictures to another Wiki. For instanse, you have one private and one public wiki, and want to maintain articles in only one place. If you have an article on your private Wiki and want to publish it on the Public wiki, you can do this via a tab (similar to Edit, watch, etc.). --Aroekene 21:33, 26 October 2008 (UTC)

Multidimensional TOC
This extension should allow authors to write an article that can be sorted, structured depending on the readers question. eg. an article about the car 2CV from citroen can be read as a time line or by technical developments. eg 2. an article about processors, can be sorted by producer (amd, intel) or by architecture (8 bit, 16 bit, 32 bit) or any other theme. The auther must think about the questions, that the reader has. Depending on that, the auther must write the text (with tags) so that wikimedia offers to the reader several TOC with the respective text sorted. --Tomton 09:12, 28 October 2008 (UTC)

Use backquotes (backticks) for preformatted code
When documenting code it would be nice to be able to use backquotes to mark text or a section that should be rendered as So on the category page of Seinfeld the hide link would pop up: "Hide Repeats" (Repeats was defined as reason in LocalSettings). Clicking it would hide all articles reading  and make the link "Show Reapeats".

A mutli-reason solution could be to use  while this would leave the problem of multiple hide-links on a category page.

A global __HIDEARTICLE__ for all categories of the article wouldn't work for my wiki. --Subfader 19:25, 5 November 2008 (UTC)

Sub-wiki, prefixes
ive been searching all over the extensions, and cannot find what im looking for. I am looking for an extension that would, say, if the page name was OSE:Collaborators, OSE: would refer to a page format and CSS file, and the prefix would not appear as the title on the page, so it would only be Collaborators. We basically want to create small wikis within our wiki, for professional appearance purposes without hampering cross-referencing and collaboration. any suggestions? 11:13 CST 15 Nov