WordPress.org

Make WordPress Core

Opened 7 years ago

Last modified 2 months ago

#16252 new feature request

Allow comment reparenting to fix poor threading

Reported by: Otto42 Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Comments Keywords: has-patch needs-testing ux-feedback needs-refresh
Focuses: Cc:

Description

For the OCD among us, it would be super nice to be able to edit the comment_parent, to properly thread comments made in the wrong place/threading order.

Choose your own UI, but even just a numeric editor in the Quick Edit area would be a huge enhancement.

Attachments (2)

16252.diff (3.3 KB) - added by MattyRob 6 years ago.
16252v2.diff (3.3 KB) - added by MattyRob 5 years ago.

Download all attachments as: .zip

Change History (13)

#1 @scribu
7 years ago

This was something that was worked on during GSoC 2010:

https://gsoc2010.wordpress.com/matt-harzewski-comments/

#2 @SergeyBiryukov
7 years ago

Perhaps something can be derived from existing plugins, like Move WordPress Comments by Nicolas Kuttler and my own Edit Parent Comment ID.

#3 @MattyRob
6 years ago

  • Keywords has-patch needs-testing dev-feedback added

I recently opened ticket 20292 which was closed as a duplicate of this ticket.

I've attached a patch file that adds a Comment Parent to the 'edit page' and allows a user with edit-comment privileges to enter a new integer into this field to update the database so enabling rethreading.

I've briefly tested it and it allow me to shuffle comments about changing their parents and even reverting the parent field to 0.

@MattyRob
6 years ago

#4 @MattyRob
5 years ago

  • Keywords dev-feedback removed

Updating patch against current trunk code

@MattyRob
5 years ago

#5 @SergeyBiryukov
5 years ago

  • Keywords ux-feedback added

#6 @travisnorthcutt
3 years ago

The Comment Hierarchy Adjust plugin may be of interest to folks with an interest in this ticket.

#7 @rachelbaker
2 years ago

  • Keywords needs-refresh added
  • Milestone changed from Awaiting Review to Future Release

This ticket was mentioned in Slack in #core-comments by ocean90. View the logs.


18 months ago

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


2 months ago

#10 follow-up: @karmatosed
2 months ago

  • Keywords close added

This came up in ux-feedback triage and seems like a plugin would be better for this. Tentatively suggesting a close.

#11 in reply to: ↑ 10 @MattyRob
2 months ago

  • Keywords close removed

Replying to karmatosed:

This came up in ux-feedback triage and seems like a plugin would be better for this. Tentatively suggesting a close.

Having looked at the logs there didn't seem t be a great deal of discussion. What reasons are behind the thought process that this is 'better' handled by a plugin?

There are plugins available of course but the code overhead of loading an entire plugin to address what is covered in the patch above which contains 12 new lines of code seems like a good reason to have this in core. Additionally, there may be a good number of users looking for this who cannot find the plugins (as they haven't been updated for years) to deliver the functionality.

Is there any direct feedback on the way the current patch looks?

Note: See TracTickets for help on using tickets.