4/12/2007 ↓

APAD: Ajax Edit Comments

Thanks for visiting! If you're new here, you may want to subscribe to our RSS feed. This blog posts regular Wordpress news, updates of themes, plugins, ideas, hacks, quick fixes and everything about blogging, especially about Wordpress. Go ahead, subscribe to our feed! You can also receive updates from this blog via email.

Name:
Ajax Edit Comments

Plugin Page:
http://www.raproject.com/wordpress/wp-ajax-edit-comments/

Description:
WP Ajax Edit Comments (for WP 2.1+) allows users and admins alike to edit comments on a post. Users can edit their own comments for a period specified by the admin, and admins can edit all post comments.

Features:

  • Edit comments inline without page reloads.
  • Can turn off comment edits for non-admins.
  • Authors with admin can choose to disable the comment editing in their User options.
  • Can adjust the comment editing time in the admin panel.
  • Users without JavaScript disabled will see a regular comment page.
  • Absolutely no theme or file manipulation needed. Works completely out of the box.

Implementation:
If you are admin, simply hover over a comment in a post and click. The comment will load, and from there you can edit the comment. If you click “Save” without editing, an error will result. This is normal. Simply click “Cancel” to back out of the error.

If you are admin and want to turn off comment editing while still allowing your users to edit, you can turn it off by going to Users » AJAX Edit Comments.

If you are a user, leave a comment. You may edit for a specified amount of time. If your comment is in moderation and you decide to edit, your comment will disappear from the page on the next refresh. Make sure you do all of your editing before you refresh the page.

Future Plans:
1. E-mail admin when someone makes a comment modification.
2. Re-moderate the comment if a user adds significant wordage or links
3. Better error messages.
4. Show the user how much time is left to edit.

My Review:

This is one plugin I love using, simply because it makes things a lot easier. I got it running on my blog and the very fact that I give users to edit their comments means there will be reduced duplicate comments with corrections.

That I believe is the primary objective of this : Allow your users to edit their comments to clean up their spelling, grammar etc.

The plugin allows you to set the timeout beyond which a user will not be allow to edit his or her comment. This is good because you don’t want users changing their comments after new comments are posted.

You also have the option of turning off user editing, while allowing admins to edit comments.
This is still a boon as you save tonnes of bandwidth loading the wp-admin page and editing the comment and returning to your page again.

A good feature of the plugin is that it doesn’t need the commenter to be a user of your blog to allow them to edit. This works well on blogs (like mine) that have user signup disabled.

Unless I run into major problems with the plugin (I haven’t seen any so far), it’s staying on my blog.

Would you install this?

1 Star2 Stars3 Stars4 Stars5 Stars (17 votes, average: 4.53 out of 5)
Loading ... Loading ...

