Discussion Plugin

The Discussion Plugin adds a discussion section after your wiki page for user comments. This is useful to separate page content and the discussion thereof and also, if you don't want to give normal users the right to edit the page but still want user contributed notes. A second component of this plugin shows a list of all pages in a namespace with a discussion section (called discussion threads) ordered by most recent comments. This allows you to create a very simple discussion forum in your wiki.

~~DISCUSSION~~
~~DISCUSSION:off~~
~~DISCUSSION:closed~~
~~DISCUSSION|Custom Title String~~
~~DISCUSSION:closed|Custom Title String~~

This is the main part of the plugin. By including the ~~DISCUSSION~~ instruction in your wiki page, a discussion section will be appended after the normal wiki page content. To turn it off again, use ~~DISCUSSION:off~~. If you want to show the existing discussion but don't want to allow new comments / replies, use ~~DISCUSSION:closed~~. A custom title can be appended after the separator |.

After each comment there may be up to three buttons (depending on your rights):

• Edit: Registered users can edit their comments; admins can edit all comments. To remove a comment, just edit it, clear the text and save the empty comment – like you would do with a wiki page. Attention: If there are replies to a comment, removing it will also remove all replies!
• Reply: To reply to a comment (vs. commenting on the wiki page content), click the Reply button. The comment entry form will then be placed accordingly.
• Hide / Show: Admins can deactivate and reactivate comments easily by this button. Hidden comments aren't shown to normal users and are displayed dimmed to admins.

Of course, the whole DokuWiki syntax can be used in comments as well. But there are problems with headers and footnotes as they may produce conflicting IDs and thus invalid XHTML. I'm looking for a way to either allow only a subset of the wiki syntax or automatically create unique IDs.

{{threads>[namespace]&[flags]}}

This displays a list of all pages of the given namespace with a discussion section. The list is sorted by the most recent comment.

The plugin can be configured using DokuWiki's configuration manager available in the admin menu.

You can try this plugin using the live demo. (link broken)

Please report bugs or feature requests at the Bug tracker.

• Git Repository
• Bug Tracker

• Edited script.js via GitHub (2011/07/10 22:39)
• Merge pull request #55 from lupo49/master (2011/06/29 19:23)
• new configuration option which enables a button for toggling the visibility of the discussion section (2011/06/29 19:20)
• Merge github.com:lupo49/plugin-discussion into lupo49-master (2011/06/27 19:04)
• Divided mail notify function (admin notify / page subscribers) - Closes #54 (2011/06/27 19:03)
• Divided mail notify function (admin notify / page subscribers) - Closes 54 (2011/06/27 18:57)
• Fix compatibility with the changed indexer in DokuWiki Rincewind (2011/06/26 14:06)
• Merge pull request #51 from yusuke006/master (2011/06/12 11:41)

I have DokuWiki formatting allowed in comments. I also have a LaTeX plugin. <math>\sum_x{x+5}</math> is not rendered within a discussion.

The plugin has built-in support for the CAPTCHA plugin. Additionally, one might also consider to use the Bad Behavior plugin.

You're probably not running the latest version of the plugin. Try to update to the latest version first.

Yes, use the newestfirst option.

If you enable the notify option admins are notified for all comments.

The comments are saved in special meta files inside the <dokuwiki>/data/meta directory. Each page which has a discussion has a corresponding pagename.comments file.

You can change the size of the box by using the following CSS class:

div.dokuwiki div.comment_wrapper {}

Because it would break DokuWiki's revisions system.

Alternative: use the pagelist plugin to make an overview of “latest discussion” by using the {{thread>...}} syntax.

This is a know problem with the sidebar plugin which needs to be fixed by it's author. If you're looking for working alternatives in the meanwhile I suggest to have a look at the sidebarng plugin.

You can list all discussions with:

{{threads>*}}

Discussions aren't stored like regular wiki pages. This will not work.

This is possible using the feed plugin, please see there how it works.

The plugin disables subscription for logged-in users when the option “subscribers” ($conf['subscribers']) is activated in the configuration.

When you submit a discussion post, you may get the following error:

Call to undefined function send_redirect()

This is because you're running an older version of dokuwiki that does not support the send_redirect() function. There are a few options to remedy this.

1. Upgrade to a later version of DokuWiki
2. Pull the send_redirect() function from the source code of a later version dokuwiki and put it in lib/plugins/discussion/action.php or in inc/common.php
3. Edit lib/plugins/discussion/action.php file and comment out the call to send_redirect() (around line 306), replacing it with something like this:

print "<html><head><meta http-equiv=\"refresh\" content=\"0,url=$url\"></head><body>Redirecting to <a href=\"$url\">$url</a></body></html>";

Newest development version of the plugin (since pull-request 34) should not have that problem with 2008-05-05 anymore, but not all current features may work with 2008-05-05 (preview and subscription for example).

After upgrading to “Anteater” the discussion-plugin doesn't work in my DW too. The url of the discussion-plugin has changed. Now, I installed the plugin from this url: Discussion-Plugin and it works fine again. :) (I got help on IRC #dokuwiki) — leolein 2010/11/20 19:40

Change the following line (#249) in action.php

$comment['user']['id'] = 'test'.hsc($_REQUEST['user']);

to

$comment['user']['id'] = 'Guest';

I've solved this by changing in syntax/comments.php

if ($match == ':off') $status = 0;
else if ($match == ':closed') $status = 2;
else $status = 1;

Into

if ($match == ':open') $status = 1;
else if ($match == ':closed') $status = 2;
else $status = 0;

Please refer to the discussion page.