このページは、時々繰り返される質問を集めたものです。

あなたがDokuWikiでここに書かれていない問題を抱えているのであれば、その質問をここでするべきではありません。新しい質問は、「サポート受けるにはどうしたらいいでしょうか？」をご覧ください。

- General

私はこんな風に使っていますよ!!

• プログラムコードサンプルも含んだ色々なフォーマットに対応している
• 構造的な文書作成がしやすい
• サーバーがダウンしても、データファイルが読み出せる(プレーンテキストで保存されているから)
• 書くのを楽にしてくれる小さな仕掛けがたくさんある。たとえば、脚注、省略表記、構文のハイライトなど。
• ほかにもたくさん。とてもおぼえきれないくらいです。

- What makes DokuWiki so good for Documentation?

Lets see what I can make up!!

• It supports multiple ways of including code examples
• It's easy to create structured documents
• The datafiles are readable even if your Server goes down (stored in plain text)
• There are all those little gimmicks that make documentation fun: footnotes, abbreviations and syntax highlighting
• maybe more I can't remember

- What License is DokuWiki Under?

I'm a little bit confused about the license of DokuWiki. Can I use it on a commercial website?

The short answer is yes. But let's explain it a little bit: in fact there are two licenses. One for the software called DokuWiki and one for the content in my DokuWiki installation at wiki.splitbrain.org.

The one that is probably the one you are interested in, is the one for the software. It's the GNU General Public License (or shorter: GPL). This means (simply spoken):

You get some rights:

1. You get the software and the sourcecode
2. You are allowed to use the software in any way you like
3. You are allowed to change the sources to your needs

But you have to accept these terms:

1. There are no guarantees of any kind - if it breaks anything for you then it's your problem ¹⁾
2. If you want to redistribute the software you need to do this under the terms of the GPL which means you have to redistribute the full sourcecode (including your modifications), too.
3. You may not redistribute the software and say you wrote it all yourself - but that is pretty obvious anyway isn't it?

The second license applies to all the content which is created here in the DokuWiki at wiki.splitbrain.org. It is licensed under the Creative Commons Attribution - NonCommercial - ShareAlike license (Sorry no official short form). Again a simple explanation:

Again you get some rights:

1. You may of course read the content
2. You may change the content
3. You may redistribute the content in its original or changed form

If you agree to the terms:

1. If you redistribute you have to do it under the same terms
2. You may not use the content commercially (eg. printing a book and sell it)
3. If you redistribute the content you have to say who the original author is - In the case of this wiki it's enough to give the originating URL and name the author as DokuWiki Community

For further information about the licenses see

• Frequently Asked Questions about the GNU GPL
• Creative Commons - learn more

- Does DokuWiki have to Run on GNU/Linux?

I really like this wiki, I've seen it used before and want to run it on my server. However, it doesn't mention in the System Requirements section what OS you're supposed to run on your server. I don't run Linux, I run a windows 2k server with Apache, PHP, MySql etc. Can I run this wiki at all on my windows machine? I just noticed you mention permissions being set with chmod which doesn't exist in windows, so I started wondering if I could run it at all.

It runs under Apache and PHP - I'm running it on a Windows 2000 Server, Windows 2000 Professional and Windows XP Professional machines with no problems so far. The permissions are set differently via the Security tab but the functionality is the same. Other Webservers supporting PHP are reported to work, too, specifically including Microsoft IIS..

I'm running a DokuWiki on IIS on our intranet. It appears to work just fine so far. You need to have PHP installed, give the IUSR user write rights if you are to have anonymous access (if I was hosting this on the Internet I'd take some time working out which files/folders need 'write' access and limit the write rights to just those), make sure the 'attic', 'cache', 'locks', 'media' folders exist in the root 'data' folder, and create a change.log file in the 'data' folder. You also have to give the IUSR user 'modify' rights if they are to delete pages.

I'm running DokuWiki under Mac OS X Server, with full user and group authentication via Open Directory working out of the box. Just follow the normal install instructions, and have a look at the example I put in for LDAP authentication