Visitors who read this post, also read:

    20 Comments | Leave a comment | Comments RSS

    1. I’ve installed this plugin and think it’s great. I had to mess around with the js I had already on my site (simply removed an “onLoad”), and then did some finessing of the plugin output, but simply works. Heartily recommend it.

      [Reply] Ben M — 04/13/2007 @ 12:37 am
    2. Ajay,

      The link to the plugin is hidden somewhere :) - I’ve included it in my name URL.

      [Reply] Ronald Huereca (7 comments.) — 04/13/2007 @ 1:00 am
    3. Quite a useful plugin, biggie ups to Ron for actually providing the link to the plugin. ;)

      [Reply] Brendan (4 comments.) — 04/13/2007 @ 1:10 am
    4. Completely forgot about the link. It should be fixed now.
      [Reply] Ajay (127 comments.) — 04/13/2007 @ 1:10 am
    5. I’ve had it installed for a week, but I’ve run into a problem with it. The author mentioned a bug where “quotations and apostrophes cannot be used when editing and will cause MySQL errors when the admin is logged in.” It seems to be a rare occurence, but it’s still annoying.

      That nasty bug aside, this is a fantastic plugin.

      [Reply] Luis Cruz (2 comments.) — 04/13/2007 @ 2:40 am
    6. I was going to install this just last night, but grew tired and weary. Great to see some more recommendations. Hopefully I can get it installed this weekend. :)

      [Reply] Dave (16 comments.) — 04/13/2007 @ 10:29 am
    7. It’s definitely a neat plugin, but I wish it had a timeout for admins, too. I keep accidentally clicking on comments and having to cancel out of the edit. There’s a similar problem with hyperlinks, too. You can’t click on them without going to edit, although the work around is opening a new tab instead of opening in the current tab.

      [Reply] jonathan hickman (8 comments.) — 04/13/2007 @ 11:21 am
    8. Jonathan,

      You can turn off admin edits by going to Users -> Ajax Edit Comments.

      [Reply] Ronald Huereca (7 comments.) — 04/13/2007 @ 11:32 am
    9. I don’t want to turn them off; I want them to time out, just like they do for users.

      I do want to be able to edit it the first 30 minutes or so after they made the comment, but I don’t want it to be editable ad infinitum.

      Actually, what the hell am I thinking? I never edit users’ comments….

      [Reply] jonathan hickman (8 comments.) — 04/13/2007 @ 11:35 am
    10. [...] la revue de Ajay de weblogtoolscollection et voici la page du [...]

      Le plugin Ajax Edit Comment pour éditer les commentaires en ligne — 04/13/2007 @ 5:26 pm
    11. I installed this plugin last week when it was first featured (and linked back to the author by blogging about it) and I think it’s a great plugin… I don’t edit users comments unless they ask me to, but they really appreciate being able to edit their own comments.

      [Reply] Britgirl (5 comments.) — 04/13/2007 @ 11:41 pm
    12. WordPress needs more AJAX behaviour. I can’t think of any other feature I want. It’s the best blog software already.

      [Reply] Batman — 04/14/2007 @ 1:19 pm
    13. Tried it and liked it, but it doesn’t validate. Every post had a validation error.

      [Reply] NewMexiKen (3 comments.) — 04/14/2007 @ 3:36 pm
    14. Tried it and love it. It was a painless install. The only thing I had to modify was to remove the “clear” elements from the stylesheet and the php page so that it didn’t break my comments layout.

      The only other thing I noticed was that if I viewed my site at its “www” url the plugin didn’t seem to be active, but if I went to my default URL without the “www” it worked just fine.

      Anyhow, I’ve been using it to great success, and my readers seem to like it as well. Kudos!

      Rich
      BlogRodent

      [Reply] Rich Tatum (4 comments.) — 04/16/2007 @ 1:35 am
    15. [...] Weblog Tools Collection weitere Artikel: « Opera 9.2: Schnellwahl mal anders || Trackback-URL Gelesen: 2 heute: [...]

      Basic Thinking Blog » WP Ajax Edit Comments — 04/18/2007 @ 6:37 am
    16. [...] [Entrada traducida. Original] [...]

      WeblogToolsCollection Español » Blog Archive » APAD: Ajax Edit Comments — 04/18/2007 @ 2:03 pm
    17. [...] 让用户能够编辑他们的留言,这是一个非常不错的想法,至少在用户可以减少用户为了修改上次输入留言中的错误而产生的重复留言。本文翻译自:Weblog Tools Collection 的 APAD: Ajax Edit Comments [...]

      我爱水煮鱼 » Ajax Edit Comments — 04/21/2007 @ 12:31 pm
    18. Ajax Edit Comments…

      让用户能够编辑他们的留言,这是一个非常不错的想法,至少在用户可以减少用户为了修改上次输入留言中的错误而产生的重复留言。本文翻译自:Weblog Tools Collection 的 APAD: Ajax Edit Comments
      …..

      我爱水煮鱼 — 04/21/2007 @ 12:31 pm
    19. [...] זה שייך לסדרת תוסף ליום של Weblog Tool Collection אני רק [...]

      תוסף ליום: עריכת תגובות בעזרת אג’קס : הבלוג של אח”×™ דקר — 04/26/2007 @ 10:25 am

    Leave a comment

    Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

    (required)

    (required, will not be published)


    S2