Extension requests/Archive 2

RecentChanges - Show Linked Title Only

It would be nice if there were an extension with a template for showing only the linked (the link would take the user to the page in question) title of a recently changed or new page. The template would contain a parameter for the namespace of the recentChange and a parameter for the number of links to show. It seems like this would be easy to implement this with a hacked version of Special:RecentChanges, but it's been so long since I've coded anything, and I'm not familiar with the global variables of mediawiki. So this could take some time if I were to do it myself.

Ability to Launch a Full Page Edit Popup Window

For those that redesign their wiki's and try to match their website layouts, who have website resolutions that is not fluid, is there a way to have a button that when click opens up the edit window in a popup? And you can edit the page there instead of on the original text area?

Maybe it is not what you want, but I recommend to use an external editor. In case you use Firefox, try the extension It's All Text. Your favourite editor opens after a single click (the button appears to the bottom right of the box by default, but you can change it)). In addition, there are other possibilities to use external editors, some are listed in en:Wikipedia:Text editor support and Manual:External editors. --Jaan513 18:30, 23 October 2009 (UTC)Reply[reply]

Ability to hide navigation AKA sidebar on page by page basis

Want to make fancy front page, the Navigation page make it look fugly, would like an extension to hide the navigation pane using a keyword in the page source (like __NO_NAV__ )

THis could be done using CSS, but you would want to remove the logo as well. --Subfader 14:12, 20 May 2009 (UTC)Reply[reply]

The uncyclopedia.info main page does this with extension:CSS, turning off just about everything except the page text. Title and sidebar are both disabled by on-page <css> --Carlb 16:32, 25 September 2009 (UTC)Reply[reply]

User experience improvements

Hi, I don't really know if I can post here because it is half an help request. We are a group of designers working on a Mediawiki based plateform for user experience design. We would like that developments maid on the design wiki help to enhance user experience on mediawiki, so that we release the project open source. All informations about the features on the build are on the MediawikiUX forge wiki. Thoose features are on the build so that it is a bit more than a brainstorming, we would need some help from some more developer however.

Have a nice day.

--Ttibot 05:50, 3 May 2009 (UTC)Reply[reply]

You chat with the MediaWiki devs directly on the MW IRC channel. Btw: Your link requires a login. --Subfader 07:17, 3 May 2009 (UTC)Reply[reply]

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)Reply[reply]

Media Category

is there extensions for creating a gallery off a category who includes media?

<cgallery>Images</cgallery> or <cgallery limit"5">images</cgallery>

--Zizanzu 14:28, 4 August 2008 (UTC)?Reply[reply]

Programming Documentation and Extensions to copy from

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)Reply[reply]

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). -- 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.

Update: there's now an extension for x3d format, that many modelers can save.

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.


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)Reply[reply]

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. 19:34, 19 July 2007 (UTC)Reply[reply]


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)Reply[reply]

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


— Preceding unsigned comment added by (talkcontribs) August 13, 2007

Check Category:Media handling extensions. -Eep² 22:07, 13 August 2007 (UTC)Reply[reply]
Tryed but No one of them works - -- 11:19, 14 August 2007 (UTC)Reply[reply]
You tried Extension:Mp3 and Extension:Player? —Eep² 12:20, 14 August 2007 (UTC)Reply[reply]

Yes , And Many Others - -- 13:11, 14 August 2007 (UTC)Reply[reply]

What happened? --Flominator 13:30, 15 August 2007 (UTC)Reply[reply]

Some of them dident show , And the one named player Did show but dident play it -- 14:19, 16 August 2007 (UTC)Reply[reply]

Are you sure that your browser supports it? --Flominator 10:34, 20 August 2007 (UTC)Reply[reply]

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. -- 17:49, 28 March 2007 (UTC)Reply[reply]

See Extension:AutoLink. 12:25, 3 August 2007 (UTC)Reply[reply]
There is a realy little bug in that Extension:AutoLink - but I don't know PHP to repair it. 07:03, 6 August 2007 (UTC)Reply[reply]
Try Extension talk:AutoLink. --Flominator 12:10, 15 August 2007 (UTC)Reply[reply]
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? 06:59, 21 August 2007 (UTC)Reply[reply]
Do you mean a single set of brackets? If so, I added it (but haven't tested it) to extension:AutoLink#version which matches all pages. —Eep² 07:40, 21 August 2007 (UTC)Reply[reply]


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
[http://www.mediawiki.org/w/index.php?title=Project:Extension_requests&action=edit&section=new 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)Reply[reply]

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 02:24, 30 August 2007 (UTC)Reply[reply]

it seems to be shockwave flash, so Extension:Flash ought to work. --Flominator 09:38, 10 September 2007 (UTC)Reply[reply]

Advanced Linking


<Addtextgotourl> - Start tag to activate the code
</Addtextgotourl> - End tag for the end of the code
</getpath> - 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
</getdomainname> - the tag will be replaced with typed text in the domainname text filed
 Action= (&action=edit&section=new) To Edit the page | (noaction) For no Action 
 Pagebeforenter= Yes or no
 Image= YPagename or no  text
 Category= name
 Namespace= Namespace name
&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  [http://www.example.com 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!...

Action= (&action=edit&section=new) To Edit the page | (noaction) For no Action 
Pagebeforenter= Yes or no
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)Reply[reply]

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 :

--Dieudo 14:10, 3 September 2007 (UTC)Reply[reply]

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. —alxndr (t) 21:30, 19 September 2007 (UTC)Reply[reply]
Hack is now an extension: LightboxThumbs. —alxndr (t) 05:04, 23 September 2007 (UTC)Reply[reply]

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)Reply[reply]

Category And Namespace...

  • Category
    • Category logo (upload image called Categorylogo:categoryname.png , The logo will be shown 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 {{ALLPAGESICATEGORY=CATEGORYNAME}} 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 shown 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 {{ALLPAGESINNAMESPACE=id}} 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)Reply[reply]

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)Reply[reply]

