Not saving data for case tracker comment driven.

details? kind of field?

the field being changed in the comment form is not being updated nor showing a changed status in the comment form.

the node doesn't get updated? (when you check it in node edition, for instance)
or is it the comment form the one who refuses to change the widget value?

I'm using with the latest open atrium. I'm not sure if there's something I'm missing.

just the modules coming with Atrium?

Hi arhak,
I get the same results. Text field ("hours remaining").
I tried with 6.x-1.0-alpha3 and 6.x-1.x-dev (using driven api 6.x-1.x-dev).
Editing the node directly at node/N/edit works, but modifying the field in the comment does not change the value.
Open atrium 1.0-beta8 - http://openatrium.com/node/39

do you have itweak_upload enabled?
(if you do, try disabling it to check if it is the same as #917270: iTweak Upload breaks Comment Driven)

what kind of content type are we talking about?
custom content type? provided by a custom module or built through CCK's GUI?

I have the same problem (although not on a case tracker content type) when using on beta8 of OA.

I disabled the iTweak as suggested but it makes no different.

Upon submission of the comment form (and changing two exposed attributes) i get the error message "Comment field is required (or a driven property change otherwise).".

If i then put in a comment string and submit with the modified drive attributes - it submits fine, but has not updated the node cck field values.

Probably more critical than major, as its pretty much stopping the module from working fully?

Is there anything we can do to help resolve this show stopper? Happy to help if there's a plan of action.

Hmm, has the poor comment driven project lost its momentum to get a stable release out? Would some $$ help get this bug resolved?

has the poor comment driven project lost its momentum

yes

to get a stable release out?

it was never meant to get an RC out all by myself

to have a decent release candidate out the door I would need some advisors (I meant "advisors", not "advice")
for some areas I don't feel that comfortable (e.g. Date, Theming, and even some tricky concerns of CCK & FAPI)

Happy to help if there's a plan of action.

more involvement
better feedback, step by step instructions to reproduce it, dump data (using comment_driven_inspect)

Would some $$ help get this bug resolved?

it might,
but useful feedback would still be a requirement,

and actually, so far feedback has been enough to get solvable issues out (there are some known issues within cdriven which require a major rewrite that I'm not able to provide right now, due to lack of time)

sub

sub

I am getting this too. comment driven is not working.

After re-reading the queue and project page, itweak upload was the cause of my issu.e

is this thread about http://drupal.org/project/casetracker_comment_driven ?

Seeing this as well with OA 6.x-1.0-alpha11. I have added a CCK field of type decimal with a text widget. When I use this field as a comment driven field it fails to update, although I can update the field via the node form. The actual comment text does update successfully as do several other CCK fields.

Happy to help resolve this one if I can elaborate or do any testing.

Cheers

El B

first of all, I need "to see" what's going on,
please use comment_driven_inspect module to report back with some dumped data

secondly, I need you to help discriminating which other modules might be introducing incompatibility issues,
to be able to spot it, start a new test OA installation, and disable as many modules as possible (comment_upload, itweak_upload, ajax_comments, or whatsoever),
if not essentially needed for the purpose of testing OA with cdriven, then turn it off for the sake of tests

once you get the minimal amount of enabled modules, repeat your trials,
if it works, start enabling modules until it breaks,
if it doesn't work, continue disabling modules if possible,
if there are no modules left and is still misbehaving it will be a nice thing to point out

@#14
in your particular case:
- enable revisions for that content type
- edit the node, changing the value of the addressed CCK field
- go to node/[NID]/revisions to see the numbers of the existing revisions (so called VIDs)
- enable comment_driven_inspect module (sub-module packaged with comment_driven)
- navigate to admin/build/comment-driven-inspect
- type the pair of VIDs like 123-456 and submit the form
- report back the dumped data, as well as which of the three types of comparisons seems to be correct/incorrect (and if incorrect, exactly how badly)

Note: right now I'm unable to download latest OA (I've got beta8)

Arhak,

I returned to this issue today hoping to follow the steps you kindly suggested. However it now seems to be working, although I have done nothing in the interim to specifically address this issue. Hmmmmm.

The only thing I did was to enable the driven_inspect and related api modules, which I have now disabled. I guess if the problem reappears I'll know what to do to help you.

Thanks

Dave