GithubHelp home page GithubHelp logo

dokufreaks / plugin-discussion Goto Github PK

View Code? Open in Web Editor NEW
35.0 35.0 26.0 607 KB

Add a comments section to DokuWiki pages

Home Page: https://www.dokuwiki.org/plugin:discussion

License: GNU General Public License v2.0

PHP 97.39% CSS 1.46% JavaScript 1.15%

plugin-discussion's People

Contributors

alexgearbox avatar araname avatar brilanto avatar dturkalj avatar foosel avatar jacobpalm avatar jfmd21 avatar jzombi avatar klap-in avatar larsgit223 avatar lpaulsen93 avatar magenbrot avatar matze1224 avatar michitux avatar mijndert avatar moisesbr-dw avatar mprins avatar nfriedli avatar petsagouris avatar planev avatar samo079 avatar sawachan avatar schplurtz avatar semotta avatar splitbrain avatar tiborepcek avatar tictactoe101 avatar xesarni avatar xtaran avatar y-ishida avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

plugin-discussion's Issues

(re)captcha not working

I had 'discussion' working with 'captcha'. It worked as expected: unless you entered the correct captcha, the comment wouldn't be added. Then sometime last week, after upgrading everything to the latest versions, 'discussion+captcha' no longer worked. The 'captcha' didn't appear at all, and comments were entered freely. I assumed since the comments were being added, something was wrong with 'captcha'. I installed 'recaptcha'. I attempted to add a comment and this time the 'recaptcha' dialog was listed. Unfortunately, comments were still allowed, even without typing anything into the 'recaptcha' box. I've uninstalled and reinstalled 'discussion' and 'recaptcha' and completely removed 'captcha'... still allowing spam comments.

Help? What other information would be useful for you to get a better idea of what's going on? Feel free to play with the comments on my blog to get a feel for what I'm experiencing: www.dustingooding.com

[solved] multiple warnings

Discussion plugin works with errors, after upgrade to dokuwiki-2010-11-07 and discussion 2010-11-16.

After save comments, I have this warnings:
Warning: Illegal offset type in isset or empty in /home/www/z111967/htdocs/inc/auth/plain.class.php on line 75

Warning: md5() expects parameter 1 to be string, array given in /home/www/z111967/htdocs/lib/plugins/avatar/helper.php on line 75

Warning: preg_match() expects parameter 2 to be string, array given in /home/www/z111967/htdocs/inc/EmailAddressValidator.php on line 19

Warning: strrpos() expects parameter 1 to be string, array given in /home/www/z111967/htdocs/inc/EmailAddressValidator.php on line 24

You can see it here http://freenaswiki.ru/doku.php/blog:dostupna_beta-versija_freenas_8

It happens on commercial hosting and on my local web server with lighttpd 1.4.23 and PHP 5.2.8

Sorry. Solved by upgrade gravatar plugin.

E-Mail Notification: One subscribers name is shown in the mail "to:"-field

Current situation: Dokuwiki-Site with discussion area enabled and multiple subscribers for one page.

If one of our user writes a new comment, new mail is generated and notificates all subscribers. Theres one disastrous information (for our company) in the mail. The plugin generates mails with "to:"-field filled with one of the subscribers name in the mail body. So that other people see who is subscribes to this page.

Would be nice if you can fix it in that way, as dokuwiki mailer is doing it (without values in the "to:"-field).

Regards
Matthias Schulte

Subscribe to all discussions

One feature I'm missing here is allowing the user to subscribe to all discussion threads. Because discussion threads are not created as pages, it is not possible to allow a user to receive a notification of any changes in the discussion threads by subscribing to changes in the namespace. Is this something that is easy to add to the plugin?

strikethrough doesn't work

if you mark text with "del" (as strikethrough), the signs < and > of the html-tag will be transformed to entities, so the tags have no effect and will be displayed as normal text.

server error after submission

If I write a new entry in the discussion field and save it, the following server error occurs: “The server encountered an internal error or misconfiguration and was unable to complete your request. Your administrator may not have enabled CGI access for this directory.”