Commons:User:Rotatebot meanwhile does this. --Flominator 14:46, 25 January 2008 (UTC)Reply[reply]
  • 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)Reply[reply]
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)Reply[reply]

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
<imgcrop:Example.jpg|X Y H W> or <imgrotate:Example.jpg|90 180 270> <imggamma:Example.jpg|2.2>
How about it MediaWiki? --Stuart Halliday 12:05, 19 October 2008 (UTC)Reply[reply]
There is such an extension (although this comes very late), you can find it here. 06:49, 6 October 2009 (UTC)Reply[reply]

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:

<notify caption="Attendees">

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)Reply[reply]

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)Reply[reply]

If your users are on IRC, there is now a new CIA Notify extension that sends change notifications as they happen to a given IRC channel. We use this extensively on our project for source code change notifications with outstanding success. The exact same setup would work for non software projects too. Once set up with CIA (the name of the reporting system), changes are basically pushed to a common forum (an IRC channel) where interested users join to take notice. Brlcad 07:26, 6 February 2009 (UTC)Reply[reply]

Review Date

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


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)Reply[reply]

You could just create a {{review|25.12.2010}} 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 <includeonly>[[Category:Articles needing review]]</includeonly> 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 <nowiki>{{review|}} 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)Reply[reply]

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

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

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)Reply[reply]
I actually created an extension that does this. The problem is that there is no way to derive this data from the standard mediawiki database. Each page has a single count entry, and provides no information about the timing of the views. What I had to do was create a new table in the mediawiki database, and I run a cron job each night at midnight to go off and store the current count value for every page. As you can imagine, this table gets big pretty fast. Then, I have a specialpages extension that allows the user to select a date and the output will be tyhe number of views for each page since the specified date. I can share if you want. DanRinkes 19:28, 24 September 2009 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]
Any luck? --Jonathan Kovaciny 14:34, 24 October 2007 (UTC)Reply[reply]
Try Extension:Log Searches for starters ... as I said ... dirty hack! --Flominator 09:21, 25 October 2007 (UTC)Reply[reply]
Has there been any progress on this? Frankly I'm amazed MW has no built in search statistics page yet. -- 07:05, 16 October 2008 (UTC)Reply[reply]
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)Reply[reply]
You might want to take a look at Extension:Woogle4MediaWiki. Related metadata of previous searches is displayed on the search page (see screenshot on extension page) and also shown as a popup to "red links". A dedicated statics page will also be included in the 1.0 release. --User:hhappel 09:46, 29 August 2009


I need hack (extension), who can automaticaly add watermark on every pictur that has been bigger as 300 x 300 pixel. Thank you. -- 15:00, 7 October 2007 (UTC)Reply[reply]

I don't think anyone believing in open source software will support such suggestions. --Flominator 18:39, 7 October 2007 (UTC)Reply[reply]
:/ -- 12:51, 11 October 2007 (UTC)Reply[reply]
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)Reply[reply]
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). 21:06, 2 December 2007 (UTC)Reply[reply]
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)Reply[reply]
I strongly support this! Please someone do it! :) --Yakushi.kabuto 09:01, 30 November 2008 (UTC)Reply[reply]
Yes, lease do this, I am looking for this same feature... I will have to look into image magic on my windows server.
Someone do this please!!!
This is not the philosophy of MediaWiki. Good luck. --Subfader 14:23, 15 June 2009 (UTC)Reply[reply]

I am working on one.. I have the basic code ready to overlay a png in the middle and the corner as well as backup the original to a new directory.. but how the heck do I do all this hook stuff... I'm confused.. Anyone here know what to do next? The code is quite simple actually, but implementing it is another story.. I just used php and GD, didn't have to install Image Magick --User:Bodykitwiki

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)Reply[reply]

These all sound quite useful. Good ideas. --Jonathan Kovaciny 15:13, 12 October 2007 (UTC)Reply[reply]
What about putting such articles on a page and checking them via "related changes"? -- 13:15, 14 October 2007 (UTC)Reply[reply]
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)Reply[reply]

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. <externalonly>This is page content that 
 shows up only for visitors outside the designated IP ranges.</externalonly><internalonly>This is page 
 content that shows up only for visitors inside the designated IP ranges.</internalonly> 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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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... 21:04, 2 December 2007 (UTC)Reply[reply]

Take a look at:Extension:EmailAddressImage and Extension:EmailObfuscator--Payo 09:01, 6 December 2008 (UTC)Reply[reply]

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: [3]

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 [4]

You can implement something like this with the [[[Extension:FreeMind|Freemind Mind Map Extension]]]. Although updates to the map need to be done outside of the Wiki - but its a start ! --JonandEl 14:13, 29 September 2009 (UTC)Reply[reply]

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

Some of the spambot blacklists (like StopForumSpam) do list e-mail addresses, IP's and usernames of known spambots. Check Spambots should in theory use this info; I haven't noticed if it makes a huge difference as any wiki which allows anon-IP's to edit will find that most of the spam is not coming from logged-in, registered users. Sites which require registration (including most web forums) may benefit, though. --Carlb 08:09, 27 September 2009 (UTC)Reply[reply]

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

