Extension talk:CommentStreams

About this board

When reporting an error, please be sure to include version information for MediaWiki and all relevant extensions as well as configuration information. Also, please turn on debug logging as described at Manual:How to debug#Logging and include the relevant portions of the debug log.

Problems with the location of the comment block

1
멍한오리 (talkcontribs)

On my wiki, the comment block always appears at the top of the document. (under the title) I don't know why this is happening.

Reply to "Problems with the location of the comment block"

How to automatically disable CommentStreams on NoticeBoards?

1
Kimmywingz (talkcontribs)

I know you can disable them on individual pages by using <no-comment-streams />. But as this is put in the source code somebody could just remove it. Is there a way to disable comment streams for all Noticeboard Pages (or a specific namespace / category of pages) automatically without having to use <no-comment-streams />?

Thank you

Reply to "How to automatically disable CommentStreams on NoticeBoards?"

How to make comment streams optional on all namespaces?

4
Summary by Kghbln

Set $wgCommentStreamsAllowedNamespaces = -1;. The documentation was updated accordingly.

Kghbln (talkcontribs)

@Cindy According to the docu $wgCommentStreamsAllowedNamespaces = []; should make comment streams optional on the content namespaces, i.e., they should only show if I add <comment-streams /> However, with this setting I stell get comment streams by default on the content namespaces. Is this a bug or did I misinterpret the docu?

MarkAHershberger (talkcontribs)

Try $wgCommentStreamsAllowedNamespaces = [-1];

MarkAHershberger (talkcontribs)

I was almost right. From the source:

// if $wgCommentStreamsAllowedNamespaces is not set, display comments
// in all content namespaces and if set to -1, don't display comments
// unless they are explicitly enabled on the given page

So, use $wgCommentStreamsAllowedNamespaces = -1;

Kghbln (talkcontribs)

Cool, thank you for your help. I verified with a wiki that $wgCommentStreamsAllowedNamespaces to -1. allows for comments on pages with tags only. Currently, the docu on the extensions page states, "To disallow comments on all namespaces even in the presence of the ‎<comment-streams /> tag function, set $wgCommentStreamsAllowedNamespaces to -1.." which is what derailed me.

2A02:8108:50C0:F81:E0C2:2D78:3918:AAC (talkcontribs)

Is there something similiar like the comment of the day feature from Extension:Comment?

Reply to "Comment of the day"

Making the title as optional?

1
Lens0021 (talkcontribs)

Hi, I am always thinking this extension is most stable and most modern extension for comments.

I want to know is there an option to make the title optional, because the articles of my wiki do not need discussions, but just comments. I think it is annoying to give a title to a comment for readers of my wiki.

Thank you.

Reply to "Making the title as optional?"

Error: Call to a member function

1
SyrinxCat (talkcontribs)

I just started getting this error when trying to view all comments...


[ZM94R3bUl1Yr5kva6AGIVwAAAk8] /Special:AllComments Error: Call to a member function getWikitextForTransclusion() on null


Any idea what could be causing this? I am on the latest version of the extension and have run all the updates. I am on Mediawiki 1.39.1.

Comments are displaying fine and you can add/edit. So it's just an issue on the Special:AllComments page it seems.

Reply to "Error: Call to a member function"

How to allow comments only on certain pages?

7
Summary by Cindy.cicalese

Fixed in version 8.0.0.

2601:280:4200:3B9:25A4:7D77:B7BA:3B3B (talkcontribs)

I did $wgCommentStreamsAllowedNamespaces = -1; and on pages I want the comment box I added <comment-streams />, but the comment box is not appearing.

Cindy.cicalese (talkcontribs)

Thank you for your question. I looked at the documentation, and it was outdated. I have updated it to correctly reflect the use of $wgCommentStreamsAllowedNamespaces. If you want to disable comments in all namespace but allow <comment-streams /> to enable comments on an individual page, you should set $wgCommentStreamsAllowedNamespaces to an empty array (i.e. $wgCommentStreamsAllowedNamespaces = [];) instead of -1.

