Extensions/Wanted Extensions

Wanted Extensions

 * See also Category:Feature Requests

Warning: feature requests filed here may not be read by developers. The proper channel is Bugzilla.

Programing Language / objects
A system or extension for documenting objects of a programming language. --Magick 11:12, 20 October 2006 (UTC)

Import/Export

 * Import from non-wikitext files (ex. Word documents, HTML files)
 * Done 1) here without touching Wiki code just using Special:Import Renmiri 09:37, 25 February 2006 (UTC)
 * See details at Wordpress Export for Wikipedia
 * Done 2) using an extension here but not using GNU license. No Wordpress required Renmiri 22:04, 9 March 2006 (UTC)
 * Done 3) Use a word macro with functionality to extract pictures: Word2MediaWikiPlus.


 * Export to other formats (ex. RTF, Word document, OpenDocument, PDF, Postscript).
 * I think it would be the best to implement a Postscript engine to the Wikimedia-Software. Now we can only pick the link "Printable verson" in the Toolbox to create a printable document from an article. The result is not very good, because this tool doesn't define the real page layout. It depends on your browser how the pages are formated if you want to print it and this is a problem especially for projects like wikibooks. To solve this problem it would be good to have influence on the page layout by defining it. This page-defining could be done by using a page-layout language like post script. Red Rooster 18:51, 22 March 2006 (UTC)


 * Export Images

Output

 * Add rel="nofollow" to links to articles that haven't been created.
 * If you are using short URLs (e.g. wiki/Main_Page and all the files are in w/), then deny the w/ directory in robots.txt

User-agent: * Disallow: /w/

Display visitor IP address
The following code can display a visitor's IP address, host and proxy on the leftside of every page. The exact position is up to individual choice, but i've put it between navigation and search on our site.

The code goes in Monobook.php

   
 * 1) echo "Proxy IP: $proxy  ";
 * 2) echo "Proxy Host: $proxyhostname ";

I deliberately commented out the proxy info to save space.

Rick

Interface

 * Contact form to be integrated in a wiki page. For example: user@domain.com or username
 * Guestbook-Extension - Form for new entry. Saved and displayed on a protected page.
 * was added by me - see Guestbook extension for more information (--Mcmilk 21:50, 26 October 2006 (UTC))
 * Spacing control (double spaced, expand the standard distance between paragraphs, etc)
 * Tag clouds
 * More sidebars besides toolbox and navigation
 * See $wgNavigationLinks and MediaWiki:Sidebar for adding to existing sidebar.
 * Color coding users according to user groups
 * Interactive image editing
 * Includable special page that has name of last edited/last added article of a category. (you can try using editable templates)
 * Non-article related rating system
 * An Address/Contact Book (with vCard import/export)
 * Add special page WantedImages
 * Allow registered non-admins to rollback "page blanking"
 * 'Add this article to Category' (perhaps in toolbar?) with dropdown list of available categories
 * Similar: On category pages, an input field similar to inputbox that lets users "Add a page to this category" (redirects to blank edit page, with the referring category already inserted)
 * A way to allow users to build a list on the side bar of their favorite pages in the wiki
 * Collapse/Expand sections (Tree View). This would be particularly useful for the Wikireason Logic Tree
 * Display the pages as a map. i.e. site map, or even better mind map - something like freemind. based on the links in the page
 * When the Special:Userrights page comes up, it should give you an option to choose the users from the list in the database. Yes, I know that you can go to Special:Listusers to see all the users, but this would be more convenient for small wikis.
 * You should be able to set a default user level for new users using the Mediawiki interface.
 * Already known text input format, such as BBCode and/or other frequently used formats
 * Support for appending/prepending/creating a wiki page via email. (i.e. Send an email to PageTitle+create@wikihost.com)

Admin

 * Block edits to user pages except by that user and sysops
 * Block edits to free defined user group
 * Special page to revert all edits by a certain user or IP address (within a time frame)
 * Special page to allow deletion of users
 * Extension to allow sysops to delete older revisions of an article
 * Support for alternative databases: Oracle, PostgreSQL, etc
 * Special page to allow sending email to all users (or specific groups) of a wiki
 * Special page to reset passwords without using e-mail
 * Account activation requires email verification [URGENT]
 * Request account for wikis that don't allow account creation
 * Allow rollbacks of rollbacks
 * Special page to rename/edit an user
 * Restrict editing of certain pages to certain users
 * Global search and replace

Usage statistics

 * Provide a dump of the apache access logs see http://httpd.apache.org/docs/1.3/logs.html#accesslog This will allow the calculation of page hits for any article.

Uncategorized

 * Internationalization: Allow pages to appear differently for each browser language, keep all translations in one place
 * Make dynamic content transclusion easier
 * Polling that can be displayed on article page (see Poll)
 * Guestbook-style interface (you can do something like this using the regular wiki)
 * Ability to replace talk page with real forum instead of wiki page (see User:Zem/Forum extension)
 * Javascript to allow tabbing in textarea
 * Ability to attach files to pages
 * This... is a textbook example of an ambiguious request. The capacity already exists to store image data inside wiki and to link/display images on pages.  The very notion of 'attaching' an image to a specific wiki page runs contrary to the very purpose for which wiki exists, which is the collaborative effort and shared media resources.  -Verlocs 12.104.195.32