That might be worth reporting on Bugzilla, as registration and e-mail verification are done by core MediaWiki code? --Carlb 08:10, 27 September 2009 (UTC)Reply[reply]

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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

Add links to a tracking page, then see Special:RecentChangesLinked/that page. ? ChristTrekker 05:10, 14 April 2009 (UTC)Reply[reply]

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)Reply[reply]

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! 10:13, 11 March 2008 (UTC)Reply[reply]

For the first part, you can use $wgRateLimits with, for example, $wgRateLimits['edit']['newbie'] = array( 2, 60 ); 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 removeUnusedAccounts.php 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. iAlex 11:43, 11 March 2008 (UTC)Reply[reply]

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 - 12:45, 11 March 2008 (UTC)Reply[reply]

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, "<mycollection />", 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, "<collectible />", 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 <collectible /> tags. For instance, <collectible title="Abraham Merrit, The Moon Pool, first edition" />, and <collectible title="Abraham Merrit, The Moon Pool, second edition" />.

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)Reply[reply]

I want something similar: Extension_requests#Flexible_Watchlists --Subfader 17:33, 6 April 2008 (UTC)Reply[reply]

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:

  • 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

--Subfader 11:37, 16 March 2008 (UTC)Reply[reply]


Slideshare Extension 12:51, 17 March 2008 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]
Cos I never saw exmaples using it and it cannot do what I requested above. --Subfader 09:56, 5 April 2008 (UTC)Reply[reply]

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)Reply[reply]

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:

  • 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:
wikipedia//[en.wikipedia.org wikipedia]
yahoo//[www.yahoo.com yahoo]
whatever you want to translate//whatever you want to have instead
  • the resulting page should be:
    bla greetings bla bla [en.wikipedia.org wikipedia] bla bla bla

Thank you,

--DonGiulio 20:35, 16 April 2008 (UTC)Reply[reply]

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

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)Reply[reply]

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)Reply[reply]

Have you seen Help:Search (GO function) and Extension:GoToCategory? --Subfader 16:23, 20 April 2008 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

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 :

$newtitle = Title::newFromText($name, NS_CATEGORY);

$newcategory = new Article($newtitle);

$newtext = "[[Category:$parent_cat]]";			
$newcat = $newcategory->doEdit($newtext,'Project', EDIT_NEW );

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)Reply[reply]

I think you mean $newcategory->doEdit ? --MrAngel 09:09, 24 April 2008 (UTC)Reply[reply]
Thanks, It's ok now ! --Teriblus 09:33, 24 April 2008 (UTC)Reply[reply]

MapLib extension

is posible to create a extension to add a iframe from MapLib like <maplib width="400" height="400">999999999</maplib> to do a:

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


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)Reply[reply]
The extension is needed only because it would generate an iframe (a restricted object) and because the target is a external URL that normally can't be rendered directmy within articles. So it should just handle the generation of the URL (from a single parameter) and of the iframe, and nothing else. The width and height parameters are superfluous, but the map id is mandatory.
Why not a simpler syntax like:
<maplib id="999999999"/>
with an optional style attribute (that users can adapt as they want, but that can be augmented with other things like, alignment, borders, background, , and an alternate content. (the default width and height could be part of the site-global extension settings and would be used if they are not already set within the user's style):
<maplib id="999999999" style="width:400px;height:400px"/>
and with the alternate inner content for the generated iframe, you can insert normal wiki code or other HTML:
<maplib id="999999999" style="width:400px;height:400px">[[Image:...]]</maplib>
Note that you proposal could as well take the form of a even more basic interwiki link:
[[maplib:999999999|Link description]]
that could be rendered as an external link to the page on the maplib site (but not as an embedded iframe). 05:32, 1 April 2009 (UTC)Reply[reply]

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 describe his preferences or other features

There are various EditCount extensions which would show the number of pages edited. Desciclopédia uses this in user-box templates "this user has edited x articles" alongside a non-standard "log count" (useful mostly for administrador's pages - "this tyrant has banned n users"). There are also some project: pages there which use the editcount information as part of a list of most-active users. I don't think a page creation or a revert is counted any differently than any other edit by EditCount, though. --Carlb 08:18, 27 September 2009 (UTC)Reply[reply]


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)Reply[reply]

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)

-- 06:41, 22 May 2008 (UTC)Reply[reply]

Backing up the complete site on your server is not enough? --Subfader 12:37, 22 May 2008 (UTC)Reply[reply]
My problem is the content should be portable for everyone in our team when he/she doesn't have internet-- 12:42, 22 May 2008 (UTC)Reply[reply]

'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)Reply[reply]

[ASSIGNED] 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)Reply[reply]

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


I'm developing what's described here (somehow). See QuickLink for more information.

--Kanor 23:48, 25 November 2009 (UTC)Reply[reply]

Addthis Social Boomarking

Extension:Social Bookmarking uses Addthis but the solutions is very unhandy.

  • 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.

--Subfader 07:47, 6 June 2008 (UTC)Reply[reply]

Don't know if this will suit you, but maybe a possibility...
You would need Extension:SecureWidgets for it to work.
--HTPCnz 06:59, 7 June 2008 (UTC)Reply[reply]
Thanks, but I want it appear on every page when user enables the gadget. --Subfader 08:34, 7 June 2008 (UTC)Reply[reply]
Use Extension:HeaderFooter perhaps? Jean-Lou Dupont 18:17, 12 June 2008 (UTC)Reply[reply]

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

  • 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.

