Opened 17 years ago
Closed 17 years ago
#4458 closed defect (bug) (fixed)
users who no longer have the ability to save posts get their posts "stolen" if the post is edited.
Reported by: | markjaquith | Owned by: | markjaquith |
---|---|---|---|
Milestone: | 2.3 | Priority: | high |
Severity: | major | Version: | 2.2 |
Component: | Administration | Keywords: | needs-patch |
Focuses: | Cc: |
Description
- User A is an Author, and published a post ("Post A").
- User A is downgraded to "Subscriber"
- User B edits "Post A"
- Result: User A is no longer listed as the author of "Post A"
This is due to the fact that authors who currently lack the ability to save posts are not listed in the author dropdown box. We need to list the current author in that dropdown, regardless of capabilities, and ensure they are kept as the author on the backend.
This particularly comes to light when importing from another CMS, in which case all authors are created as Subscribers. Any editing of their posts will cause them to lose authorship.
Calling this one major, because mis-attributed posts are a big deal for professional publishers of content.
Change History (5)
#2
@
17 years ago
Sure, but it's going to be rarely that they'll want to do so. The most important thing is that we're non-destructive.
Note: See
TracTickets for help on using
tickets.
Surely the author role is more of a permissions thing than a semantic thing? I don't see why administrators/editors shouldn't be able to set any user to be the author of a post, regardless of that user's role.