This funcationality already exists in MediaWiki. In the LocalSettings.php file is a setting to indicate what file extensions to exclude (all others will be included). If you need a file to be included, that is not already included, you can just change this variable.
 * I think he means attach any type of file, not just images. im also looking for this functionality.  seems clear to me -AaronC


 * Highlighting terms on a page based on URL/search referral
 * Filtering on alluser list based on user rights
 * Conditional logic in templates (see Winter scripting language for a possibility)
 * A macro to insert mail addresses that will be displayed in obfuscated form if the reader is not logged in, and as a proper mailto: link otherwise
 * Grabbing the latest posts from a phpBB forum and a Wordpress blog.
 * See Wordpress Export for Wikipedia and play with the WK.php script Renmiri 17:36, 25 February 2006 (UTC)


 * Grabbing any RSS feed and include it in a box
 * See Wordpress Export for Wikipedia, it gives you the XML format to import XML into Wiki using the built in Special:Import Wiki page, RSS is XML and any XSLT program can taylor it to output the XML / Wiki format Renmiri 17:40, 25 February 2006 (UTC)


 * Simple spreadsheet functionality (example: summing a column of a table)
 * Cooking recipe extension would be nice. It should be possible to use Wiki markup language to store recipes in common format to MediaWiki. It should allow storing informatino about recipe's ingredients, cooking instructions etc. It would be nice, if you could also store picture from food to recipe. Any directions how to proceed?
 * Dynamic creation/update of a Google SiteMap format file to speed Google Index updating.
 * see ThinkLemon. Also for a yahoo urllist.txt visit my blog here for an edited version of the Google sitemap generator. --Elliotgoodrich 15:47, 31 May 2006 (UTC)


 * For protected pages allow users to 'edit' them. Edits are not shown on the protected page but in a different page. An administrator can then view the edits and accept or deny the edits. Accepted edits are automatically made to the protected page.
 * Should have an extension to allow users to write definitions of word inside tags, and have these words automatically alphabetically added to a database of words that users can scan through. Sometimes you don't want to have a separate page for each word as users may not know the exact word for which they are looking.
 * Some sort of bulk import of HTML files would be handy
 * RandomLine extension. Usage: Article. Outputs a random line from specified article.

Interface
i'd like my pages to have extra attributes ... e.g: books: author, number of pages, written in ...

the pages should include the attributes and be sort- and searchable by these attributes

maybe adding a related table to the page with the seperate information, what would destroy the history function ...

maybe similar things already exist

curmetsefrog@gmx.at


 * Look at Semantic MediaWiki, it's a very powerful tool which does what you want.

Jabber Presence Plug-In
I would love to see a jabber plugin for MediaWiki, specifically using Wildfire server.

Here is the syntax required

http://www.jivesoftware.org/wildfire/plugins/presence/readme.html

jasona@gmail.com 07/25/06

Hi, here is the requested Jabber Presence Plugin for MediaWiki.

Create a file in jour extensions folder : Jabber.php : setHook( "Jabber", "RenderJabber" ); }

function RenderJabber( $input ) { $output = ''; return $output; }

?> NOTE #1 : Replace jabber.example.com but your hostname. NOTE #2 : You must run Wildfire 3.1.1 in order to be able to use the Presence Plugin. Upgrade then install the wildfire presence plugin on your server. NOTE #3 : You must setup the Presence Plugin through the Wildfire admin page in order to allow anybody tu see users's status.

Usage : user@jabber.example.com

This works perfectly on my MediaWiki 1.7.2

Hope this can help.

Best Regards. KlinT ( klint@klintcentral.net )

Ticketing
Im setting up a wiki to form a new information system on systems infrastructure at my company. The structure of documentation itself poses no problem, but one thing I want to implement does. I want to set up a knowledge (error) base. This should provide easy documentation of faults and make retrieval of this information almost immediate. Additionally, referring to a problem between teams by using the unique identifier can make communication easier im thinking along the lines of KB_Article:[numbered_identifier]. This would require a component to maintain a counter within wiki and auto-assign this number to newly created kb articles, preferably forcing the layout of the article (see extension request from Blckdmnd99, will look into options provided by barrylb) As much as i would like to avoid the analogy, something along the lines of the Microsoft Knowledgebase There are solutions available but those require a full implementation of a service management tool with limited dump-to-wiki functionality for solutions. A simple extension however would suffice.

All help is appreciated VinceV

Can I rephrase the request? - may we have a class of articles with states and automatic enumeration? The media already provides all the necessary elements, it is the supporting tools to manage (spawn, sort, assign-to-user, change state) these articles that is "new".