The error log on the server says:
File does not exist: /home/.sites/3/site536/web/libImage, referer: http://www.mydomain.at/wiki/doku.php

Does anybody have an idea what's wrong?
I use dokuwiki anteater and the discussion plugin from 2010-11-16

Discussion Plugin and Anteater

Mails are no longer sent out to subscribed users when a new discussion entry is created since upgrading to Anteater. My config is with Swiftmail on an AD backend. Is this a known issue?

Email notification is broken

I'm using the discussion plugin with current stable dokuwiki. Installed via plugin manager by means of https://github.com/dokufreaks/plugin-discussion/tarball/master

I have subscriptions turned on, and use Swiftmailer for sending mails. Swiftmailer is configured okay (tested just now by sending myself an email via password change)

However, when adding a comment I get the following

SwiftMailer log:

++ Log level changed to 4
++ Forcing ESMTP mode. HELO is EHLO.
++ Forcing ESMTP mode. HELO is EHLO.
++ Trying to connect...
++ Trying to connect to SMTP server at 'tls://199.195.157.117:465
<< 220 mail.bla-bla.org ESMTP Postfix (Ubuntu)

EHLO [199.195.157.183]
<< 250-mail.tenebrix.org
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-AUTH PLAIN
250-AUTH=PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
++ SMTP extension 'PIPELINING' reported with attributes [].
++ SMTP extension 'SIZE' reported with attributes [10240000].
++ SMTP extension 'VRFY' reported with attributes [].
++ SMTP extension 'ETRN' reported with attributes [].
++ SMTP extension 'AUTH' reported with attributes [PLAIN].
++ SMTP extension 'AUTH' reported with attributes [PLAIN].
++ SMTP extension 'ENHANCEDSTATUSCODES' reported with attributes [].
++ SMTP extension '8BITMIME' reported with attributes [].
++ SMTP extension 'DSN' reported with attributes [].
++ Trying to authenticate with username 'tbxwiki-noreply'.
++ No authenticators loaded; looking for defaults.
++ Authentication mechanism 'PLAIN' attached.
++ Authentication mechanism 'LOGIN' attached.
++ Authentication mechanism 'CRAM-MD5' attached.
++ Trying 'PLAIN' authentication...
AUTH PLAIN ***
<< 235 2.7.0 Authentication successful
++ Success! Authentication accepted.

And then... nothing happens. The mail never arrives.

The only other clue seems to be in syslog of mail server, which says"

Aug 11 05:52:21 mail postfix/smtps/smtpd[6437]: lost connection after AUTH from unknown[199.195.157.183]

Aug 11 05:52:21 mail postfix/smtps/smtpd[6437]: disconnect from unknown[199.195.157.183]

And that's it. Not a single more clue.

Would you please kindly advise on how to fix it ?

P.S.: something similar happened here: http://irc.dokuwiki.org/?d=2010-12-09
But it has been very long ago and apparently is fixed.

Warm regards,
Lolcust.

Old versions of a page can enable/disable comments

Whenever an old version of a page that contains some discussion syntax is parsed the .comments file is updated with that status. This is caused by 2eddb74. I think the discussion plugin should store it's status in a metadata property that is rendered in the renderer of the syntax plugin as then there are also no longer problems that after removing the metadata syntax from a page the .comments file still exists and thus comments are still enabled. As a quick fix one could move the writing of the .comments file in the render() function and write only when metadata is rendered, but I don't know if that would have any negative side effects.

[feature request] Archive Stale Threads

Hi,

I really love the Discussion plugin, but once the discussion gets long it is hard to navigate.

Is it possible to have stale threads (say threads that have been inactive for more than a certain period of time) moved to an archive section that is accessible by a link?

Thanks!

Google Reader/SideWiki integration

coComment integration is good but increasing integration level with multiple blogging engines is better. Please add Google integration!

[Feature request] Hidden discussion

