Installing MediaWiki takes between 10 and 30 minutes, and involves uploading/copying files, and running the installer script to configure the software.

Many Linux distributions provide MediaWiki in a packaged format for that distribution. The MediaWiki development team refers you to your Linux distribution for assistance with installing, configuring or using them. The individual communities & companies who maintain such packages should provide installation instructions.

You use a different database prefix for each wiki (for Postgres, you can achieve a similar effect by using different schemas and users) For information on an alternative way of setting up more than one wiki using the same server, database and source, see Steve Rumberg's excellent expose and additional comments from users. Shell access (SSH access) is not required for installing MediaWiki, but it is highly recommended.

How to install more than one wiki on a single server, using the same source code, and using the same database (v1.5.1, May 2006)

Yes, MediaWiki can be installed multiple times in different directories using either the same database with a different set of table prefixes (configurable upon install) or using different databases altogether. Additionally, you may want to make some settings common for all the installations, and have a central place where changes to these can be made. Since the configuration file (LocalSettings.

There is a project at mw:Project:PD help that is creating a self-contained help system, with links to an experimental pywikipedia bot that can mirror that. Mediawiki has problems with autostarting sessions. Check your php.ini (you can run phpinfo() to find where it is located) and look for session.auto_start. It should be '0'. Also, session.use_cookies should be '1'. If you don't have access to php.ini and you're using Apache try to create a .

The latest stable release of MediaWiki can be downloaded from download.wikimedia.org or sourceforge.net. Files are supplied in a .tar.gz archive. MediaWiki can also be obtained direct from our Subversion repository. See also Download

MediaWiki 1.12 is in a development state at present, and has not been packaged into a general release. The code can be downloaded from Subversion if desired. Wikipedia and other Wikimedia web sites use the current version of the code in development; at present, this is MediaWiki 1.12alpha. Coupled with the use of several extensions, this means that functionality between these wikis and your particular setup may differ.

No. Wikimedia is the name of a group of wiki-based open-content projects managed by the non-profit Wikimedia Foundation. MediaWiki is the software developed to meet the needs of these projects. edit] I tried that but it didn't work I had a problem, I came to this page and it told me how to fix it. But it didn't work, the problem is still there! Nine times out of ten this is because you didn't clear your cache. The simple test for this is to request a page that hasn't been requested before.

There are two timezone-related settings: $wgLocaltimezone and $wgLocalTZoffset. Set both in LocalSettings.php. $wgLocaltimezone is used for formatting the timezone in signatures, and should be set to the locale name, for example "Europe/Berlin". $wgLocalTZoffset sets the default user preference the number of hours your local time differs from server time, and is used for timestamps seen in recent changes and history views.

Set $wgReadOnlyFile in LocalSettings.php to the name of a file, then put the reason for read-only mode inside the file. The contents of the file will be displayed to anyone trying to edit the wiki. Since 1.5 you can set $wgReadOnly to a string describing the reason for read-only mode, instead of creating a file. (Usual wiki markup is allowed in this string).

You can hide the Powered by MediaWiki image by adding the following to your wiki's MediaWiki:Common.css: If you want to remove it completely, you could alter /skins/MonoBook.

First you should try a PHP cache engine such as eAccelerator or APC. It will save the parsed PHP scripts and enhance performance a lot (this is something you should use anyway on any PHP installation with non-trivial traffic). Zend Platform also contains a bytecode cache, however its "dynamic content caching" is not supported in MediaWiki at the current time. Memcached will provide some performance benefit, especially for heavily viewed sites.

Under 1.5, to disable all view top tabs, create a new skin according to the instructions in MediaWiki look and feel#Skin and name this MonoBookNoViews. Set this as the default theme. Logged in users will need to change their default theme to see the tabs to edit pages, however. You will need to remove the section of code in the MonoBookNoViews.php file which generates the views (top tabs).

We currently have the opportunity to add comments, which are not displayed: Maybe a special comment could be detected by the engine and used to fill the string this->Keywords. How is this done in MediaWiki 1.6.x because those functions don't exist --Elliotgoodrich 19:41, 22 May 2006 (UTC) I have managed to fix this http://www.psconclave.com/blog/mediawiki-mods/meta-tags feel free someone to write a proper guide for wikimedia as I don't have time at the moment.

No, remote loading is discouraged. If you're really keen, you can set up a mirror of it and use that.

With each new install of the client, you are given a new node ID. Each time you re-install the client, you will have another node ID. When you reinstall - just copy that file to the same directory it was before and you will not have to add another node to your stats. No. If you stop a run before you have completed all the conformers for a candidate, the docking will be aborted.

You can use the attachment:wiki:TracWiki:mediawiki2trac.py script as a starting point. WikiProcessor for the MediaWiki styles has been started as trac plugin on http://trac-hacks.org/wiki/MediaWikiPluginMacro.

Use it! When you see a page that you like, click on the "edit" link on top to learn its anatomy. It is intuitive and you can just copy the features you want into your own page. As long as you do not click on "save", no changes will be recorded so there is nothing that can go wrong if you click on "edit". Use it! When you see a page that you like, click on the "edit" link on top to learn its anatomy.