--Subfader 19:06, 23 June 2008 (UTC)Reply[reply]

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)Reply[reply]
Done. --Subfader 20:07, 5 November 2008 (UTC)Reply[reply]

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!

see bugzilla:19481/Extension:FlagArticle --Church of emacs 15:26, 2 July 2009 (UTC)Reply[reply]

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? -- 18:28, 3 July 2008 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]
WHat's the benefit of seeing the redirected from article names when editing an article? --Subfader 18:41, 5 November 2008 (UTC)Reply[reply]
The benefit? It would show you right away if there are redirects on the page. That is plainly obvious. Having redirects on articles isn't very professional. This will make fixing them easier.Matt 09:47, 23 November 2008 (UTC)Reply[reply]

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">...</p>
--Benjamin Garn 19:03, 10 October 2008 (UTC)Reply[reply]

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. --Truetech (Talk)   MediaWiki Support Team 23:30, 4 September 2008 (UTC)Reply[reply]

Hard to find a solution working on all browsers...--Subfader 19:59, 5 November 2008 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

MW 1.12+ have the script maintenance/deleteOldRevisions.php for older versions check Extension:SpecialDeleteOldRevisions. --Subfader 15:32, 28 September 2008 (UTC)Reply[reply]

That would kill the entire revision history of every article, a mite bit extreme.

Certainly there is a need for a "infi-ban IP and remove all its contribs" as a tool to clean up spambot damage on wikis, but so far I haven't seen a quick, straightforward way of doing this as a one-click operation. The nuke extension does some (and only some) of what's needed, but a botspam run that's immediately reverted really isn't even worth keeping in the article histories (as none of the current versions of pages are derivative works of that revision). One could presumably delete spam from article histories by deleting the entire page, then selectively undeleting any revisions which aren't robot spam - but that's a slow, manual process. What's needed is a process which does the whole operation:

  • An IP or user is identified as a blacklisted known spambot
  • The IP (if static) is blocked permanently from editing or registering new accounts
  • All pages where the IP is sole contributor are deleted, en masse
  • All pages where the IP edited and was immediately reverted, discard both the spambot edit and the reversion from article history
  • All other pages where the IP is the most recent editor, delete that revision and go back to the last-good version of the page

If a human user is vandalising pages, the revision history may be worth keeping as admins may look at the record before deciding the length of this user's subsequent ban if and when the problems recur. If this is a spambot, odds are nothing it posts are worth keeping. Infiban, delete, gone. Automating this process would save the administrator's time for dealing with edits left by those pesky two-legged critters. --Carlb 08:43, 27 September 2009 (UTC)Reply[reply]

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.

See Extension:BackwardNavigation, which uses the sidebar "What links here" to do something similar. Bill Johnson 22:57, 16 January 2009 (UTC)Reply[reply]

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)Reply[reply]

Take a look HERE. --Aroekene 12:57, 27 October 2008 (UTC)Reply[reply]
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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
Why bother, they're invisible and treated as such. --Subfader 20:22, 5 November 2008 (UTC)Reply[reply]
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)Reply[reply]

Exclude Redirects from Search Suggest

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

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.

The database dumps for some wikis are huge and can take hours to generate a full set. I'd expect a version of Special:Export that came anywhere near attempting to generate a downloadable database dump of everything (or even a huge section of everything) would be so slow as to be useless - that's why the dumps are periodically run in the background every few days and put up for download, after all. --Carlb 08:53, 27 September 2009 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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 <code> or <pre>. When writing technical documentation and quoting source code it starts to drive a man nuts seeing <pre> and <code> all over the place. For example, instead of writing this:<pre>$IP/extensions/include.php</pre> You could just write `$IP/extensions/include.php`. The be rendered as



It might be helpful to use `` or ```. Or we could even use {{{ Trac-style }}} markers. That's much better than <pre> foo </pre>. Granted you loose the ability to tweak CSS style, but for 99% of the time I don't need to adjust the style of preformatted text. I let the main.css do that.

--Noahspurrier 02:42, 31 October 2008 (UTC)Reply[reply]

I don't see the usefulness of this at all. It's just as much work to type ` as it is to type pre or nowiki. Also, the backtick has a special meaning in PHP (it's the equivalent of wrapping everything inside of it into an exec() function), so that could be potentially confusing (and a huge security concern if not escaped correctly). Also, {{{ }}} is already used for template parameters. --Skizzerz 03:15, 31 October 2008 (UTC)Reply[reply]

Hide/Show articles in category

__HIDDENCAT__ hides the category on an article page. This is not what I mean.
Imagine a wiki about TV shows (bad example). Imagine "Seinfeld on NBC" as a category. There would be articles like "1995-04-16 - Seinfeld - S01-E05" etc but also repeats, e.g. "2003-11-04 - Seinfeld - S01-E05 (Repeat of 1995-04-16)".
I want to be able to hide those repeats on the category page but also to display them again.
Therefor the category on which this should be the case must be marked as "to be hidden". A simple "one-reason-per-wiki" solution would be to add "Hide" as catsortkey on the repeat article (2003...) for those categories it should take affect:
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 [[Category:Seinfeld|Hide]] and make the link "Show Reapeats".

A mutli-reason solution could be to use [[Category:Seinfeld|HideReason:Repeats]] 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)Reply[reply]

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

