Page MenuHomePhabricator

Add new sections to the top of a page on a site-wide basis
Closed, ResolvedPublic

Description

Add a configuration option that would allow sites to post new comments at the top (rather than the bottom) of talk [discussion] pages.

I've seen several requests to put new comments [+] at the top of user discussion pages rather than at the bottom so that original comments appear in reverse chronological order, newest to oldest.

Patch is extremely simple (see attached).

This would only affect the section='new' so, microscopic performance impact and would not impact existing talk pages.

Negative is it adds another $wg option ($wgNewCommentFirst).

Activated by adding to LocalSettings.php:

$wgNewCommentFirst = true;

Possible permutations might include:

  • Adding to user preference
  • Tag activated (by page)

Version: unspecified
Severity: enhancement
URL: http://wiki.montcopa.org/TestWiki
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=31919

Details

Reference
bz15494

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:22 PM
bzimport set Reference to bz15494.
bzimport added a subscriber: Unknown Object (MLST).

Configuration option for CommentAtTop of Talk

attachment AddNewCommentsAtTop.patch ignored as obsolete

Patch for trunk (revision 40580)

Added attachment to current trunk

attachment AddNewCommentsAtTop-Trunk.patch ignored as obsolete

*Bulk BZ Change: +Patch to open bugs with patches attached that are missing the keyword*

sumanah wrote:

Jack, thanks for your patch, and I'm sorry it's taken so long for you to get a response. I've added the "need-review" keyword here to signal that developers should take a look and review your code.

Sumana, this was a blast from the past. I'm not sure worth reviewing at this point - Talk is being replaced with liquid threads, right?

sumanah wrote:

The hope is that eventually LiquidThreads will be a suitable replacement, yes. But I think it's still worth working on Talk and improving it in the meanwhile.

We now (as of 1.19) have PlaceNewSection hook that allows extensions to modify where new sections are placed (And one extension does something similar to this request - [[mw:Extension:PlaceNewSection]]).

Since this can be trivially be done by an extension, I would be in favour of closing this bug and getting people to use an extension (I could write said extension if folks want).

sumanah wrote:

Comment on attachment 5301
Patch for trunk (revision 40580)

Marking patch as obsolete given information bawolff gave in most recent comment.

sumanah wrote:

removing keywords.

Oliver, would you be interested in this as a Micro Design Improvement?

Not directly, I'm afraid. I can't see any demand for this from within the community, and we're primarily directed towards editor retention and engagement issues. Sorry :(

This bug is related to bug 31919 ("Allow posting new sections to top of page on a per-page basis").

(In reply to Bawolff (Brian Wolff) from comment #7)

We now (as of 1.19) have PlaceNewSection hook that allows extensions to
modify where new sections are placed (And one extension does something
similar to this request - [[mw:Extension:PlaceNewSection]]).

Since this can be trivially be done by an extension, I would be in favour of
closing this bug and getting people to use an extension (I could write said
extension if folks want).

> moving to Extension requests; does not look like core territory.

Agreed.

*** This bug has been marked as a duplicate of bug 31919 ***