This is the opposite of a closed discussion - existing comments not displayed but users able to add new ones (with comments displayed to members of a group that I can configure). The idea being that a page can gather feedback without all users seeing it. I can probably code both this and my other request, with a bit of help on where to start.

Plugin Disabled After Update, 2010

hi,
when I ever write some comment and submit it, I just get directed to a blank page.

Comment box does no longer show after I add DISCUSSION , while existing boxes and comments still there but I can not submit any new comment. I get a blank page.

I found this error in my php:

[Wed Sep 22 07:21:48 2010] [error] [client 192.168.0.101] PHP Fatal error: Call to undefined function subscriber_addresslist() in /var/www/html/dokutest/wiki/lib/plugins/discussion/action.php on line 1097, referer: http://192.168.0.175/dokutest/wiki/doku.php?id=%D8%A7%D8%AC%D8%AA%D9%85%D8%A7%D8%B9_20_09_2010

[feature request] allow for customisation of discussion form

I am using this plugin for a wiki for a small group of players and love the possibility of having users leave comments easily.

However, currently the comment area is rather large - please allow for some customisation to make it more unobstrusive (i.e. reduce textarea size, remove wysiwyg editor, make everything collapsible, etc.).

That'd be great! :-)

Folded plugin doesn't retain paragraph spacing - instead it renders all text on a single line.

I'm using DokuWiki release rc2011-05-08 "Rincewind RC2" with the latest version of this plugin (as of 5-17-11).

The folded plugin doesn't retain paragraph spacing - instead it renders all text onto a single line.

Tables and bulleted lists do retain formatting, the problem however is when using just regular text.

If I simply add an additional carriage return after each line of text, the folded plugin puts everything on a single line of text.

For example:
++++ my title |

pargraph 1 text

paragraph 2 text

paragraph 3 text

++++

Renders as:
my title>
paragraph 1 paragraph 2 paragraph 3

As mentioned , if I enter two backslashes at the end of each line of text, it no longer wraps the text on a single line. Instead it forces a line break but there isn't the additional carriage return between paragraphs as normal formatting allows in DokuWiki.

For example:
++++ my title |

pargraph 1 text (two backslashes here)

paragraph 2 text (two backslashes here)

paragraph 3 text (two backslashes here)

++++

Renders as:
my title>
paragraph 1
paragraph 2
paragraph 3

Note: I had to type out "two backslashes" in parentheses above because github won't render them in the comments.
See: http://www.dokuwiki.org/syntax#basic_text_formatting

Locked links with IE, dokuwiki 2009-12-25 and discussion

With Internet Explorer 8, dokuwiki 2009-12-25 and the discussion plug-in no link is clickable anymore. They are marked as links but behave as normal text. With the former dokuwiki version or with Firefox or with deactivated discussion plug-in everything is working.

Just now I can only deactivate the plug-in to ensure proper wiki usage for all users.

runaway comments

sorry if this is a repeat, I cannot see the other issue entry.

Latest dokuwiki, latest plugin; works on my laptop; identical installation on the server gives
hundreds of duplicate comments every time someone tries to add a comment.

Help please ... I'm going to have to disable it otherwise. \

~~NODISCUSSION:off~~ doesn't work with automatic

Hi,
Thanks for this great plugin. However, I can't stop discussion in pages. I use the option automatic in local.php :
$conf['plugin']['discussion']['automatic'] = 1;
So actually we have three cases :

  • no automatic, discussion needed
  • automatic, all pages
  • automatic, nodiscussion usefull

So, these third case is not expected ? Probably easy to modify ?

Thanks,
Thibaud.

Unintended duplicate class names

I just ran into a world of trouble because the "Preview" button and the preview container itself both share the class "comment_preview" and I wanted to apply different CSS styles to each one.

It's in line 889:

<input class="button comment_preview" ... >

I suggest it should be changed to something like:

<input class="button comment_preview_button" ... >

Email (non-) error on discussion.