Most of the required tools are already supplied by MediaWiki_Bulletin_Board, what will be missing is support for TYPE and autoenumeration and perhaps more fine grained STATES. I'm off to play with the current Beta.

And, yes, "Knowledge base" is the wrong analogy :-) Wikipedia is a knowledge database!


 * MediaWiki already generates a primary key called  for each new article. You can see it if you dump your   database with . Here's the table definition where it appears:

-- -- Table structure for table `page` --

DROP TABLE IF EXISTS page; CREATE TABLE page ( page_id int(8) unsigned NOT NULL auto_increment,  page_namespace int(11) NOT NULL,  page_title varchar(255) character set latin1 collate latin1_bin NOT NULL,  page_restrictions tinyblob NOT NULL,  page_counter bigint(20) unsigned NOT NULL default '0',  page_is_redirect tinyint(1) unsigned NOT NULL default '0',  page_is_new tinyint(1) unsigned NOT NULL default '0',  page_random double unsigned NOT NULL,  page_touched char(14) character set latin1 collate latin1_bin NOT NULL default '',  page_latest int(8) unsigned NOT NULL,  page_len int(8) unsigned NOT NULL,  PRIMARY KEY  (page_id),  UNIQUE KEY name_title (page_namespace,page_title),  KEY page_random (page_random),  KEY page_len (page_len) ) ENGINE=InnoDB DEFAULT CHARSET=latin1;


 * I don't know if there is any user-level access to  of the type you seem to be asking for. Also, the   sequence would be discontinuous for one type of page, because it would increment for every new page on the wiki. You might look at TWiki which from what I have read has more structured wiki features and support for wiki applications than MediaWiki does, at the moment anyway. Perhaps with all the corporate interest in MediaWiki resulting from the overwhelming popularity of Wikipedia, MediaWiki (or perhaps a separate enterprise version thereof) will evolve into something more like TWiki, in terms of having the kind of structured wiki features the typical corporate user expects. Teratornis 05:41, 25 December 2006 (UTC)

Select categories and display pages
Is there an extension that shows a site wehre checkboxes with all the categories are so that you can pcik whatever you want to and the sites in the selected cats are shown? Thanks! mediawiki-1 [at] wikiplant [dot] org

Tracking or Issue Management Extension
What would be great - and probably quite easy to program and implement - would be an extension that helps setting up, managing and and maintaing lists of issues, i.e. a tracking system that could be used, for example as a "bugtracking system". I know there have been attempts from bugtracking systems (e.g. Mantis Bugtracker or Trac) to incorporate a wiki into their system (meaning, for example, that you dont have to log into Mantis and, subsequently, its Wiki); however, I am not aware that this would have been attempted using MediaWiki as the primary platform and an add-on or a mediawiki extension that acts as a bugtracker or issue management extension. While the Tasks Extension lists all Tasks on all Wiki pages on one page, what is needed in addition or independently is a system that helps creating, listing, collecting, maintaining, and updating tasks on one page.


 * TWiki might have some wiki applications that would do what you want. A list of TWiki applications is here. I have not tried installing TWiki yet; I might, after I get farther along with MediaWiki. I'm not necessarily advocating TWiki, but maybe you could get a tracking system working in TWiki before someone will write one for MediaWiki. According to the MediaWiki page, the MediaWiki development team does not use MediaWiki to track bugs in MediaWiki. Instead they use MediaZilla (their version of BugZilla). Teratornis 06:13, 25 December 2006 (UTC)

Review Extensions
There is a new Rating script at LeerWiki.nl. This script has your stars and is powered by AJAX.
 * I'm looking for a simple star rating review extension that could be used on basically any topic (restaurants, stores, music, bars, even people, anything). I'd like it to look like the one on the right side of this site (I spoke to the creater of that site, and he isn't prepared to release the source code yet).  Any suggestions?  --Mijunkin 05:48, 3 November 2006 (UTC)


 * There is something called Review.php which is in SVN but doesn't appear to have any documentation on Meta. There is also this: http://www.wikihow.com/WikiHow:RateArticle-Extension . But these are both like one rating corresponding to each page, which might not be exactly what you're looking for. 128.250.80.15 09:07, 11 December 2006 (UTC)


 * The solution available from LeerWiki.nl is not working with MediaWiki 1.8.2. It generates a blank page, meaning the wiki can not display any pages anymore. Seems that everyone with 1.8.2 who tried it, faced the same issue. Anyone can help fixing this would be real great help. Alain --66.131.228.50 04:52, 31 January 2007 (UTC)

Time Management/Tracking

 * I am looking for a wiki extension that can somehow tie into the time tracking. Like users log-in to their account and register their time that they have worked on certain projects. Based on that certain reports should be able to generate. I have limited knowledge of wiki therefore would love to know if something is already out there or a freeware that can merge with wiki to do this.

Blank pages
I'd really like an extension that could quickly check every page in the database and flag up any blank ones. This'd make it easy to check for blanking vandalism and unwanted pages. Thanks, 82.19.27.115 23:34, 10 January 2007 (UTC)

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