While I'm not really sure how it works, you could examine the Forum: namespace, and try to find out how it works. All links to creating a new forum use a preloader, which adds a header automatically. You might be able to do something like this, with a <div> tag at the top, along with a title hack, and finally a preloaded </div> tag at the end. Timeroot 16:10, 24 January 2009 (UTC)Reply[reply]

Automatical make categories

I need an extension who automatical make categories from Special:WantedCategories, because on my wiki i have a lot of wanted categories(about 5000).Thanks a lot!--Robypedia 19:36, 23 November 2008 (UTC)Reply[reply]

What's the use in it then? Just don't watch Special:WantedCategories ;) --Subfader 14:52, 24 November 2008 (UTC)Reply[reply]
Use case might be that you use Categories for, well, categorizing articles, while you do not need to actually have content in the category pages. As they don't exist, they look ugly (prompt you to create the category-page), when you in fact only need the list of articles in the cateogry. I want that, too. Or is there a way to disable the auto-editing of wanted categories when you click on them? --Borp 16:45, 11 March 2009 (UTC)Reply[reply]
It would be very useful to distinguish between categories with a blank page, and unpopulated categories. I'm sure it's more expensive from a performance standpoint to check if a category has articles than to merely look up if it has text, though. ? ChristTrekker 04:58, 14 April 2009 (UTC)Reply[reply]
Extension:Uniwiki_Auto_Create_Category_Pages creates categories when they are linked to, which will at least stop the list getting any bigger. -DavidSev 11:46, 31 August 2009 (UTC)Reply[reply]


Email deleted content back to the creator and other stakeholders.

There could be a checkbox in preferences - email: 1. any page being deleted that I've edited 2. only pages i created 3. pages i'm watching --- something like that. So if people want to delete stuff to keep things "neat and tidy" there would be less of an impact. The email would have the wiki markup of the edit before the delete tag or something... or just the last edit.. or the last few edits. Something like that.

Inline editing w/AJAX

Click, edit, save, done. All on one page.

please help

i want someone to create a wiki extension for which i am ready to pay. please mail me @ xman_in@yahoo.com for more details.

See jobs for another site focused on this. --Brian 22:50, 21 January 2009 (UTC)Reply[reply]

Logic circuits (makes an image from wiki markup)

A couple articles on wikipedia have logic circuit diagrams, and i bet electronics wikis use them too. I'd be nice if you could just enter in markup for a logic circuit and the image is created. -- 22:40, 29 December 2008 (UTC)Reply[reply]

Expand Shorthand

So that when you write mw, it is shown/viewed as MediaWiki. the abbreviation list could be defined on mediawiki:shorthand-definitions or something (like mw->MediaWiki etc.). How hard is that? I could use Extension:Replace Text but it's too much trouble than making a list.--Alnokta 10:42, 21 January 2009 (UTC)Reply[reply]

An indiscriminate search-and-replace across every page done is possible with the emoticons extension (the original idea was to replace :-) with a graphic face icon, but it can replace text with other text). Unfortunately, this is an overly-broad replacement and gets very annoying very quickly once it starts hitting text which you didn't necessarily want replaced. --Carlb 08:58, 27 September 2009 (UTC)Reply[reply]

Internal link

Hello, I search for some days an extension which I do not find.

I would like to create a link towards an internal document. For example: "file: /// c: / 1.txt" or "s: / common / doc / general-info.doc" but always mediawiki, request the "http"

Many thanks for your help Sébastien ( 09:26, 22 January 2009 (UTC))Reply[reply]

Maybe you should have a look at Extension:FileProtocolLinks. Lexw 15:26, 29 January 2009 (UTC)Reply[reply]

Switch article order on category pages

I'd like to be able to switch the order (asc/desc) of the articles (only) listed on a acategory page. It should enable 3 things:

  • set default order in extension
  • a tag to include manually into certain category pages for setting the opposite order of the default set in the extension.
  • display switch links (sort: asc | desc) in the same (not below) row as "The following X pages are in this category, out of X total."
  • a user preferency for the user's default order (still the switch links will be displayed though)

I think a lot of wikis would find use in this. --Subfader 21:09, 30 January 2009 (UTC)Reply[reply]

Looks like a job for Dynamic Page List. —Bytesmiths 06:24, 20 November 2009 (UTC)Reply[reply]


This extension will allow a wiki to import a page from another wiki. With this extension enabled, you start out creating a page as you would normally, but then instead of adding content in the text box, you put the URL of the page you would like for the wiki to import (maybe using some sort of subst like call {{slurp:url-of-the-page-to-import}}), and then the wiki will import the page with history - presuming the licenses are compatible.

Make Extension

I clap twice and whoop there it is. --Subfader 18:12, 12 February 2009 (UTC)Reply[reply]

Joking. I talked to the devs on the IRC chan and this page is really useless. Better visit http://www.mwusers.com/forums/. If you still believe in Santa Claus, keep posting your ideas.--Subfader

Magic button

Magic button would be an effective way to prevent vandalism in wikis. Magic button would be a button that reverts all the contributions made by the vandalist, deletes the markings of his/her contributions in page history and recent changes, and also gives him/her an everlasting banana.