　私はあまりにたくさんの電子メールを受けとりますので、わたしへの質問メールは最後の手段にしてください。その代わりとして、最初にwiki、bugtracker、メーリングリストアーカイブを捜して過去に同じような問題がないか探してみてください。もし、そこで解決方法が見つからなければ、メーリングリストに参加して、そこで質問をしてみてください。ほかにも、フォーラムやircチャットチャンネルを使うこともできます。

　法人で使う場合は、業務としてのサポートが必要になるかもしれません。そのような場合は、私の働く会社を通じてサポートを提供できます。DokuWikiサポートページを見るか、dokuwiki [at] cosmocode [dot] deにメールを送るか、+49 30 28096200に電話してください。

- How do I get Support?

I do get too much emails so please mail me only as your last resort. Instead try to solve your problem by searching the wiki, the bugtracker and the mailinglist archive first. If you don't find a solution for your problem subscribe to the mailinglist and ask your question there or use the forum or join the irc chat channel.

Companies might be interested in commercial support. Such support is available through the company I work for. Visit the DokuWiki Support page, send a mail to dokuwiki [at] cosmocode [dot] de or just give us a call at +49 30 28096200.

変更や新しいバージョンのロードマップみたいなものを公開してくれるとうれしいんですけどね。

私はいつもDokuWikiの改良をしているわけではありません(みなさんと同じように私にも生活があります)。だから、次のリリースの準備がいつ整うのか予想することは、私にとっても難しいことです。私は、いつも新しい機能を完全に追加できたときや、以前のリリースから全ての重要なバグを解消できた時に新しいリリースを出しています。もし、あたながリリース前のより新しいバージョンを試したいのであれば、Darcsリポジトリから取ってくるか、デイリースナップショットの１つをダウンロードしてください。 — Andreas Gohr 04.02.2005 18:10

- When will the next version be released?

It would be great, to publish some kind of Roadmap on changes or news.

I do not work constantly on DokuWiki (I have a life, too) so it's hard for me to estimate when the next release will be ready. I usually do a new release when I completed adding new features and fixed all major bugs from the last release. If you are eager to try a newer version before it is released, fetch it from the Darcs repository or download one of the daily snapshots. — Andreas Gohr 04.02.2005 18:10

　DokuWikiは、UTF-8（Unicodeの代表的な符号化方法の１つ）を使います。この符号化方法が文書のmetaヘッダで送られて、編集画面ではaccept-encodingして使われています。DokuWiki自体はブラウザーによって送られるデータを再エンコードしないので、ブラウザーがaccept-encodingを無視すると、問題がでるかもしれません - しかし、全てのよく知られたブラウザーの最新バージョンでは、しっかりUTF-8に対応しています…

- How are charsets handled?

DokuWiki uses UTF8 (an Unicode representation). This encoding is sent in the documents meta headers and used as accept-encoding in the edit form. DokuWiki itself does no reencoding of data sent by the browser, so if the browser ignores the accept-encoding of the form there may be problems - however all known modern browsers do work just fine with UTF8…

　そうすることはできます。しかし、そうしない理由があります。DokuWikiは、全ての種類の文書データを管理するように設計されています。あなたの管理するデータベースやWebサーバーがダウンし、このWebサーバーやデータベースを通じてしか文書データを取り出せないとしたらどうでしょう？　ゲェ！　そういうわけで、あなたの最愛のサーバーに残されたものがテープバックアップだけだったとしても、DokuWikiは完全な情報をいつでも読めるプレーンテキストとして保管してあるのです。

http://www.pmwiki.org/wiki/PmWiki/FlatFileAdvantagesは、２万レコードまでのwikiデータについて、データベースよりフラットファイルが優れている点について解説しています。

- How about using a DB?

It would be possible, but there was a reason for not doing it. DokuWiki was designed to hold documentation of all kinds. So what do you do when your database or your webserver is down and the documentation to bring it up again is only accessible through this webserver or database? Yikes! So DokuWiki stores all this vital information as plain text which is always readable, even if you only have some tape backups left of your beloved Server .

http://www.pmwiki.org/wiki/PmWiki/FlatFileAdvantages talks about why flatfiles are better than databases for wikis of up to about 20,000 records.

