Page MenuHomePhabricator

Protecting LiquidThreads talk pages
Open, NormalPublic

Description

Looks like there isn't a way to protect (or semiprotect) completely a talk page with LiquidThreads, e.g. an archived talk: even if you use [edit=sysop] [move=sysop] [newthread=sysop] [reply=sysop] [cascading] , users will be able to edit existing replies (but not to summarize threads, if my test was correct).
I haven't tried all the other possibile actions, but I think that at least cascading protection (or something similar) should block them all.

Otherwise, it's impossible to protect pages from vandalism and even from good faith edits; while currently, if you archive a page, you put the archive in your watchlist and if someone edits it you will see it immediately; with threads it isn't so easy, although I don't remember if watchlisting a talk page will watchlist every included thread).


Version: unspecified
Severity: enhancement

Details

Reference
bz24814

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 21 2014, 11:10 PM
bzimport set Reference to bz24814.
bzimport added a subscriber: Unknown Object (MLST).
Nemo_bis created this task.Aug 16 2010, 5:02 PM
Jorm added a comment.Sep 9 2010, 6:20 PM

This is a big, big conversation, and one that I think requires more consideration than a simple bug can give it. I'm going to take this bug (to remove it from Andrew's plate) and we'll hopefully begin a dialog on a wiki page.

I believe there's one there already (on the redesign talk page) - we can continue it further.

Cancel LiquidThreads talk pages.

Jorm removed a subscriber: Jorm.Dec 26 2015, 7:29 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 26 2015, 7:29 PM
Jdforrester-WMF lowered the priority of this task from Normal to Lowest.Aug 4 2016, 11:35 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

LiquidThreads has been replaced by StructuredDiscussions on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as "Lowest" priority.

Nemo_bis raised the priority of this task from Lowest to Normal.Feb 24 2019, 8:37 AM

Restore information removed with now-invalid rationale.

Liuxinyu970226 lowered the priority of this task from Normal to Lowest.Mar 22 2019, 1:56 AM
Nemo_bis raised the priority of this task from Lowest to Normal.Mar 22 2019, 1:10 PM