Ludi81 (talkcontribs)

Hi, I tried to use $wgCommentStreamsAllowedNamespaces = []; but the comment is still enabled on all pages. I see the comment field, even if <comment-streams /> is not present on the current page.

Devaroo (talkcontribs)

Hey Cindy & Ludi81, same here, setting $wgCommentStreamsAllowedNamespaces = []; doesn't disable comments. As a workaround, I've only allowed one namespace that I'm not using – a dummy namespace, if you will. It works as expected, comments are enabled by default in that allowed namespace and disabled everywhere else. Inclusion through the comment-streams tag works, too. @Cindy.cicalese thanks for the great extension! Super useful and works like a charm :-)

Cindy.cicalese (talkcontribs)

I'm so sorry for the delay in responding to this. I did not have time to work on this extension for quite a while, but I'm now working on getting out a new release. I was able to confirm the reported behavior and have a patch at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CommentStreams/+/932024/. It should make it into the next release and will be backported the the REL1_39 and REL1_40 branches.

Devaroo (talkcontribs)

Hey Cindy, no worries! Nice to hear you were able to patch this, thanks for your effort :-)

Cindy.cicalese (talkcontribs)

You're welcome! I released version 8.0.0 with the fix two days ago.

79.119.106.13 (talkcontribs)

Hey. First of all: Great extensions! Our users love it. Secondly: Would it be possible to include the year in the timestamp of comments? Currently, the timestamp is a bit of confusing, as not displaying the year doesn't actually show when the comment was made, i.e. users can't tell if it's 7 February this year, last year etc. Also, would it be possible for the extension to simply follow the date format set by users in their preference settings? Or at least to have an option where to control this setting ourselves (whether to be 12 or 24-hour format, dd/mm/yy or yy/mm/dd etc.). Any chance any of these could be implemented in the near future? Thanks!

79.119.106.13 (talkcontribs)

Hey. Could I please receive an answer whether this will be implemented in the future or not?

FrozenPlum (talkcontribs)

I have filed a phab ticket for this (task T326508) as we too have run into this issue with our users increasingly asking about this, as they assume it is expected behavior. It is likely easier to track this kind of request when a there's a ticket.

Wesus99 (talkcontribs)

It seemed like everything was working until I added the command to allow voting, then, even if I remove the command to revert, I get "Invalid API response" if I try to delete a comment or admin delete a comment. Any ideas on what is going on? I honestly am not even sure of where I would look for more detailed error logs on this... Love the feature, I just can't use it if a moderator or user can't delete a comment.

Cindy.cicalese (talkcontribs)

There would be more information in the JavaScript console in your browser. You could also look for api.php in the Network tab of the browser developer tools to see the error response. It sounds like you have uncovered a bug. Please report you MediaWiki and CommentStreams versions, your configuration settings, and any debugging information here or in a new task in Phabricator. Thank you.

FrozenPlum (talkcontribs)

I have created a task for this, adding the stack trace on phabricator task T326382 as I've received the same error on latest CS version (8.0-dev 11350a0 06:44, 3 January 2023) and MediaWiki 1.39.1.

I posted only the stack trace, as there's nothing in the console, and everything shows status 200 in network tab including api.php.

Why is CommentStreams excluded from RecentChanges?

2
Summary by SlyAceZeta

The suppression has been made optional by a new patch, see task T338406.

SlyAceZeta (talkcontribs)

CommentStreams not being included in RecentChanges in any way is an insane decision. Why is this the case? I find myself unable to track new, edited, or deleted comments unless I manually refresh Special:Log/commentstreams or Special:AllComments, which is not an ideal solution. RecentChanges is a standard way to track changes made on the wiki, and I can't believe this extension is completely omitted from RC. Please restore this--it doesn't have to be visible by default, but let us see changes to comments in RC, please.

SlyAceZeta (talkcontribs)