Last modified: 2011-03-13 18:06:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T26820, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24820 - Users should be able to customize thread replies edit summary
Users should be able to customize thread replies edit summary
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Andrew Garrett
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-17 01:33 UTC by Nemo
Modified: 2011-03-13 18:06 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nemo 2010-08-17 01:33:52 UTC
After bug 21931, summary is always auto-filled when creating or replying to a thread. You should be able to add a customized summary to the auto-filled one, as with all auto-summaries.
Summaries are very useful in discussions to let people know what's happening without having to read everything (there's bug 20541 but I don't think that we'll dump recentchanges) and they're heavily used, see e.g. http://en.wikipedia.org/w/index.php?title=Special:RecentChanges&hideanons=1&namespace=1 (and if you're not convinced run a query on the database).
You can say that when you create a thread the title should be the summary, but this doesn't apply to replies.
Comment 1 Andrew Garrett 2010-08-29 03:25:41 UTC
This is probably a WONTFIX. If we're going to allow per-comment summaries, they would be more likely to be versioned and editable.

Will discuss with the design team.
Comment 2 Brandon Harris 2010-09-10 02:19:55 UTC
Per comment summaries are not a function of liquid threads.  However, there is another extension that works *with* LQ that does this already (REFLECT).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links