Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.API page: https://api.drupal.org/api/drupal/modules%21block%21block.api.php/functi...
Enter a descriptive title (above) relating to function hook_block_info, then describe the problem you have found:
I posted a couple comments that might be confusing to developers. I'm wondering if you have maintainer's rights to update or delete posts. My posts on this page were entitled "Not so" and "Correction/Retraction." I think it would be best to replace both of these with one post clarifying dalin's suggestion. The post body would be exactly the same as my Correction/Retraction post except with the first few words "I stand corrected. After further research, " omitted.
Thanks!
Comments
Comment #1
jhodgdonMoving to webmasters queue.
Comment #2
apadernoComment #3
jhodgdonWhat is our policy for removing comments on api.drupal.org? I do not know where such a policy is, who's monitoring comments there, etc. This comment that is requested to be removed is not spam, it is merely incorrect.
That is why I moved this to the webmaster queue.
Moving back (sorry!) until someone can point out the policy.
Comment #4
lizzjoyThe policy is at https://www.drupal.org/drupalorg-webmasters-guide and the way I read it this applies: "Content that is outdated by another page should also be unpublished with a comment in the revision log linked to the newer page." Even though it isn't the exact case here, if the comment is giving incorrect information, wouldn't it fall under being outdated?
Comment #5
apadernoWe have Commenting on community documentation pages and API pages. As for correcting a previous given comment, if users cannot edit them (but I do recall the user who wrote a comment can edit it), the only alternative is for the user to post a comment about the previous comment being wrong.
I removed a duplicate comment. Since the request came from the author of those comments, I made the changes as requested. I still think users have the permission to edit their comments, and maybe delete them, but I cannot see the permissions given to users on API.
Comment #6
jhodgdonWe should put in place similar comment editing/deleting permissions on api.drupal.org and drupal.org. I do not know what the permissions are for normal users on d.o. Can someone check on that?
Comment #7
tvn CreditAttribution: tvn at Drupal Association commentedOn Drupal.org 'Authenticated user' and all roles above it have 'Edit own comments' permission. On Api.d.o none of the roles has that permission. Deleting comments ('administer comments') permission is granted to Webmaster role on both sites.
I think giving 'Authenticated user' on api.d.o permission to edit own comments to match Drupal.org makes total sense. Moving to Api.d.o customizations, since user permissions are now stored in a feature. Patch needs to be created and deployed to make this change.
Comment #8
jhodgdon+1 from me for this proposed policy change.
Comment #9
drummComment #11
drummSounds good, fixed and deploying.
Comment #12
jhodgdon@normk: If you are still following this issue, you can now go to api.drupal.org and edit your own comment. At least, it should be possible. Thanks for your patience!