I am using this great module for a help desk ticketing system.

I notice that the comment driven values do not correspond with the current values in my node.

As I have others start to use this more, I don't want them to have to change all settings each time they make a comment.

I am not sure if this is a bug or a feature request.

Comments

arhak’s picture

arhak commented

I am not sure if this is a bug or a feature request.

I'm not sure either, since I don't get the idea

could you please describe your issue a little more? (perhaps some example and/or screenshot)

socialnicheguru’s picture

socialnicheguru commented

I have a node with a content taxonomy field, field_ct_field with options 1, 2,3.

I originally selected 3.

Then I hit enter.

I then use comment driven.

Instead of the ct_field being set to 3 it is set to 1, which is just at the top of the list.

arhak’s picture

arhak commented

perhaps related to #873502: Content Taxonomy checkboxes can't be unchecked

so, your problem is just for content_taxonomy fields?

ylavi’s picture

ylavi commented

I have the same issue where using a single value drop-down box to choose a taxonomy value (the taxonomy is required). Instead of presetting the value to the existing taxonomy for the node it sets it to the first actual value in the - not even the "- please choose -" setting!
So while it may be somehow related to 873502 it's not an unchecked-checkbox problem.

arhak’s picture

arhak commented
Status: Active » Postponed (maintainer needs more info)

could not reproduce it,
please provide more detailed steps

which version of content_taxonomy?
configuration details for the field?
- widget type: select list
- default value: none?
- required: checked
- numbers of values: 1
- Save values additionally to the core taxonomy system?
- Vocabulary: tags? multiple? required?
- any Advanced settings for hierarchical vocabularies?

chey’s picture

chey commented
Status: Postponed (maintainer needs more info) » Active

I have discovered this issue as well.

Assumptions:
CCK installed
Content Taxonomy field installed
Comment Driven (Driven API) installed
(hopefully i didn't miss any)

Steps to recreate:

  1. Create a taxonomy vocab with two or more items in it. Call it Tags.
  2. Create another taxonomy vocab. Call it what you wish. Add some different items to it.
  3. Create a new node type. Call it Blog.
  4. Add a new Content Taxonomy field to the new node type that points to the taxonomy vocab you created in the first step (Tags).
  5. Add a second field of type Text to the new node type. Use the select list widget for it and give it a couple values to choose from. Call it Status
  6. Enable comment driven for the Status field only.
  7. Create a new node of the type you created in step 3 (Blog), select a couple Tags(take note of selection), select a Status, save the node.
  8. Proceed with adding a comment to the node. Enter some information in the comment field, select a different Status, preview the comment. This is where you will first see the problem. Note that the Tags in the preview of the node are not what was selected when the node was created.
  9. Save the comment.
  10. After being put back on the view for the node you will see the problem again as the Tags are not what was originally selected.

Again, the only field being used by comment driven in this case was the Status field. Hopefully someone can follow my steps here.

I changed it back to active. Hope thats ok.