So much with a single click (a verifiation system wouldn't be bad). It would make vandalism absurd because of the ease of making all the hard work discombobulate. Let's remember that all the wikis are not Wikipedia so the powerfulness and cruelty of magic button would not be a problem. It's really needed in wikis which are actively vandalized.

I'd like to push the button, homies! -- 15:02, 21 February 2009 (UTC)Reply[reply]

There are good reasons that this highly requested feature has not been included to MW. Also you only want to clean up the dirt that was there for quite a while (minutes, hours, days). Make your wiki safer so it won't get dirty at all... Start with captchas for registration (against bot registration), disallow anonymous editing, add bad words in $wgSpamRegex --Subfader 21:38, 21 February 2009 (UTC)Reply[reply]
All this is done. The problem is that in this case it comes to a religious wiki, and of course it makes anti-religious people vandalize it. They are not randomize vandalists. That's why it should be possible to make their vandalization dicombobulate easily. They must be made frustrated. Believe me or not, in this case it's necessary and will be in many other cases. Every wiki is not Wikipedia. -- 01:27, 22 February 2009 (UTC)Reply[reply]
I agree, when it comes to dedicated vandalists instead of random bot actions it's hard. But as said, there are good reasons that this highly requested feature has not been included to MW. I remember it was about deleting the user history. --Subfader 13:35, 22 February 2009 (UTC)Reply[reply]
Right. But because it's not included to MW, there could be an extension for extreme cases, imho. In the wiki I'm talking about it's needed and I don't have skills to create one. -- 15:28, 22 February 2009 (UTC)Reply[reply]

Images with relative (percentage) dimensions?

Would it be at all possible to implement sizing an image to the percentage of its containing element (table, div)? At least point me to some code which even attempts to do this (and no, Extension:ImageSizeInfoFunctions seems to be about something somewhat different). Or would such a functionality be impossible "by design"? Yury Tarasievich 09:06, 5 March 2009 (UTC)Reply[reply]

This would rock :) Would be good to use e..g align=right|size:20% so on big monitors it would be larger than on small ones. Technically no problem. There is some javascript command to catch the clients window width / height, but I guess it's not working in all browsers, like Intenret Exploder. Don't ask me how to implent :) --Subfader 18:41, 5 March 2009 (UTC)Reply[reply]
I was thinking more of avoiding the irregular widths of presentation elements and of achieving more classical typography of simple proportions (you know, 1:3, 3:5 etc.). But using the big monitors is good, too; as I see it, small monitors' users would benefit, too. Javascript idea I played with, but it won't help here, as it works after the parsing and serving; differently in different browsers, too, yes.
The most primitive way to implement seems to circumvent the blocking of percentage parameter in Parser and so always cache and serve full image. Quite not good, as images can get big these days. Still I'm willing to play with this. I'm now trying to get some directions in the [wikitech-l]. Help and suggestions etc. welcome, too. :) Yury Tarasievich 08:29, 9 March 2009 (UTC)Reply[reply]
If you think this is simple, you're wrong: most browsers don't have the logic to resize the images they have downloaded, without adding a non standard extension for this dynamic behavior (in addition, reducing/growing an image is not trivial as it requires filters and cna use various algorithms). So there exists various solutions (including SVG, the most standard one, and VML by Microsoft), but not within HTML or CSS alone. If you add Javascript, the solution will be highly browser dependant. As long as CSS3 will not be released and widely deployed in browsers, there's littely chance to see such support on the client side.
Now if you think that you could use Javascript ans Ajax to request resized images to the servers, it will certainly not rock (not only the charge on the server will be excessive, but also the browser response will be extremely slow. 05:43, 1 April 2009 (UTC)Reply[reply]
The one obvious problem is that many of us cache pages rather aggressively on high-volume wikis. That a varnish cache may need to hold three versions of the same page (one zipped, one gzipped, one plain) is an annoyance but manageable - but having to generate a different version of the same page every time just to resize images in some arbitrary manner would break the caching strategy entirely, more than doubling the load on the origin servers. I'd expect the sites would stop in their tracks under peak load if this were done. --Carlb 09:07, 27 September 2009 (UTC)Reply[reply]
Check upright=Factor here (didn't try on my wiki yet) --Subfader 00:58, 3 October 2009 (UTC)Reply[reply]

Document Expiration

I'd like to be able to set an expiration time for a wiki article along with an owner of the document. When triggered this would notify the documents owner and email/sms/communicate with them about the next course of action. It would not remove the article but would in some way notify the reader that the page has expired and therefore might house dated information. It could even be fancier and have a hierarchy of users to contact if no one responds to the messaging.

This mechanism would be used to remove the amount of document rot that happens when pages are orphaned or forgotten about. I see this extremely useful for any organization that uses its wiki to document an ever increasing and changing operational structure but has trouble maintaining updated documentation. Tomasz Finc --Tfinc 01:46, 7 March 2009 (UTC)Reply[reply]

I think Wikipedia has templates which do exactly this - after a certain date, they flag as "dated information" in the article. --Carlb 09:09, 27 September 2009 (UTC)Reply[reply]

Status of article

Could anyone suggest me one extension for choosing and displaying of a status for article. For example a drop down menu in bottom of page with a couple of entries (e.g in editing process, complete etc).

Thank you very much. --Pekarskij 15:42, 11 March 2009 (UTC)Reply[reply]

Mutual page pair invisible section transclusion/substitution

For instance, on a wiki dedicated exclusively to cataloging references to things "In popular culture", you could add something to the Wood page like

 In episode 6 of [[Firefly]], "[[Our Mrs. Reynolds]]," Jayne
 is given a wooden [[rain stick]] by a villager.

and after hitting "Save page" it would add both that to the Wood page and this to the Firefly page:

 In episode 6 of [[Firefly]], "[[Our Mrs. Reynolds]]," Jayne
 is given a wooden [[rain stick]] by a villager.

placing it using a set of configuration-defined rules based on the category/namespace of each page (ie. if the target page (Firefly) is in the Category:TV Show, it will place it under "Things this show has referenced" before the first section coming after it alphabetically).

If either is edited, the other page's content under that header is updated. For instance, if that section in Firefly were then updated to say

 In episode 6 of [[Firefly]] (number 3 in broadcast order), "[[Our Mrs. Reynolds]]," [[Jayne Cobb|Jayne]]
 is given a wooden [[rainstick|rain stick]] by a villager.

the corresponding text originally added to Wood would be changed to say

 In episode 6 of [[Firefly]] (number 3 in broadcast order), "[[Our Mrs. Reynolds]]," [[Jayne Cobb|Jayne]]
 is given a wooden [[rainstick|rain stick]] by a villager.

(The markup was chosen to be similar to what currently exists in MediaWiki without actually overlapping existant wiki formatting.) --Stuart P. Bentley 07:22, 15 March 2009 (UTC)Reply[reply]


I would like to see an extension that would check if a given page is in a given category. It would probably take the form of a hashed function, like this:


So, imagine a setting like this:

A page Foo is in the Bar category, but not in Baz or Koll. A page Bek is in the Koll category, but not Baz (directly) or Bar. Koll is a subcategory of Baz, but not Bar. A page Quok has not been created yet.

These would then be the basic inputs/outputs:

Input Expected Output
{{#incat:Foo|Bar|Yes|No}} Yes
{{#incat:Foo|Baz|Yes|No}} No
{{#incat:Foo|Bar|Yes}} Yes
{{#incat:Foo|Baz|Yes}} 0 (default value)
{{#incat:Foo|Bar}} 1 (default value)
{{#incat:Foo|Baz}} 0
{{#incat:Quok|Bar|Yes|No}} No
{{#incat:Quok|Baz|Yes|No}} No
{{#incat:Bek|Koll|Yes|No}} Yes
{{#incat:Bek|Baz|Yes|No}} Yes (by subcategory)
{{#incat:Bek|Bar|Yes|No}} Yes

If there is something like this, or if it would be feasible, I'd be very happy. This would probably have to be an expensive parser function, as it requires loading the cache of an entire category page, would definitely take more server time than #ifexist. But, used sparingly, this could be extremely helpful. Timeroot TalkContribsEdit Count 01:09, 31 March 2009 (UTC)Reply[reply]

I'll take a look into this. Matej Grabovský 11:36, 13 August 2009 (UTC)Reply[reply]
Well the code is finished, I'll try to find some time to submit it here later today. Matej Grabovský 07:47, 15 August 2009 (UTC)Reply[reply]
Sorry for the long delay and the bare documentation anyway here it is: Extension:HasCategory. Enjoy! Matej Grabovský 12:58, 16 August 2009 (UTC)Reply[reply]

Secure Login

If it is possible, I think it would be great developing extension which encrypt user password using or--Kwj2772 13:41, 5 April 2009 (UTC)Reply[reply]

Inactivity Log-out Timer

A method to set a timer that will automatically log a user out if there is no activity for an amount of time. (Time set in ether a special page, or in localsettings.php. Ideally the it would redirect to the login page after the log out.

I am surprised this is not a configuration setting.

Usernames starting with lower case

I understand the (original) logic for forcing the first character of a page name to upper case, but is forcing usernames in the same way really necessary?

I have installed an extension that links the wiki to the user accounts in phpBB. This means that new user accounts can "arrive" in the wiki with a lower case first letter, but are then are changed to start with an upper case first letter. This means that the phpBB account and wiki account end up being different.

Please could we have any extension or configuration option to leave the case of usernames alone? GhostInTheMachine 18:11, 18 April 2009 (UTC)Reply[reply]

$wgCapitalLinks = false; should allow it but doesn't. I opened a bug report. --Subfader 17:28, 18 April 2009 (UTC)Reply[reply]
I'm OK with leaving main page names to be uppercased. The problem is only with the user account names. GhostInTheMachine 11:44, 25 April 2009 (UTC)Reply[reply]
Hack in beta ... User:GhostInTheMachine/Lowercase_Usernames


Instead of edits by IP addresses being displayed as being by specific IP addresses, everywhere, the attribution would be to "Anonymous". Alternatively, some sort of unique identifier could be created, without having to give out IP addresses. For example, edits could be displayed as "Anon xxxxxx" where "xxxxx" is some sort of Hex code.

Goog idea. I can imagine this has been thought about since the displayed IP's is kind of sensible data. SInce nothing has been coded to core yet I guess there are valid arguments against it. --Subfader 23:02, 19 April 2009 (UTC)Reply[reply]
I saw http://www.mwusers.com/forums/showthread.php?t=4551. It shows a hack to make it happen, but appears to also hide IP's from admins; that may make it difficult to block vandals and spammers.
It will make each IP an 'anonymous coward' as well. No way for to differ them. -Subfader 03:29, 20 April 2009 (UTC)Reply[reply]
So if you had to ban any anonymous user, you'd have to ban them all? If so, that is too bad. : / Wikademia 03:36, 20 April 2009 (UTC)Reply[reply]


Right now,This extension could give the option to alternatively merge histories.


this would fix full-page-name magic word for wikis where it is broken.


This extension would make it so Special:Random/namespace would only seek a base page and not a subpage.

it would be more useful to add a new parameter to restrict the selection to base pages only. Check bugzilla and open a bug report. --Subfader 16:27, 31 May 2009 (UTC)Reply[reply]

Auto Title Prefix (like "How to" on Wikihow)

I wonder why in Wikihow articles, it always have prefix "How to." Can someone make an extension for that?

maybe you need to modify the skin template of your wiki to add title prefix. I also saw some extensions that can change title displayed on page, but they wouldn't work with 1.16.0.

Extension:Add/Remove/Update Extensions

Makes installing, uninstalling, and updating extensions super super unbelievably, shockingly, amazing, astoundingly, boringly, mindbogglingly, unsurprising trivial.... sort of like plugins on WordPress.

Extension:Configure does this partially. Matej Grabovský 18:28, 14 August 2009 (UTC)Reply[reply]


This extension would clone a page, perhaps via a special page. This way, content could be duplicated as needed, to create templates and what not, but then also, edit histories could be nicely preserved.


I'm hosting a wiki at my company that develops 6 major products. Each product group wants to use the wiki, but i'm afraid that the user contribution of articles will cause all types of categorizing issues with inexperienced wiki users. An extension that forces an article to first be categorized into any one of the 6 product groups (a 7th for general articles) would allow for proper categorization and hopefully the ability to search just within that product's articles. I've started work on this, but any ideas from someone also developing something similar would be greatly appreciated. --Bonezoo 17:30, 8 June 2009 (UTC)Reply[reply]

play external URL viedo

play external URL video File like linked image(not like embed video id)--Bluemangoa2z 12:06, 27 June 2009 (UTC)Reply[reply]

RAW digicams files

An extension that gives the ability to handle the digicam's raw files (like Nikon's .NEF) and other; ideally is just an interface between PHP and dcraw or ufraw-batch outputting their outputs on a string representing the picture that will be embedded on the wiki page; hint: something similar to the SVG handling?? Just an idea!--Fpiraneo 20:06, 28 June 2009 (UTC)Reply[reply]

Transclude section headings only as page links

This extension would allow one to transclude just the section headers from a set of pages or subpages and present them as page links preserving their rank.

The use would be on a composite page that would serve as a table of contents page for the page set. Users could click on an entry in the outline of headings and view the page.

The composite page would be built from markup similar to this:

<transclude headings>
</transclude headings>

or an alternate implementation that would collect subpages:

<transclude subpage headings>
</transclude subpage headings>

It would be like dynamically wrapping section headings in <includeonly>[[{{PAGENAME}}# and ]]</includeonly> tags.

I might have a peak at this. Matej Grabovský 18:31, 14 August 2009 (UTC)Reply[reply]

Hide Index in a category page

Up to Mediawiki 1.15, category pages always show the index of it's subcategories and articles. I just want to hide it in some pages. How about providing a Magic words to do that (suggestion __NOSUB__ and __NOLIST__)?. I think this one requires hack to the main code, not an extension.


Create an extension for Google Affiliates or any other of the big affiliate providers

I would like to include Google affiliates or become a publisher for any of the other big affiliate networks and would like to see a a extensiuon for that just like the adsense extension. Can anyone make or share that? I would really love to include it into my wiki http://www.klusopedia.nl

Would be great!


Allows for different Adsense keys to be injected into a page to be used for Adsense. It could give two contibutors a 50%/50% split, or any other split they agree to. It would allow for anywhere from 1 to perhaps hundreds of sharers. It could be done on a per page basis or wiki-wide. Emesee

Template Recursion

I'm looking for an extension (or patch) that allows configurable template recursion. --Niightblade 04:14, 1 September 2009 (UTC)Reply[reply]

If you can help, please leave a note on my talk page. --Niightblade 13:40, 19 September 2009 (UTC)Reply[reply]

Define point to add new section

When using the + tab on a discussion page, the new section is always added at the end of the article. To allow adding (inserting) a section at a pre-defined place in an article, please add a magic word, such as "__ADDNEWSECTIONBELOW__" which will define the point BELOW WHICH the section will be inserted. This will result in sections being ordered newest at top to oldest at bottom. Also consider supporting "__ADDNEWSECTIONABOVE__" which will result in sections being inserted in order from oldest to newest (normal MediaWiki order).

See Extension:PlaceNewSection Nx 23:35, 17 December 2009 (UTC)Reply[reply]

"Go" to categories FIRST

I checked the GoToCategory extension. However, is there any way so it will "Go" to the category first instead of MAIN namespace? thanks. Stahn 06:51, 3 November 2009 (UTC)Reply[reply]

have it done by disable lines 88 to 99 and also lines 878 to 893 in /includes/specials/SpecialSearch.php, is it okay to do so? Stahn 07:26, 3 November 2009 (UTC)Reply[reply]

Subtitles in a wiki page for an embeded video

Context :

The idea would be to have the subtitles editable in a wiki page so that many could improve them.

--Dieudo 16:19, 7 November 2009 (UTC)Reply[reply]

Paste image from clipboard Extension

I have seen the TWiki JavaPasteAddOn, wich provides a button to paste images from clipboard directly into the article. What does it do:

  • Start a signed Applet.
  • Get Image Data from clipboard
  • Greate a JPEG
  • Upload JPEG into the Wiki-Software
  • Embed File:WhatEver.jpg into Wiki-Page

Could we get this as MediaWiki Extension? The Source of the TWiki Add on can be found here: [6]

Difference Like

Can you do a extension, difference like. Useful differences will get a positive vote. Same Facebook? -- 12:58, 24 November 2009 (UTC)Reply[reply]