Extension:Tasks

The Tasks extension was created by Magnus Manske in December 2005. Its purpose is to manage creating, processing, and closing tasks for a page.

Installation
require_once( "extensions/Tasks/Tasks.php" ); // Or "extensions/Tasks.php", if you copied only the file and not the directory
 * 1) The Tasks extension requires MediaWiki 1.6beta or above, because of several essential hooks.
 * 2) Get Tasks.php from the extension module in CVS and put it in the "extensions" directory of your MediaWiki installation.
 * 3) Look at the comment at the beginning of the file. Run the MySQL statement (with respect to your database prefix!).
 * 4) Enter the following in your LocalSettings.php (in that order):

Configuration
You can change the appearance and behaviour of the extension through system messages and CSS settings.

System messages
Several system messages (in the "MediaWiki:" namespace) serve as settings for the extension. They all start with "tasks_".Some important ones are listed below.

Task messages

 * tasks_task_types:This is a list of available task types. Task types are separated from each other by a "|", and each has the form "NUMBER:TEXTKEY:TEXT", where TEXT is the local translation (e.g., "Clean up") and TEXTKEY is a one-word key (e.g., "cleanup"). NUMBER is used internally in the database. Each NUMBER and TEXTKEY has to be unique. Once a type is in use, neither NUMBER or TEXTKEY should never be changed. You can deactivate a task type by removing its data-triple here, however, do not reuse either the NUMBER or the TEXTKEY on anothe task type. Several of the other messages and CSS styles use the TEXTKEY.
 * tasks_creation_tasks:A comma-separated list of NUMBERs. List the numeric key of each task type here which comprises a "page creation". Upon creation of the requested page, all such tasks will be automatically closed.
 * tasks_significance_order:The order for messages to appear in the header of pages with tasks. Only tasks with a type mentioned here can appear in the header, and of these only the "highest-ranking" one will appear. Example "rewritediv element with the ID "task_sign".

Status messages

 * tasks_status_TEXTKEY:Several messages, one for each (open,assigned,closed,wontfix). Contains the translation of the task status (e.g., tasks_status_wontfix="Won't fix").
 * tasks_status_bgcol_TEXTKEY:Similar to the one above, this one holds the background color of the status cell in the task tables (e.g., "red" or "#FF9999").
 * tasks_action_TEXTKEY:Again, for each status, this contains the translation for action-after-the-fact (e.g., "Task \"$1\" opened.").

Other messages (there are lots more!)

 * MediaWiki:tasks_existing_table_header:The header titles for the status tables. Each header is separated with a "|".

CSS

 * task_header:The ID of the title of the header of "Task:" pages.
 * task_header_table:The ID of the table in the header of "Task:" pages.
 * task_sidebar_TEXTKEY:For each textkey in tasks_task_types, the ID of the li element in the sidebar.
 * task_transcluded_comment:The ID of the transcluded task talk page (user option, default=off).

Little known features

 * If there is a create and/or write request for a "blank" page, and this page is created, the appropriate tasks are automatically closed.
 * If a page is deleted, all its tasks are removed as well (should probably be turned off?).
 * Every change in a task status is logged on a log page, and shown in RecentChanges as well.
 * In order to close or assign tasks you need to be a logged in user.

Wish List

 * When a Task is assigned, it should be sent an Email to assigned user.
 * When a user logs in, there must be an automatic display of their (pending and new) tasks.
 * A way to see a sumary of open tasks at another page than the tasks search page, I want open tasks in a list at my front page.
 * Sentences such as "Very well" "Splendid" "Go on" would appear for every task done (or it might be Anthe re's flower)