Extension talk:Comments

Auto refresh page
Hi. This extension is working great! One thing I miss is an auto refresh of the page when you entered a reply to someone else or deleted a comment. - Now, when I reply to another comment, I first need to refresh the page before I can add another reply. - And also, when I delete a comment/reply, the message is still there, till I refresh the page, than it's gone. Should be great if this can be fixed. I was looking into the code already, but can't really find where to add this and how to do that. —The preceding unsigned comment was added by 131.174.244.35 (talk • contribs)

Cannot add comments 2.7.2
Same issue as noted below, appearing in version 2.7.2. When I click add nothing happens, can not find any error-messages generated by press of the button - just seems that nothing happens. No data stored in DB-table comments.

Any ideas? —The preceding unsigned comment was added by 93.190.196.156 (talk • contribs)


 * Try updating your version of Comments and then looking at your browser's JavaScript console for any and all JS errors. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)

Cannot add comments
Hi, I just installed the extension but I cannot add the comments. I am using the version 1.8 If I click on add the comment nothing happens. I have the tables and everything looks good on the installation.

Any help will be greatful —The preceding unsigned comment was added by 189.203.24.27 (talk • contribs)

Not Working.
I've just installed this in my PC at the localhost, e looks like that it works, but I can't send any comments.

Any ideas? —The preceding unsigned comment was added by 189.38.206.71 (talk • contribs) 03:42, 31 October 2011 (UTC)
 * This might sound ridiculous, but it vaguely sounds like the same silly problem I just had. I'm assuming you mean the button and forms are there but won't do anything. If you happened to have manually downloaded each file, make sure that Comment.js wasn't saved as Comment.js.txt!! -81.147.29.227 02:09, 5 March 2012 (UTC)

not working in 1.170
not working in 1.170


 * I found a fix for it in 1.17 by changing a line in the extension's Comment.js:

to You might want to push that into the public release. ~Fern --67.121.127.113 17:25, 6 November 2011 (UTC)


 * The reason why it probably didn't work was because ResourceLoader messed things up. I've updated the code and now it should be RL-compatible (and it requires MediaWiki 1.18). --Jack Phoenix (Contact) 16:40, 7 January 2012 (UTC)

Spam Prevention
Hello before I attempt to install this extension I would like to know if there's any protection against spammers besides administrators going through and deleting each comment. As an example like akismet on wordpress? —The preceding unsigned comment was added by 175.239.223.175 (talk • contribs) 21:48, 22 November 2011‎ (UTC)


 * While there are various anti-spam extensions out there, some of which (like ConfirmEdit and SimpleAntiSpam, for example) are used on Wikimedia wikis, Comments currently doesn't support these. However, seeing that ContactPage extension supports ConfirmEdit CAPTCHAs, I believe that it might be relatively easy to add ConfirmEdit support to Comments. --Jack Phoenix (Contact) 16:40, 7 January 2012 (UTC)


 * thanks for the reply. Thing about captha is that its not very effective these days. I know this a long shot but possible to implement akismet - http://akismet.com/development/  ? Thing works beautifully at least on wordpress! --175.239.243.165 21:12, 7 January 2012 (UTC)


 * I've just tried out QuestyCaptcha and really impressed with it. That works well. Can that possibly implemented for spam prevention? If so definitely will install the extension. --175.239.131.38 23:46, 27 April 2012 (UTC)

MediaWiki Version 1.18.1 - Delete Comment did not work / Comments of the day
I just test "Comments" - was easy to install but i found 2 "bugs" in my enviroment:

1. The "Delete Comment" Link did not work. i set the rights in LocalSettings.php and have the link at the comments (if i logged in) - but the link ist "red". If i click the link, the page is reloading - but the comment isn't delete. I take a look in the scripts - but i did not find why. I try 3 different Webbrowser (IE / Firefox / Chrome) but is all the same