この素晴らしいフッターボタンは、どこで手に入りますか？ 自分専用のものはどうやって作りますか？

このようなボタンはAntipixelのblogのポストで創られました。ネット上には、再利用できる より 多くの ボタン があります。そして、Webインターフェイスから独自のボタンは、ここ や ここ や ここ で作ることができます。

- Footer buttons

Where are those nice footer buttons from? How can I create my own ones?

These kind of buttons originated at this Antipixel blog post. There are many resources of more buttons available on the net. And you can create your own using a webinterface like this, this or that.

- Installation & Configuration

- Cannot send session cookie

I edited the config file and now I'm getting errors like this

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/codecrai/public_html/wiki/conf/dokuwiki.php:81) in /home/codecrai/public_html/wiki/inc/common.php on line 22

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/codecrai/public_html/wiki/conf/dokuwiki.php:81) in /home/codecrai/public_html/wiki/inc/common.php on line 22

Warning: Cannot modify header information - headers already sent by (output started at /home/codecrai/public_html/wiki/conf/dokuwiki.php:81) in /home/codecrai/public_html/wiki/doku.php on line 123

This happens when your editor adds a newline after the closing ?> php tag. This starts the output and PHP can't send cookies and other headers anymore. To fix it simply remove the newline or the whole closing tag. Also make sure you have no leading whitespace before the starting <?php tag.

A similar problem can occur when non-ASCII is used in the config file and your editor saves the file in UTF-8 using a Byte Order Mark. Certain Windows software (eg. Notepad) is known to do this. The solution is to save the file using software which doesn't save this mark or allows you to omit it. The freeware program Notepad2 does this correctly when using Encoding→UTF-8.

This error is also displayed when another error occurs first and PHP starts the output by printing the error message. If you get any other error before the “cannot send session cookie” message, you need to fix that one first.

最大ファイルアップロードサイズ(現在2Mバイト)を増やす簡単な方法はありますか?

ファイルのアップロードサイズは、PHPの設定で制限されています。php.ini内のupload_max_filesizeパラメーターに記述されています。インストールしたディレクトリにある.htaccessというファイルに次の2つの行を追加しても増やすことができます。

php_value upload_max_filesize 15M
php_value post_max_size 15M

- Maximum Upload File Size

Is there an easy way to increase the maximum file upload size (currently 2 megabytes)?

The file upload size is limited in your PHP configuration php.ini with the parameter upload_max_filesize. or append the following two lines to .htaccess in the installed directory:

php_value upload_max_filesize 15M
php_value post_max_size 15M

Note: Red Hat ES users will also want to check (and probably increase) LimitRequestBody in /etc/httpd/conf.d/php.conf, which is set by default to a fairly low value. This directive specifies the number of bytes from 0 (meaning unlimited) to 2147483647 (2GB) that are allowed in a request body.

- Missing utf8-decode

I get an error for the utf8-decode function being unknown.

On some systems (Mandriva, formerly Mandrake) you need to install an additional PHP package called php-xml

- session_start() errors

What do errors like these mean:

session_start(): PrivoxyWindowOpen(/tmp/sess_be09512603dfe7ca99751ee0ded7fbad, O_RDWR) failed: Permission denied (13)

Fatal error: session_start(): Failed to initialize storage module: user (path: /tmp)

This means your PHP install isn't configured correctly. PHP can't create the session datafiles. Contact your admin or read the PHP docs to setup session handling correctly.

