Closed (duplicate)
Project:
Drupal core
Version:
4.7.x-dev
Component:
comment.module
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
20 Aug 2006 at 19:39 UTC
Updated:
2 Jul 2007 at 20:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
webchickThis is true, however it involves an API change, and thus is a new feature, and thus will only get applied to HEAD, not 4.7. :( Though this patch will actually probably work for 4.7 too.
Comment #2
robertdouglass commentedThis can be used to avoid another unwanted byproduct of editing comments in flat forums; that the comments change order.
The query that builds the comment list takes the timestamp of the comment into consideration and the timestamp gets updated when a comment is edited, so in a flat forum, you can change the order of comments by editing yours after other replies have come in. While this patch doesn't actually address that bug, it does make it so that site admins could avoid the bug altogether.
Comment #3
dundun commentedPatch works well in Drupal 4.7.3 but 'edit' link still appears under own comments.
Anyway when you click on it all you can get is a 'permission denied' page.
Comment #4
webchickYou're exactly right! Don't know how I managed to miss that, sorry!
Comment #5
dundun commentedIt looks perfect now.
Thanks a lot.
Comment #6
nedjoThis is a good idea. Ideally we'd implement it in a way parallel to the 'edit own [contenttype]' permissions. I.e., it's handled in comment_access() rather than being an additional permission test.
Comment #7
dundun commentedThere is a better solution though.
If you allow edit own comments they should be unpublished and sent to moderation queue again.
Would be that possible?
Comment #8
rkn-dupe commentedThanks for this patch. However its not working for me on 4.7.3.
Running the patch program it says its failed on 2 out of 3 bits.
Doing the changes by hand i can edit them in fine - everything is as it should be. But when i try and load up my forums page everything comes up blank.
Comment #9
robertdouglass commentedyeah, this is a patch against the development branch. It isn't expected to work for 4.7.3. If you are able to tease it into working for 4.7.3 and can submit a patch, that would be a useful resource for people in the future, but it won't get committed to the 4.7.* code base because that is a release and thus frozen... only bugfixes and security issues are committed to releases.
Comment #10
deavidsedice commentedI've send other issue to correct the bug itself:
http://drupal.org/node/128162
But my patch does not add any feature of any kind.
Comment #11
killes@www.drop.org commentedmarking duplicate in favour of http://drupal.org/node/128162
Comment #12
killes@www.drop.org commentedmarking duplicate in favour of http://drupal.org/node/128162