2. The "Comments of the day" did not work - i think the reason is that i have so social network plugin. i removed the line 94 and 95 and it will work (at this line the script ry to get the avatar and the image of the avatar
 * i have same problem too. i delete this from my database--Hamed.n (talk) 10:01, 21 February 2012 (UTC)

JJ-4APR2012: Same issue here... —The preceding unsigned comment was added by 68.14.221.168 (talk • contribs) 20:30, 4 April 2012

MediaWiki 1.18.1
I can not delete the comments once inserted. All other functionality seems to be working just fine.

No Delete
Comments will not delete —The preceding unsigned comment was added by 68.14.221.168 (talk • contribs) 20:31, 4 April 2012

Trouble with Comments on 1.18
I ran into a problem first where Comment.js was saved as Comment.js.txt, but I fixed it. I can not get this to work on MediaWiki 1.18 using WampServer. I tried removing sajax_do_call because I saw it was deprecated and updating the code to use $.get, but I really don't know what I'm doing.

But basically, I got the latest manually, and it isn't working for me on 1.18. If I figure out what's wrong I'll update this topic.

So now I found a problem that I'm still getting a file not found error from ResourceLoaderFileModule: script file not found: "C:\wamp\www\wiki\extensions\Comments/Comment.js"'

Note the non-WINDOWS separator in front of Comment.js

I'll see if hard coding the lines in ResourceLoaderFileModule make a difference.

I fixed it by hard-coding the lines in ResourceLoaderFileModule to use "\\" instead of "/".

COMMENT DELETED
COMMENT DELETED TO PREVENT CONFUSION Khpark87 (talk) 12:48, 6 May 2012 (UTC)


 * Hi Khpark87, I'm glad to see that you're interested in the Comments extension and improving its codebase. What I found strange, however, is that instead of contacting me or anyone else with commit access to svn.wikimedia.org, you decided to fork the code, pack it up as a .rar file and encourage people on this talk page to download your fork instead of the "official" version, so to say.


 * I don't believe in forks most of the time. Sure, sometimes they're necessary, if a project is no longer being maintained, for example. This is not the case with the Comments extension and svn.wikimedia.org in general (although, yes, svn.wikimedia.org will made completely read-only in 2013, by which I need to find a new place for hosting all the social tools and other extensions I've written).


 * It would've been more than preferrable had you tried to contact a developer in the first place to get your changes approved. I, for one, despite by busy schedule, am always interested in patches and making the extension's codebase better.


 * For what it's worth, I've fixed the issue with comment deletion in r115137 &mdash; by using a patch submitted by a user of this extension.


 * I sincerely wish that we can collaborate on this extension in the future instead of causing unnecessary confusion and code duplication. --Jack Phoenix (Contact) 15:10, 10 May 2012 (UTC)


 * Thank you for reply. To tell the truth, I was not familiar with Wiki and open source revision system such as SVN, GIT(now I am wating for approving SVN account). After read your comment, I realize that 'fork' is inefficient and Social Profile is maintained by same person, you. Sorry to make it complicated and if you allow, I want to collaborate improving Comments and Social Profile. Khpark87 (talk) 19:12, 10 May 2012 (UTC)

Chinese translation for this extension
/* Chinese translate by zoglun@gmail.com */ $messages['zh'] = array(	'comment-comment' => '评论',	'comments-db-locked' => ' 添加评论 数据库被锁死，正在进行维护，请过一段时间后再来~！',	'comment-voted-label' => '投票',	'comment-loading' => '读取中...',	'comment-auto-refresher-enable' => '开启评论自动刷新',	'comment-auto-refresher-pause' => '关闭评论自动刷新',	'comment-reply-to' => '回复给',	'comment-cancel-reply' => '取消',	'comment-block-warning' => '你确信你要永久的忽视全部来自这里的评论吗？',	'comment-delete-warning' => '你确信你想删除这段评论？',	'comment-block-anon' => '匿名用户（显示IP地址）',	'comment-block-user' => '用户',	'comment-sort-by-date' => '按时间顺序排列',	'comment-sort-by-score' => '按分数高低排列',	'comment-show-comment-link' => '显示评论',	'comment-manage-blocklist-link' => '管理忽略评论列表',	'comment-ignore-message' => '你忽略了来自这个人的评论',	'comment-you' => ' 你',	'comment-reply' => '回复',	'comment-login-required' => '登陆后才能留言',	'comment-not-allowed' => '你没有足够的权限来留言',	'comment-post' => '发表评论',	'comment-submit' => '添加你的评论',	'comment-score-text' => '分数', 'comment-permalink' => '永久链接', 'comment-delete-link' => '删除评论', 'comment-anon-name' => '匿名用户', 'comment-anon-message' => ' 欢迎 评论~！ 如果你不想匿名, 免费注册 或者 登陆. ',	'comment-ignore-item' => '$2 在 $3 (解除黑名单)', 'comment-ignore-no-users' => '目前没有用户被加入黑名单. ',	'comment-ignore-remove-message' => '你确信你要把$1的评论移出黑名单？', 'comment-ignore-unblock' => '解除封锁', 'comment-ignore-cancel' => '取消', 'comment-ignore-title' => '忽略的评论列表', 'commentignorelist' => '忽略的评论列表', 'comments-no-comments-of-day' => '目前没有今日评论', // for the parser hook 'commentslogpage' => '评论日志', 'commentslogpagetext' => '这是评论的日志', 'commentslogentry' => '', # For compatibility, don't translate this 'commentslog-create-entry' => '新评论', 'comments-create-text' => '$1 - $2', # Don't translate this 'comments-time-ago' => '$1 之前', 'comments-time-days' => 'NaN $1 天s', 'comments-time-hours' => 'NaN $1 小时s', 'comments-time-minutes' => 'NaN $1 分钟s', 'comments-time-seconds' => 'NaN $1 秒s', 'log-show-hide-comments' => '$1 评论日志', // For Special:Log // For Special:ListUsers - new commentadmin group 'group-commentadmin' => '评论管理', 'group-commentadmin-member' => '评论管理员', // For Special:ListGroupRights 'right-comment' => '提交评论', 'right-commentadmin' => '管理用户提交的评论',

--Zoglun (talk) 05:15, 13 June 2012 (UTC)


 * Thank you for your contribution, Zoglun! I've committed your Chinese translation to SVN in r115505. --Jack Phoenix (Contact) 11:46, 13 June 2012 (UTC)

Automatically add to pages
Is there a way to add the comments to every page in the main namespace automatically instead of manually inserting the tag at the end of the article? I'm very new to the backend of MediaWiki, so perhaps there's something I'm missing. &mdash;Topher208 (talk) 21:05, 3 July 2012 (UTC)


 * If you have a basic knowledge about coding, you can use ArticleViewHeader hook. Worked for me in HelpCommons extension. Cheers, Tim (SVG)  22:11, 3 July 2012 (UTC)

Download not available
I tried to download this extension using http://www.mediawiki.org/wiki/Special:ExtensionDistributor/Comments. Got 404 error. How can I download it? —The preceding unsigned comment was added by 1.23.201.162 (talk • contribs)


 * Ext dist is broken for non git extensions at the moment. You can download directly from http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/Comments/ Bawolff (talk) 12:38, 16 July 2012 (UTC)

Comment moderation
Will there be a possibility of some kind of moderation in later releases? So anonymous users can post comments without having an account but giving the admin the possibility to accept or refuse comments before publishing them?

87.139.121.244 06:24, 25 July 2012 (UTC)


 * Maybe in future releases, yes. It sounds like a feature that would be nice to have (but I'm not actively working on building such a thing at the moment). --Jack Phoenix (Contact) 19:04, 7 September 2012 (UTC)

Only works once.
Hi, I installed this extension on the 1.19 version of Mediawiki. At first, everything works just fine. But when I post a comment, everything stops working entirely -- and by everything, I'm assuming it's just the Javascript. Basically, once a comment is posted and until I manually refresh the page, neither the delete nor reply functions work. When I hit delete, nothing happens at all. When I hit reply, it simply takes me to the bottom of the page and doesn't activate the reply script. Now, I'm good with PHP, but Js is an absolute foreign land for me, so any help is appreciated.

EDIT: OK, I applied a quick and dirty fix by having the thing reload the page whenever a comment is posted. Now, everything works fine, since the delete and reply functions don't break the script.

EDIT: So, since the refresh thing works, I've tracked everything down to that "ugly" viewComments function. Something it does seems to break everything. —The preceding unsigned comment was added by 75.58.116.24 (talk • contribs)

Do comments cause a watchlist notification?
When someone adds a comment to an article, and users are watching the article, does the added comment produce a watchlist notification? Thanks. Maiden taiwan (talk) 15:00, 7 September 2012 (UTC)


 * I believe it doesn't cause a watchlist notification, but do tell me if I'm mistaken (I haven't ever tested that out to be honest). --Jack Phoenix (Contact) 19:04, 7 September 2012 (UTC)

Our version
With email notification, recaptcha, threaded comments, preview and blah blah blah. —The preceding unsigned comment was added by Mopec (talk • contribs)


 * Very nice! Is the source code available somewhere? Many of those features would be very useful to have integrated into the mainline codebase. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)

RU translation
$messages['ru'] = array(	'comments-comment' => 'Comment',	'comments-desc' => 'Добавляет парсеру поддержку тэга, позволяющего комментировать страницу',	'comments-db-locked' => ' Добавление комментариев В настоящий момент база данных заблокирована для технического обслуживания. Пожалуйста, попробуйте позже!',	'comments-voted-label' => 'Голос учтён',	'comments-loading' => 'Загрузка...',	'comments-auto-refresher-enable' => 'Включить автопоказ новых комментариев',	'comments-auto-refresher-pause' => 'Приостановить автопоказ новых комментариев',	'comments-reply-to' => 'Ответ участнику',	'comments-cancel-reply' => 'Отмена',	'comments-block-warning-anon' => 'Вы уверены, что хотите игнорировать все комментарии от данного участника (его IP-адреса)?',	'comments-block-warning-user' => 'Вы уверены, что хотите игнорировать все комментарии от участника $1?',	'comments-delete-warning' => 'Вы уверены, что хотите удалить этот комментарий?', 'comments-sort-by-date' => 'Сортировка по дате', 'comments-sort-by-score' => 'Сортировка по оценке', 'comments-show-comment-link' => 'Показать комментарий', 'comments-manage-blocklist-link' => 'Управление списком заблокированных', 'comments-ignore-message' => 'Вы игнорируете автора данного комментария', 'comments-you' => 'Ваш', 'comments-reply' => 'Ответить', 'comments-login-required' => 'Необходимо представиться, чтобы оставить комментарий.', 'comments-not-allowed' => 'Вам не хватает прав для отправки комментария.', 'comments-post' => 'Добавить комментарий', 'comments-submit' => 'Добавить комментарий', 'comments-score-text' => 'Оценка', 'comments-permalink' => 'Ссылка', 'comments-delete-link' => 'Удалить комментарий', 'comments-anon-name' => 'Непредставившийся участник', 'comments-anon-message' => 'На сайте комментарии можно оставлять всем. Если Вы не хотите оставаться анонимным, зарегистрируйтесь или представьтесь. Это бесплатно.', 'comments-ignore-item' => '$2 on $3 (unblock)', 'comments-ignore-no-users' => 'В настоящий момент нет игнорируемых участников.', 'comments-ignore-remove-message' => 'Вы уверены, что хотите перестать игнорировать комментарии участника $1?', 'comments-ignore-unblock' => 'Разблокировать', 'comments-ignore-cancel' => 'Отмена', 'comments-ignore-title' => 'Список игнорируемых участников', 'commentignorelist' => 'Список игнорируемых участников', 'comments-no-comments-of-day' => 'Комментария дня сегодня нет.', // for the parser hook 'commentslogpage' => 'Лог комментариев', 'commentslogpagetext' => 'Лог комментариев.', 'commentslogentry' => '', # For compatibility, don't translate this 'commentslog-create-entry' => 'Новый комментарий', 'comments-create-text' => '$1 - $2', # Don't translate this 'comments-time-ago' => '$1 назад', 'comments-time-days' => 'NaN $1 дняs', 'comments-time-hours' => 'NaN $1 часаs', 'comments-time-minutes' => 'NaN $1 минутыs', 'comments-time-seconds' => 'NaN $1 секундыs', 'log-show-hide-comments' => 'Лог комментариев $1', // For Special:Log // For Special:ListUsers - new commentadmin group 'group-commentadmin' => 'Модераторы комментариев', 'group-commentadmin-member' => '', 'grouppage-commentadmin' => ':Модератор комментариев', // For Special:ListGroupRights 'right-comment' => 'Комментировать', 'right-commentadmin' => 'Модерировать комментарии', ); -- Vlsergey (talk) 21:12, 20 December 2012 (UTC)


 * Hi Vlsergey and thank you for the translation. By now, Comments extension &mdash; like the MediaWiki core software and numerous other extensions &mdash; is using translatewiki.net for internationalization (i18n) and localization (l10n), so you should sign up there in order to translate untranslated extensions and improve existing translations. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)


 * This pural forms is invalid (and Git master too). Mediawiki implements only 3 pural forms. And the same pural form for 1, 21, 31, 41...(singular form) should be:

'comments-time-days' => 'NaN $1 дняs', 'comments-time-hours' => 'NaN $1 часаs', 'comments-time-minutes' => 'NaN $1 минутыs', 'comments-time-seconds' => 'NaN $1 секундыs',
 * --SimonLitt (talk) 19:55, 7 November 2013 (UTC)

Add comments log to Recent Changes
How exactly can I make the comments log appear in the Recent Changes, so users don't have to go to Special:Logs? --GeorgeBarnick (talk) 22:42, 1 March 2013 (UTC)


 * Extension:Comments --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)


 * I added the $wgCommentsInRecentChanges = true; code to LocalSetting.PHP file, but it is not working. My SpecialChanges is index.php?title=Speciális:Friss_változtatások, because I installed MediaWiki with Hungarian languages.
 * Atomjani (talk) 06:49, 10 December 2013 (UTC)

Voting for anonymous users
Extension works great, but voting seems to require users to be logged in while commenting is allowed to everyone (default right). How can we change this? Can we use a voting right as we do with the comment one setting for example: $wgGroupPermissions['*']['votecomments'] = true; Maybe just an ip check could be enough to avoid self voting or spamming votes. Tank you --Federicodip (talk) 11:28, 5 May 2013 (UTC)

database not updating
Possibly I am missing something, but I receive the following error when attempting to use the extension comments:

Database error A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "Comment::getCommentList". Database returned error "1146: Table 'cre1323108561357.mw_Comments' doesn't exist (cre1323108561357.db.11635546.hostedresource.com)".

I have tried the install on two different instances and both produce the same error. Yes, I ran update.php with no errors. It simple appears not to be update the database. I looked at the schema and confirmed the new tables are not present.

Please advise. —The preceding unsigned comment was added by Mp29885 (talk • contribs)

I am also having this problem.

Any help would be great.

Thanks —The preceding unsigned comment was added by 110.22.53.0 (talk • contribs)


 * Update your copy of the Comments extension and rerun update.php &mdash; older versions (which also lacked the update.php support) did not have support for $wgDBprefix (the database prefix). In any case, if possible, I'd recommend getting rid of the database prefix in the long run, it's more problematic than anything else in my opinion. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)

My corrections and suggestions
If there are very much comments (they can be added by spam bots), the error may occur due to long-running script. To fix this, need to limit the number of simultaneously displayed comments and add a pager. I implemented it, you can download the my version of the extension from the following page: http://coding.bezslabostei.ru/File:Comments-mw1.21_my-20130828.zip (also there are diff files at the achive).

I also suggest: --SimonLitt (talk) 21:48, 28 August 2013 (UTC)
 * То spam protection is necessary check the input text for links. Further action will depend on the user's rights.
 * If the user don't have a permission to bypass a check, that should be displayed Captcha.
 * If the user don't have a permission to bypass the pre-moderation, the comment should not appear until it will be approved by the administrator.


 * Hi SimonLitt and thank you for the patch! I recall reviewing this earlier on, and while the code itself was mostly issue-free and the only "problems" I could find were very minor code style nitpicks, the main issue I had with it was the lack of AJAX. Comments uses JavaScript and AJAXy things extensively (whether that's a good or a bad thing is a different debate...) but since your code generates "normal" links, clicking on the pagination links causes the entire page to be reloaded. This not only breaks the "look and feel" of the extension, but it's rather inconvenient for the end-user.


 * That being said, you're absolutely right &mdash; Comments needs proper pagination, it needs anti-spam measures and moderation queue would be also very useful to have. While I don't have the time to work on all of those myself, I'd be happy to assist you and/or any and all other developers who feel like tackling these issues to the best extent of my abilities. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)


 * Now I implement fully AJAXy pager. And fix a loop error (thanks うー). You can download the my version of the extension from the following page: http://coding.bezslabostei.ru/%D0%A4%D0%B0%D0%B9%D0%BB:Comments-d6e0307-my20131107.zip --SimonLitt (talk) 19:01, 7 November 2013 (UTC)


 * Hi again Simon and my apologies for the delay in reviewing your patch! I cleaned it up a bit and submitted to the repository as 99632. Thanks again for your contributions, I'm sure many users will like the new features you added. :-) --Jack Phoenix (Contact) 11:33, 6 December 2013 (UTC)

Theoretical bug
Hello,

Jack Phoenix helped me with a problem over at the MediaWiki Support Desk, and he referred me to the source code for this extension as guidance in writing my own. I have written a JavaScript function that was modeled on your function in. In the process of testing my function, I discovered a bug that manifested in my extension, and I suspect it would in yours as well. I have never used your extension or tested this, so this may only be a potential bug. :-)

Here is an excerpt of what I wrote over at the Support Desk:

I've used the function as a model for my own. I found that if I click the toggle link [in my own extension] several times (>10), the toggling takes longer and longer, roughly twice as long each time. Quickly, this brings my browser to its knees.

The problem is that each time the  function is called, a new jQuery event handler is created using. It is appended to the list of existing event handlers. So, for each click, JavaScript is executing, etc., and this list doubles in length with each click.

One way to fix this is to use instead of   in these two lines of code:. Although, since [the Comments] extension is using  instead of   and there are other on-click events associated with , you may need to use  in combination with   instead (see the example here).

I hope you find this helpful!

--Jpgill86 (talk) 15:35, 27 September 2013 (UTC)


 * Hi Jpgill86 and thanks for the detailed report! Talk about a rather obscure bug! I haven't tested that part of the Comments extension extensively, but I'll try to find some time for that and apply your suggested fixed. But in case if I forget, you're more than welcome to apply for developer access and submit a patch on gerrit (and add me as a reviewer for the changeset). --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)

Git Snapshot for 1.20
Just a heads up. The Git snapshot downloader for version 1.20 downloads an old version - revision 9807f3c (2012-11-04). The most recent major change (as of this comment) is d8f84d4 (2013-07-28), which is compatible with 1.19+, and includes compatability with maintenance/update.php 03swalker (talk) 10:12, 1 October 2013 (UTC)

loop comments
  - If add this text in the comment. Comments extension has loop message.

Proposal
—The preceding unsigned comment was added by うー (talk • contribs)


 * Thank you for the patch. I'm not sure if this is the cleanest possible approach, but the issue you describe is a very real one and especially inexperienced users might stumble upon it, so fixing it would be very nice. I'll see if I can get a Parser guru somewhere to explain me the internals of parser hook processing and what's the proper way to handle these kind of edge cases. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)


 * Is not full patch. When the comments loaded through ajax, the problem remains. --SimonLitt (talk) 15:08, 7 November 2013 (UTC)

Comments Extension Database error
I have installed Comments extension http://www.mediawiki.org/wiki/Extension:Comments ,i am using 1.21.2 version of mediawiki, i have updated the wiki ,when i have checked Special:Version it is there ,but when i have added to the end of the page ,it is showing this error Database error A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "Comment::getCommentList". Database returned error "1146: Table 'lriwiki.lriComments' doesn't exist (lriwiki.db.5278410.hostedresource.com)".

please help me with a slution,i have been stuck with this for 3 days, googling a lot —The preceding unsigned comment was added by Fazeela Abu Zohra (talk • contribs)


 * You forgot to create the required database table, as described in the installation instructions (step #2). Make sure you have an up-to-date version of the Comments extension and then rerun maintenance/update.php. --Jack Phoenix (Contact) 13:06, 1 November 2013 (UTC)

More level comment
I would more level comment. Example:

Comment1
 * Comment2
 * Comment4
 * Comment5
 * Comment6
 * Comment7
 * Comment3

How can I set this?


 * LiquidThreads may be more useful for you. Otherwise it'd require various hacks to the extension. --GeorgeBarnick (talk) 07:09, 10 December 2013 (UTC)

Disable avatar, reply and permalink; add delete for poster, sort by username
What's the best way to disable the display of avatar images, and the reply and permalink links?

I'd also like to be able to sort by username as well as date.

Lastly, I'd like to give the poster the ability to delete their comment.

Thanks!