This is useful when you allow users to have their own blogs, but don't really want to manage their comments or have them managing their comments and everyone else's. Now they can just click the delete link below each comment for nodes they authored...

CommentFileSizeAuthor
#10 users_admin_own_comments.diff2.45 KBmarcoBauli
comments_2.patch2.88 KBms2011

Comments

drumm’s picture

drumm
he/him
Location NY, US
commented
Version: 5.1 » 6.x-dev

This feature will not be put in the stable Drupal 5.x.

catch’s picture

catch
he/him
Primary language English
commented
Version: 6.x-dev » 7.x-dev
Status: Needs review » Needs work

No longer applies.

yngens’s picture

yngens commented

subscribe

macgirvin’s picture

macgirvin commented

subscribe

thehong’s picture

thehong commented

Organic Group needs this feature too.

damien tournoud’s picture

damien tournoud commented

This is a good idea, but the implementation is wrong. The permission should be based on the node type, and the user_owns_node() hack is useless.

yngens’s picture

yngens commented

i am looking either this or User Comment module to be ported to Drupal 6.x. I put small bounty and call others to second my call. Details: http://drupal.org/node/234204#comment-802908

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Marked #295352: Comment permission granulation a duplicate, which has a patch.

I'd like to see this get into Drupal 7, but definitely configurable per content type rather than at a global level. While I probably want users to be able to manage comments to their blog posts, I probably do not want them managing comments to their forum topics.

catch’s picture

catch
he/him
Primary language English
commented

Would make sense to have create foo, edit own foo, administer comments on own foo, edit all foo, although that won't actually work with our permissions page being grouped by module.

marcoBauli’s picture

marcoBauli commented
StatusFileSize
new users_admin_own_comments.diff2.45 KB

rerolled original patch against D5.14 in case someone needs in the meantime

johanneshahn’s picture

johanneshahn commented

There's an error in your patch

@@ -1076,7 +1076,10 @@
 
   $output = '';
 
-  if (is_object($comment) && is_numeric($comment->cid)) {
+  if (!comment_access('delete', $comment)) {

change it tfrom 'delete' to 'edit'

@@ -1076,7 +1076,10 @@
 
   $output = '';
 
-  if (is_object($comment) && is_numeric($comment->cid)) {
+  if (!comment_access('edit', $comment)) {
manop’s picture

manop commented

subscribe. I would love to see this feature too.

jct’s picture

jct commented

I had to change line 385 in comment.module from
'#access' => user_access('administer comments') ,
to
'#access' => user_access('administer comments') || user_access('administer comments in own node'),
to give users access to the "Comment settings" form on node add/edit.

farald’s picture

farald commented

Subscribing

izmeez’s picture

izmeez commented

subscribe

Marat’s picture

Marat commented

I wish to see this feature, should be in core comment module. I think users can open and close commenting on their node!

Subscribing too

catch’s picture

catch
he/him
Primary language English
commented
Version: 7.x-dev » 8.x-dev

This is too late for D7, moving to Drupal 8. However it should be very easy to do this in a contrib module now for D7 since the way comments are built and rendered is a lot more standardized.

jct’s picture

jct commented

Any chance someone has rolled a patch for D6?

Edit:I was able to get some of this functionality with UserComment (http://drupal.org/project/usercomment)

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Needs work » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank 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!

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since this has been around since Drupal 5 and not much follow up believe we can close out. If someone still wants it for D11 we can always re-open

Thanks all

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.