#1785 closed defect (bug) (duplicate)
After editing a reply, topic's tags changed
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Component - Topic Tags | Keywords: | |
Cc: |
Description
Scenario:
I created new topic.
I added replies from another account.
While editing last reply, I changed reply's tag.
Save.
What's happened?
Topic's tags changed, after changing reply.
Topic was not created on that account, only last reply.
I think that, topic's tags and reply's tags should be diffrent.
Otherwise, it does not make sense to allow add or edit tags to reply.
Attachments (1)
Change History (10)
#2
@
13 years ago
- Keywords needs-testing removed
Was able to duplicate the issue, looking into the cause.
#3
@
13 years ago
- Keywords has-patch 2nd-opinion needs-testing added; needs-patch removed
From what I can tell this fixes things, but I'm not certain that's all there is to it - is there supposed to be multiple topic-tag taxonomies? (just doesn't seem right on first glance)
#4
in reply to:
↑ 1
@
13 years ago
- Resolution set to duplicate
- Status changed from new to closed
Replying to alexvorn2:
the another user should be able only to add a new tag, not to replace the main tag of the post if it is not a member moderator or administrator... I think so.
This is currently by design, until a more robust tagging UI can be built.
Replying to jaredatch:
From what I can tell this fixes things, but I'm not certain that's all there is to it - is there supposed to be multiple topic-tag taxonomies? (just doesn't seem right on first glance)
This is normal.
Closing as a duplicate of #1546.
#5
@
13 years ago
- Keywords has-patch 2nd-opinion needs-testing removed
- Milestone 2.1 deleted
- Priority changed from high to normal
- Severity changed from major to normal
#6
@
13 years ago
- Keywords dev-feedback added
- Milestone set to Awaiting Review
- Resolution duplicate deleted
- Status changed from closed to reopened
- Version 2.0 deleted
Part of it was I rarely use tags so I mis-understood how things were stored, however I think I figured out the issue which was throwing me off. See if this makes more sense.
In 2.0.x when you are on the 'reply form' for a topic, the Tags field is pre-filled with the tags - this makes sense.
If the OP tagged the thread "tag1" and "tag2" the person replying already has those tags in the Tag Field, so they can simply add on any additional tags, eg "tag3". Easy peezy.
In 2.1 this doesn't auto populate (in my 2 test setups).
If the OP tagged the thread "tag1" and "tag2", the person replying gets served an empty tag field. Not knowing they need to re-input the current tags (tag1/tag2) they will probably just enter in "tag3" - on the assumption it will get appended to the current list of tags. This results in the tags getting screwed up - losing "tag1" and "tag2" completely.
Am I missing something or is this a bug? :)
the another user should be able only to add a new tag, not to replace the main tag of the post if it is not a member moderator or administrator... I think so.