I was getting this error message as well. It was a PHP configuration problem as described above. I fixed the problem by editing the php.ini file and setting this directive to a directory that existed… it had previously been /tmp by default (expecting to be hosted on a *nix server. So if you are running php on Windows you have to change it, just keep the / instead of using the windows \.

session.save_path = c:/temp

- DokuWiki on Sourceforge?

I'm trying to get DokuWiki running on sourceforge.net but whatever I try it doesn't work.

Sourceforge changed its webserver configuration to mount project directories readonly. This means the webserver can't write to the project directories regardless of the set permissions. Unfortunately this makes it nearly impossible to run DokuWiki on sourceforge's webservers. I recommend to set up your wiki on a different host and link your sourceforge project website to this other host. The following free hosters provide similar services to sourceforge's and should be able to run DokuWiki without problems: developer.berlios.de, dotsrc.org.

However, Johannes Schaback managed to install DokuWiki on SF although it is not recommonded because one have to place all data files in public space where everyone can tamper with it! This is a big security issue. Basically, one move all folders that require write access to /tmp/persistent/YourProjectName which will be mountend with write access by the webserver. A more detailed description what you got to do follows. It is assumed that your project is called FengGUI (unix name fenggui). You need to replace FengGUI with your own project name.

1. log on SF via SSH
2. change to the htdocs directory in your project directory ($>cd /home/groups/f/fe/fenggui/htdocs)
3. extract the DokuWiki tar in /home/groups/f/fe/fenggui/htdocs ($>tar -xzvf dokuwiki-rc2006-09-28.tgz)
4. rename the directory dokuwiki-rc2006-09-28 to dokuwiki ($>mv dokuwiki-rc2006-09-28 ./htdocs/dokuwiki)
5. move the directory /home/groups/f/fe/fenggui/htdocs/dokuwiki/data to /tmp/persistent/fenggui/ ($>mv /home/groups/f/fe/fenggui/htdocs/dokuwiki/data /tmp/persistent/fenggui/)
6. move the directory /home/groups/f/fe/fenggui/htdocs/dokuwiki/conf to /tmp/persistent/fenggui/ ($>mv /home/groups/f/fe/fenggui/htdocs/dokuwiki/conf /tmp/persistent/fenggui/)
7. create symbolic links to the two moved folders such that DokuWiki can access the folders without noticing that they are located in a completely different branch in the file system. Change back to the dokuwiki directory ($>cd /home/groups/f/fe/fenggui/htdocs/dokuwiki). Then create symbolic links to the data and the conf directory (ln -s /tmp/persistent/fenggui/conf and ln -s /tmp/persistent/fenggui/data)
8. make the moved stuff world-writable ($>chmod -R 777 /tmp/persistent/fenggui)

This should do the trick. You may want to execute install.php that comes with the nice feature to check the permissions of all necessary folders. Don't forget to backup the data and conf directory constantly.

- DokuWiki on free.fr?

I try to set up DokuWiki on an account at the very popular french provider free.fr, but I get all kinds of errors.

free.fr cripples their PHP configuration beyond anything that can be supported by DokuWiki. DokuWiki will not run on free.fr (if it does for someone it's just pure luck). Please do not report any bugs regarding running DokuWiki on free.fr before making sure that they still exist when using a different provider.

Running (very) good (2006/10/13) with last RC2.

Running without fatal errors, when I create a folder sessions at the root of the server, with 6/11/06 Version, but have some warnings when I try to change config. parameters via the wiki.

When loading DokuWiki, I'm getting an Error 500 (Internal Server Error), what should I do?

This can happen if the htaccess files in your DokuWiki directory use settings or trigger actions which are not supported by your Apache server config. If you're not running the server yourself, but are registered with a webhost, you can either ask your webhost to enable the options in question, or just comment them out in the htaccess files.

The options which are known to cause an Error 500 are:

Options -Indexes

as well as all settings related to Apache's mod_rewrite option to pretty-print URLs. The latter are disabled by default.

I also saw this problem with my hosting company because I had the PHP scripts and directories set with access permissions of 777 everywhere. That's what I'd needed on a previous site, but the new one gave me 500 internal server error until I set the .php files to permissions 644 and the dokuwiki directories to 755.

DokuWikiを使っていると、時々”Writing xyz failed(xyzの書き込みに失敗)“というエラーが表示されます。どうしたらいいのでしょうか？

最も可能性があるのが、PHP's Safe Modeが有効になっているウェブサーバーを使っているということでしょう。残念ながら、ウェブからのディレクトリへの書き込みができません。なぜならすべてのアクションはウェブユーザーのユーザーIDで行われているからです。しかし、FTPユーザーはウェブスペースのディレクトリへの書き込みが許可されています。

この問題の解決には2つの方法があります：

1. DokuWikiのページが存在するサーバーにFTPでログインし、手動で問題となっているフォルダを作成してしまう。所有者は、自動でFTPユーザーになっているので、パーミッションを777にするのを忘れずに。

2. safemode hackとして知られるDokuWikiに内蔵される機能を使う。

- Error writing files and directories

While using DokuWiki, I'm often getting errors reading: “Writing xyz failed”. How come?

Most probably, you're with a webhost which has enabled PHP's Safe Mode. Unfortunately, this keeps DokuWiki from writing to directories using the web interface, because all actions are triggered with the user ID of the wwwuser, but only the FTP user is allowed to write to the directories on your webspace.

There are two solutions to this problem:

1. Log in over FTP to the server where your DokuWiki pages reside and create the folders in question manually. They will automatically be owned by the correct user (the FTP user). Don't forget to chmod them to 777.

2. Use DokuWiki's built-in workaround known as the safemode hack.

An error like this occurred to me when my dokuwiki was updated by apt. It used my old config file which used umask for creating files and directories in stead of a creation mode — Bert Hekman 2006/08/08

アクセスコントロールが無効になっているのでしょう。設定でユーザーアクセスコントロールを有効にして、users.auth.phpとacl.auth.phpが存在するかを確認しましょう。

- Why is there no login button?

ACL is disabled, please enable “useacl” in the configuration, and make sure users.auth.php and acl.auth.php exist.

- Error sending password email

When I try to create a user for the first time, why do I see this error?

Looks like there was an error on sending the password mail. Please contact the admin!

When using Dokuwiki's ACL feature, it uses PHP's email() function to send the password email. You will get this error when that call fails. This usually means the 'sendmail' command is not available, and you need to install sendmail or some other MTA which mimics the sendmail command. See also PHP's mail() docs: http://www.php.net/mail

OK, I fixed that, now I get:

Sorry, a user with this login already exists.

Even though it failed to send the password email the first time around, it still created the user account. The easy way to fix this is to simply remove the user from the users.auth.php file, then you can try to register again.

- Usage

ユーザーを他のページに自動的に移動させるようなWikiページを作成する方法がありますか？

GOTO プラグインについて調べてみましょう。 — Allen Ormond 2006-06-30 23:11

- How to make a redirect page?

Is there a way to create a wiki page that automatically brings the user to another page?

Check out the GOTO plugin. — Allen Ormond 2006-06-30 23:11

- How to add pages?

In DokuWiki pages are created as in every other wiki. Simply create a link to a non existing page, follow this link, and click on Create this page. This is the most common and recommended way. It ensures all your pages are linked together correctly and you don't create orphans anywhere.

There are some alternative ways as well:

• You may enter the name of new page directly in the search field, and click the “Search” button and can choose Create this page on the results page. The new page will be named after your query.
• You can copy a .txt file to the directory (namespace) wherein you want it to reside.
• Of course you can also open an non-existing page by manually manipulating the URL in your Browser
• There is also a plugin to add a page creation interface called addnewpage

Make sure you properly link your newly created page from other pages, when using one of the alternative methods

- Keeping newlines as is?

Can I display the newline without using the magical '\\'? I find that when dokuwiki parses my document it eats up all my newlines, but I want the newlines displayed just as what I inputed.

If you want a new paragraph just add a blank line. Preformatted text is possible with <file> and <code> tags. A mode which preserves newlines but applies other formatting is not available currently. As a side effect this encourages the users to create more structured texts, creating paragraphs for logical blocks.

Adding a blank line is to easy. That does not work for me in a listitem. I would like one bullet point with two paragraph in it. How to do that? –jroeterd.

Note: such a mode should be available, see implementation sample in 'nonewline mode' – Daniel Chaffiol 02/06/2005

Try the linebreak plugin — Christopher Smith 2006-05-25 22:00

それには２つの方法があります：

1. そのページに相当するサーバー上のファイルから書き込み権限をなくします。例:

   chmod 644 file.txt

2. ACLの機能を使います。

- How can I make some pages non-writable?

There are two ways:

1. Just remove the write permissions for the webserver on that particular file. eg:

   chmod 644 file.txt

2. Use the ACL feature

- HTML does not work

I have changed the dokuwiki.php file to allow HTML code:

 $conf['htmlok']      = 1;

Read the syntax page again: You can embed raw HTML code into your documents by using the html tags. So to embed HTML you need to enclose the HTML with <html></html>.

However, remember that the <html> is case sensitive; <HTML> will just display the HTML text source code.

- Deleting or Renaming Pages

Is there a way to delete or rename a page through DokuWiki?

Renaming would possibly break a lot of links linking to the old page, but Dokuwiki doesn't know which pages link where to so this could be handled. A better way to rename a page is to create the new one and then change the content of the old page to something like this:

moved to [[newpage]]

Pages are deleted automatically when the whole page is cleared (the attic remains).

Does renaming/moving the txt file in the file system to bad things other than breaking links? Does the history move with the moved file? – Zugschlus, 2005-08-11

The history does not get moved with the main file. The history is associated with the filename, not the file itself. — ta' lajzar 2005-08-11 16:37

- Deleting media files

Is there a way to delete orphaned image (media) data?

This feature is available only when ACLs are enabled. You can assign the DELETE permission to users allowed to delete Mediafiles. They then can use the delete button in the media popup.

- How Do You Upload Files?

I don't see where a user can simply upload a file to a page. How does one do this, and how does it get set up?

If you have permission to upload files (see ACL) you can use the add images button to upload files (when you are editing the page). Only certain filetypes are allowed to be uploaded. This is configured through the mime.conf file.

Please note, normal users are not allowed to upload here on wiki.splitbrain.org.

- Don't cache external images?

I created a link to an external image which is updated every five minutes. I don't want DokuWiki to cache that image at all, but link directly to the image source. How can this be accomplished?

See images — Andreas Gohr 2005-02-17 18:19

http://youdomain/yourwiki/doku.php?do=check

たとえば、このサイトでは、ここを見てください http://wiki.splitbrain.org/doku.php?do=check

- How do I display Version Information?

http://youdomain/yourwiki/doku.php?do=check

For example, to check this site, visit http://wiki.splitbrain.org/doku.php?do=check

- Add pages to a system of static pages?

I know there is a script out there, but i cannot use it.

セクション毎に編集ボタンを表示するにはどうしたらいいですか？

編集ボタンは、ヘッドラインセクション毎にその最後に表示されます。もし、表示されないのであれば、以下を確認してください:

• local.phpで定義されているmaxseclevelは、だいたい3～5の範囲です。あなたの希望するセクションの数を決めて編集してください。
• そのページは、セクションの編集で苦労しているACLで許可されたユーザーによって編集中になっています。
• また、そのページはサーバー上のファイルが直接編集中なのかもしれません。

— Terence J. Grant 2006-04-18 08:40

- How do I get Edit buttons to appear for section editing a page?

How do I get Edit buttons to appear for section editing a page?

They appear at the end of each “headline” section. If they're not appearing then check that:

• maxseclevel in local.php is something like 3, 4, or 5, depending on how deep you want section editing.
• your pages are modifiable (ACL) by the users who are having trouble with section editing.
• and that the pages are not read only on the server.

— Terence J. Grant 2006-04-18 08:40

- How do I change /doku.php?id=wiki to /wiki ?

Sorry I've spent a good hour looking around for the answer to this with no luck so I figured it was about time to ask. I would like to know how is it possible to change the default “wiki/doku.php?id=projects” to simply “wiki/projects.” I know it can be done and I'm sure the answer is easy but it is kind of hard to find it, not many narrowing keywords.



here is an example of what I want:

http://wiki.ps2dev.org/

http://wiki.ps2dev.org/psp:software_projects



Thanks in advance

You need to use the “rewrite engine”; it requires that:

• your server supports it(most apache servers appear to do so by default)
• make sure your config file enables rewrite
• and of course make sure your .htaccess file is modified correctly

See also:

• http://wiki.splitbrain.org/wiki:tips:modrewrite
• http://wiki.splitbrain.org/wiki:config

— Terence J. Grant 2006-04-18 08:36

english version: 2006-11-08 01:59 by chi.

Add your email here if you created translated or modified whole or part of this page.

このページを作成・変更した方は、次にメールアドレスを追記してください。

• kinneko
• initial-t