With Rincewind, Discussion dated 2009-08-22, pagelist dated 2010-01-07.
If a user is subscribed to changes for a page,
changes to the main text of a page result in an email being sent correctly.
changes to the discussion result in no email and an error message (swiftmail is configured to print a full error log).

Conflicts with plugin:lightboxv2

When I installed [https://github.com/downloads/glensc/dokuwiki-plugin-lightboxv2/lightbox-20120103.zip](lightbox plugin) , CAPTCHA cannt display, why?

Toggle Printing

Feature request: I would greatly appreciate a function to switch of printing the discussion.

multiple comments

using the 2009 stable release. Adding a comment adds the same comment more than 200 times.

[feature request] Breaking long discussion in several pages.

When discussion becomes very long (hundreds of comments) page become very long. It's possible to add for such discussions additional navigation like this:
comments < page 1, 2, 3, all comments in one page >
And add option how many comments may be on one page, and show only desired part of discussion.

edit.js causes javascript error with dokuwiki 2009-12-25c

Line 155 of action.php says:

array_unshift($event->data['script'], array('type' => 'text/javascript', 'charset' => 'utf-8', '_data' => '', 'src' => DOKU_BASE.'lib/scripts/edit.js'));

edit.js contains a bit of code:
//FIXME consolidate somewhere else
addInitEvent(function(){
var field = $('wiki__text');
if(!field) return;
addEvent(field,'keydown',keyHandler);
});

Problem is, line 155 includes the edit.js BEFORE the rest of the dokuwiki js code has loaded:

<script type="text/javascript" charset="utf-8" src="/lib/scripts/edit.js" ></script>
<script type="text/javascript" charset="utf-8" src="/lib/exe/js.php?tseed=1268166351" ></script>

So the function addInitEvent() isn't defined yet, which means edit.js throws a javascript error.

Not clear why line 155 is in dokuwiki, since edit.js is included with the main javascript (js.php), and thus line 155 seems redundant. I commented it out, and everything seemed to work

sort order in moderate discussions (DokuWiki "Angua")

I don't know if this plugin is still maintained. I know it's a complex plugin. Are there any known issues with DokuWiki 2012-01-25 "Angua"? I've upgraded from an ancient DokuWiki installation, replaced all plugins with their latest version and noticed a weird sort order in the "Administrator -> Moderate Discussions" dialog. Can anyone confirm this?

It seems like the files in /data/meta (I assume the discussion plugin uses it) are overriden. Does the discussion plugin list the comments by the timestamps in meta?

[Feature request] Managing comments (moving within thread and between threads)

It would be grate if it's possible to move comments in other place within discussion tread.
Often users add replies to other comments without pressing "Reply", just using general form in the end of discussion tread.

It's possible to fix it manually (move to other parent comment), by editing .meta files. But It's very annoying process.

More over I'd like to move some comments to different discussion tread (when users misplaces comments, to moderate discussion). And this is almost impossible because not only first comment, but all the tree of replies should be moved at the same time.

"Subscribe to comments" disappears

The "Subscribe to comments" box disappears whenever the "Enable page subscription support" is enabled in the "Editing Settings" section of the configuration manager. This allows you to either have subscriptions to pages/namespaces or subscriptions to comments in discussion threads, but not both.

Please implement DokuWiki's internal dformat() function in your plugin

Hi,

I am using the %f syntax with DokuWiki's internal dformat() function to show the relative time of events in Dokuwiki, i.e. 2 mins ago, 4 hours ago, etc, as opposed to a fixed date/time, and because I am also using your plugin (which works great by the way), I would like to be able to use this date/time format in the discussions too. At the moment it is just showing %f for the time. I believe this is because you are using the strftime() function. Would you be able to switch to using DokuWiki's internal dformat() function instead?

Thanks,

Nick

do not show empty and unusable discussion section

if a user is not logged in and is not allowed to add comments, opening an article without comments still displays "discussions" block that contains only heading and background blob.
in such cases, discussion section should not be shown at all

Discussion box showing up even with ~~DISCUSSION:off~~

I've tried to use Discussion plugin with Blog plugin. It works fine, but as soon as I erase the cache, or if it expires by itself, a new comment box is showing in the main blog page (where I added {blog} tag. I tried to add DISCUSSION:off without success.

[Feature request] Anonymous submissions

I want to put together an anonymous feedback system, that would allow members (I plan to put this on a page only members can see) to submit discussion comments with no identifying details. Is that something that would be easy to add to this plugin?

Weak e-mail validation

E-mail is tested only for being not blank and gaving just "@". Try this function:

function validate(form){
if(!form) return;

if (isBlank(form.name.value)){
    form.name.focus();
    form.name.style.backgroundColor = '#fcc';
    return false;
} else {
    form.name.style.backgroundColor = '#fff';
}
p=new RegExp("[a-zA-Z0-9_.]{4,}@[a-zA-Z0-9_.]{4,}[.]{1}[a-zA-Z0-9_.]*");
if (isBlank(form.mail.value) || p.test(form.mail.value) == false){
    form.mail.focus();
    form.mail.style.backgroundColor = '#fcc';
    return false;
} else {
    form.mail.style.backgroundColor = '#fff';
}
if (isBlank(form.text.value)){
    form.text.focus();
    form.text.style.borderColor = '#fcc';
    return false;
}

}

The point is to use simple regexp for validation =)

