This page explains how to download and install PmWiki 2.1 and 2.2. Here’s a list of related pages:
If you upgrade, please read the page Upgrades.
Download the latest stable version of PmWiki as a
Download the latest beta version from the PmWiki:Subversion page.
Unpack the archive (
README.txt An introductory document pmwiki.php The main PmWiki script local/ Configuration scripts (local configuration files) cookbook/ Recipes (add-ons) from the Cookbook docs/ Brief documentation, sample configuration scripts pub/ Publicly accessible files pub/css/ Extra CSS stylesheet files further not found pub/guiedit/ pub/skins/ Layout templates for custom look and feel scripts/ Scripts that are part of PmWiki wikilib.d/ Bundled default PmWiki pages
The pmwiki-x.y.z directory needs to be placed into a location accessible by your webserver (e.g., in a public_html directory of some sort). You can place files and directories using a number of methods — FTP, or a Unix
Note: It is recommended to change the “pmwiki-x.y.z” directory name to be simply “pmwiki”.
In most cases PmWiki will do this for you. Open a web browser to the pmwiki.php script on the server (i.e., not the one on your local computer or accessed using a file://... URL). PmWiki will then analyze your system configuration and provide instructions (if needed) for creating the wiki.d/ directory which will be used to hold the pages created for your site.
3a. You can create the wiki.d/ directory manually, and then give it full write permissions (i.e., “
3b. On some systems you can let PmWiki create wiki.d/ by temporarily changing the permissions on the directory containing the pmwiki.php file to 2777. In Unix this is commonly done by changing to the directory containing pmwiki.php and executing the command
(note the dot at the end). The
After establishing directory permissions, try opening a browser to the pmwiki.php script again. If all is well, the wiki.d directory will have been created and you’ll see the default home page.
Important: If you used method 3b, you should reset permissions by executing “
5. Set language
If you want to use PmWiki in a different language download the international language pack as zip archive (i18n-all.zip) from http://pmwiki.org/pub/pmwiki/i18n/. Then extract it and copy the files into the wikilib.d/ directory as described above. Besides the -all file you can also download your country localization file only.
Languages available are:
There are two directories in the decompressed i18n archive, scripts and wikilib.d. Copy the files respectively contained in these directories to the scripts and wikilib.d of your PmWiki directory. For example, for French localization, PmWiki Fr?.* and PmWiki.* must be contained in the same directory.
Then, enable localization by adding an instruction to local/config.php to load the language translation page of your choice. For instance,
Read more about this on Internationalizations.
Resist the temptation to rename pmwiki.php to index.php because if you rename the file it will not be overwritten during an upgrade.
Q Should I rename pmwiki.php to index.php?
Renaming pmwiki.php is not recommended. Instead, create an index.php file that contains this single line
Q How do I make pmwiki.php the default page for a website?
Create an index.php file that runs PmWiki from a subdirectory (pmwiki/ for example) and place it in the site’s web document root (the main directory for the website).
Note: You will also need to explicitly set the
Q How do I enable “Clean URLs” that are shorter and look like paths to my wiki pages? Why does pmwiki.org appear to have a directory structure rather than “?n=pagename” in URLs?
Q Is it possible to move wiki.d to /tmp/persistent/foo/wiki.d (a new sourceforge rule)?
Sourceforge suggests moving everything to ‘tmp/persistent/new-folder-of-your-choice’ and creating a symbolic link to the new folder on /tmp . It works — see Cookbook:SourceForgeServers.
Q How can I run PmWiki on a standalone (offline, portable) machine ?