Page MenuHomePhabricator

Add ability to delete LiquidThreads placeholder threads
Open, LowPublic

Description

Author: theevilipaddress

Description:
When you move a thread to another page, a placeholder always remains at the old page where it has been. However, unlike other threads on the page, it's not deletable. While it may be good to keep them around usually, it should at least be possible to delete them since they clutter the page and the table of contents and some users might not like them. Furthermore, on some wikis, it's common practice to delete unnecessary move leftovers. For example, on the German language Wikipedia, there's an own bot that puts speedy deletion templates on all talk page redirects and move artifacts with a parentheses title. Some time ago, a bot used to delete about 300 user talk subpage redirects leftovers from userspace drafts. Thus, a delete option would be useful, even though you might not want to encourage deleting them.


Version: unspecified
Severity: normal

Details

Reference
bz24621

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:11 PM
bzimport set Reference to bz24621.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Aug 1 2010, 9:23 AM

danny.leinad wrote:

I would like very strong support this request.

On Polish Wikipedia we consider the introduction of LQT on pages where we discuss whether an article should be deleted. On one page we would like to have all open threads and after closing the thread, we are going to move thread to another archive-page (yes, we know that threads can be archived automatically, but more clear situation is distinction on page with open threads and page with archive threads). So placeholder stamp will be useless on page with open threads.

It would be great to

  • create magic word like {{lqtnotcreateplaceholder}} or/and
  • on [[Special:MoveThread]] add option "Leave a redirect behind" the same as on [[Special:MovePage]].

danny.leinad wrote:

*** Bug 24178 has been marked as a duplicate of this bug. ***

Jorm added a comment.Sep 10 2010, 1:33 AM

I'm going to turn this into a real bug and not an enhancement. Here, let me wave my magic wand!

ding!<

danny.leinad wrote:

Hello,

Is there any progress in fixing this bug (and other related to LQT)?

Next weekend Polish Wikipedia community is going to meet on annual strategy planning meeting ([[meta:GDJ 2010]]) and we are planning to talk about enabling LQT. But it would be easier to discuss if the bugs have been fixed :-)

PS. I heard that you are working under new version of LQT - is there possibility to test it?

This is particularly annoying because it makes impossible to archive LiquidThreads, see also bug 24815 and bug 25329.

danny.leinad wrote:

(In reply to comment #5)

This is particularly annoying because it makes impossible to archive
LiquidThreads, see also bug 24815 and bug 25329.

This is a main idea of this bug. As I said in comment 1:
"On one page we would like to have
all open threads and after closing the thread, we are going to move thread to
another archive-page (yes, we know that threads can be archived automatically,
but more clear situation is distinction on page with open threads and page with
archive threads). So placeholder stamp will be useless on page with open
threads."

(In reply to comment #6)

(In reply to comment #5)

This is particularly annoying because it makes impossible to archive
LiquidThreads, see also bug 24815 and bug 25329.

This is a main idea of this bug.

Well, because you agree I add it as blocker of bug 24815.

Ricordisamoa added a subscriber: Ricordisamoa.
Jorm removed a subscriber: Jorm.Dec 26 2015, 7:24 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 26 2015, 7:24 PM
Nemo_bis rescinded a token.Jul 16 2016, 8:01 AM
Jdforrester-WMF lowered the priority of this task from Low 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 Low.Aug 5 2016, 7:37 AM