#11893 closed feature request (wontfix)
Comment author should be able to edit his comments for a half hour
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 2.9.1 |
| Component: | Comments | Keywords: | needs-patch |
| Focuses: | Cc: |
Description
It's a shame that, in 2010, WP still doesn't allow (even on wp.com) to edit one's comment for a half hour/an hour after writing it, in order to fix a typo.
Change History (8)
#1
@
16 years ago
- Milestone changed from 3.0 to Future Release
- Type changed from enhancement to feature request
#4
@
16 years ago
I assumed he meant for anonymous commenters as well.
For registered users only, it would be easier:
- add a link in the theme to the comment editing screen in the admin
- check if the current user is the author of the comment (or add a new capability: edit_own_comments)
#5
@
16 years ago
I did some light testing with anonymous comments. It looks like the author cookie isn't set unless the commenter fills the name field. Unless that gets changed, the editing feature wouldn't be available to everyone.
#6
@
16 years ago
Ah, you've also got trivial session fixation in the existing system. That's a deal-breaker for anonymous comment editing.
- Fill the name field as 'user1' and leave a comment.
- Delete author cookie or switch computers.
- Leave a second comment with same name value as the first commenter.
WordPress resets the second user's author cookie with the first user's session key. The second user can now guess the comment ID number and edit the first user's comment.
Conversely:
- Leave a comment using a known name, 'scribu'.
- Use your favorite method to sneak your author cookie onto scribu's computer.
- When scribu leaves a comment, the author key is already known by a third party and the comment ID number can be guessed for editing access.
I agree.
However, it's not a trivial task. Moving to Future Release until a patch is submitted.
Since we don't have a special template for editing... anything, here's how I think it could be done:
Have a special query_var that would populate the comment area with the desired comment to edit.
Example: