Closed (outdated)
Project:
Drupal core
Version:
11.x-dev
Component:
comment.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Nov 2007 at 05:53 UTC
Updated:
8 Aug 2025 at 18:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
JirkaRybka commentedI didn't check the patch yet :( No time.
But a big +1 from me. Also note, that with FLAT comments, we currently have hidden descendants: Also deleted along, but otherwise rather random and completely impossible to see anywhere (except perhaps PhpMyAdmin). There's other issue on that elsewhere (dealing with entirely other bit of that workflow), but for now it makes this fix even more important.
Comment #2
catchPatch works fine, and is a massive, massive, usability improvement for the reasons JirkaRybka outlines above.
The page description should read:
"The following replies" not "Following replies", and only single quotes required.
Also ideally the patch should be rolled from the root of your drupal directory, with the -p option, and without windows line breaks.
Otherwise code style and everything looks fine to my not very picky eyes. Marking as needs work, but these are minor gripes, and it's lovely.
Comment #3
dami commentedThanks for your review and encouragement! I was on windows and used TortoisCVS, and I don't have cvs access on linux box at work...Anyway, just rerolled patch with 'diff -up', changed wording as catch suggested. Hope I have done it right this time.
Comment #4
dries commentedMoving to Drupal 7.
Comment #5
dami commentedDries, can I know why we can't put it in 6.x? It doesn't change any API. We are still in beta2, and I think this is a usability improvement. Thanks.
Comment #6
catchI know we're late in the cycle but I'd agree with dami here. It's quite scary not knowing how many children you're going to kill when you push that button. And as JirkaRybka points out, there's no way to even go back and find out if you use "flat" comment settings. I've been using the 'nasty hack'[sic, Heine] flatcomment module for precisely this reason.
I guess there could be a performance concern if a comment had dozens of children, but then presumably that applies to the actual deletion process as well.
I'm going to drop this back down to D6 for one last chance, although I understand the reasons for postponing it at this stage. Also marking as a bug report since it's unpredictable deletion of users' data ;)
Comment #7
catchBack to D7 :)
Comment #8
birdmanx35 commentedJust tested this patch, the code still applies to Drupal 6 HEAD. It applied cleanly, and the feature is quite nice!
+1 from me.
Comment #9
catchStill applies and the functionality is great. I'm marking this RTBC since birdmanx35 also reviewed positively.
See also JirkaRybka's comments on: http://drupal.org/node/175841#comment-605205 in regard to comment deletion.
Comment #10
catchComment #11
dries commentedCode should use l() instead of constructing its own URL. I'm not sure I'm willing to classify this as a big usability improvement -- it adds clutter to me.
Comment #12
catchIt's not a big win if you have comments set up to be threaded - because then you can work out visually what's going to go beforehand. However if you use the flat setting, you have no way of knowing which comments are replies to which (and users don't care most of the time) - which leads to very unpredictable data loss.
If no-one gets to it I'll work on a re-roll with l() soonish.
Comment #13
Jaza commentedMoving.
Comment #14
pillarsdotnet commentedRe-rolled as requested.
Comment #16
pillarsdotnet commentedTrying again...
Comment #17
pillarsdotnet commentedPatch.
Comment #19
pillarsdotnet commentedOne more time...
Comment #20
pillarsdotnet commented#19: comments-list_descendents_on_delete_confirm-193409-19.patch queued for re-testing.
Comment #21
pillarsdotnet commented#19: comments-list_descendents_on_delete_confirm-193409-19.patch queued for re-testing.
Comment #22
kscheirer#19: comments-list_descendents_on_delete_confirm-193409-19.patch queued for re-testing.
Comment #24
andypostNice UX feature.
There could be a lot of descendant comments so we need to decide how to display them properly
Comment #40
smustgrave commentedThank you for sharing your idea for improving Drupal.
We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #41
smustgrave commentedSince there's been no follow up on this one, going to close out. If still a valid feature though please re-open.
Thanks all!