mailfrom config doesn't accept macros

In DW core ( inc/common:notify() ) it is possible to use macros in the configuration parameter $conf['mailfrom'] - in particular @user@, @name@, @mail@.

Although the discussion plugin references the same config parameter, it does not do the same macro substitution in action.php:_notify(). It is therefore not possible to take advantage of the core feature of macro substitution in $conf['mailfrom'] when the discussion plugin is in use.

$ diff -u action.php.dist action.php
--- action.php.dist 2009-05-28 14:38:52.000000000 +0100
+++ action.php  2009-05-28 14:39:01.000000000 +0100
@@ -1067,11 +1067,16 @@
     function _notify($comment, &$subscribers) {
         global $conf;
         global $ID;
+        global $INFO;

         $notify_text = io_readfile($this->localfn('subscribermail'));
         $confirm_text = io_readfile($this->localfn('confirmsubscribe'));
         $subject_notify = '['.$conf['title'].'] '.$this->getLang('mail_newcomment');
         $subject_subscribe = '['.$conf['title'].'] '.$this->getLang('subscribe');
+        $from = $conf['mailfrom'];
+        $from = str_replace('@USER@',$_SERVER['REMOTE_USER'],$from);
+        $from = str_replace('@NAME@',$INFO['userinfo']['name'],$from);
+        $from = str_replace('@MAIL@',$INFO['userinfo']['mail'],$from);

         $search = array(
                 '@PAGE@',
@@ -1102,7 +1107,7 @@
                     );

                 $body = str_replace($search, $replace, $notify_text);
-                mail_send($to, $subject_notify, $body, $conf['mailfrom'], '', $bcc);
+                mail_send($to, $subject_notify, $body, $from, '', $bcc);
         }

         // notify comment subscribers
@@ -1124,7 +1129,7 @@
                             );

                     $body = str_replace($search, $replace, $notify_text);
-                    mail_send($to, $subject_notify, $body, $conf['mailfrom']);
+                    mail_send($to, $subject_notify, $body, $from);
                 } elseif(!$data['active'] && !$data['confirmsent']) {
                     $search = array(
                             '@PAGE@',
@@ -1140,7 +1145,7 @@
                             );

                     $body = str_replace($search, $replace, $confirm_text);
-                    mail_send($to, $subject_subscribe, $body, $conf['mailfrom']);
+                    mail_send($to, $subject_subscribe, $body, $from);
                     $subscribers[$mail]['confirmsent'] = true;
                 }
             }

Is this plugin dead?

I see it hasn't been updated for a long time, lots of problem reports unaddressed, probably incompatible with the current stable DokuWiki.

As a noob I probably don't want to start mucking with this eh?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.