PmWiki 的設計,讓您可以輕易地升級現有的PmWiki,而不會影響您現有的一切資料。在絕大部份的情況下,您只需要將最新版的PmWiki檔案複製至您現有的Pmiki資料夾即可。

PmWiki 1.0版本請注意: 從1.0.x 升級至2.0 ,除了複製檔案外,還需要其他較多的工作。請參見Upgrading From PmWiki 1

如何升級您的:

1. 閱讀版本訊息release notes

在升級之前請仔細閱讀ReleaseNotes,以得知升級版本與您現有版本之差異。並可得知新版本的重要變動或是升級前所需的準備工作。

2. 備份

在做任何升級之前,請總是backup您現有的PmWiki。您可選擇直接複製您PmWiki程式的整個資料夾;也可以只複製您的wiki.d/ 資料夾以及您之前所做的其他客製化設定(例如 config.phplocalmap.txt等)。

3. 下載並解壓縮

請至download頁面,下載您所需要的PmWiki版本。

請解壓縮您所下載的,名為tar -xvzf tgzfile的壓縮檔。解壓縮產生pmwiki-x.y.z 資料夾,便是新版本的PmWiki了。

4. 複製

複製pmwiki-x.y.z中的檔案,並覆蓋您現有的PmWiki檔案。例如:如果您的PmWiki檔案安裝於名為pmwiki的資料夾,要用新檔案覆蓋原有的檔案,請輸入以下的指令:

cp -a pmwiki-x.y.z/. pmwiki

Note that BSD systems will not have the -a option as a command-line argument for cp, but that's okay, since it's just shorthand for cp -dpR, so use that instead of -a.

Some environments have an alias established for cp that enable interactive prompts before overwriting a file. To work around this specify the absolute path to cp, such as /bin/cp.

On (some) FreeBSD servers and Mac OS X systems you need to use

cp -Rpv pmwiki-x.y.z/. pmwiki

(抱歉,筆者並不會操作BSD系統,深怕在操作上誤導了BSD用戶,故放上原文。)

5. 更新您的客製化外觀及recipes

以上,您的PmWiki更新已經大致上完成啦!

現在,請使用PmWiki:Site Analyzer來檢測您是否有recipes需要進行更新。

除非您的PmWiki客製化設定儲存於pmwiki.php或者是scripts/資料夾中,否則您的PmWiki應該可以順利且正確地運作! (所以並 不建議 更動上述的檔案)

(Local customizations? should go in local/config.php, pub/css, and pub/skins/yourskinname)

Note: Additional tips can be found on the PmWiki:Troubleshooting page.

How can I determine what version of PmWiki I'm running now?

See version? - .

How can I test a new version of PmWiki on my wiki without changing the prior version used by visitors?

The easy way to do this is to install the new version in a separate directory, and for the new version set (in local/config.php):

    $WikiLibDirs = array(&$WikiDir,
      new PageStore('/path/to/existing/wiki.d/{$FullName}'),
      new PageStore('wikilib.d/{$FullName}'));

This lets you test the new version using existing page content without impacting the existing site or risking modification of the pages. (Of course, any recipes or local customizations have to be installed in the new version as well.)

Then, once you're comfortable that the new version seems to work as well as the old, it's safe to upgrade the old version (and one knows of any configuration or page changes that need to be made).