Compatibilty with Content Taxonomy

I tested the patch. It seems to work fine on node edit, but on node view the controlled field is never visible even if triggered.

That is because of #250710: Not all fields with valid conditions are displayed when viewing node ... patch is underways

the following patch worked here:

you have to apply
http://drupal.org/node/250748#comment-819833
and
http://drupal.org/node/250710#comment-860312

I've applied the three patches and it works fine, all the fields are showing even when using a taxonomy field controller, I think we should commit and release a beta version to keep track more easily of all the changed that were made recently??

Patchak

subscribing

Please commit this one too!!! ;)

as a comment to this, i think it should be a patch in content taxonomy than making a patch to conditions fields
// The problem is that content taxonomy doesn't use '#value'

This is great! Thank's for these patches, they are working just as needed (so far).

@ dereine, so you think we should change the project for this issue ?? But does the patch needs to be redone to be working with content taxonomy ???

Yes, these patches work for me also. Using the dev version of Content Taxonomay now includes the patch: http://drupal.org/node/250710#comment-860312

So the only patches to make this work are the two in this issue, in comment #1 and comment #4.

Here is a single unified patch of the two required patches against the dev version of this module.

This patch does not seem to respect the 'Specify terms to show' in the Content Taxonomy Field window.

Aside from that, if your Vocabulary is enabled as a hierarchy, the patch will also ignore any child terms.

txcrew

I am new to this. How would I go about impementing the patch.

I am getting the error below. I am using Drupal 5.x. Will it help with this issue?

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of conditional_fields_set_required_for_render(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /home/content/r/i/t/ritetimedirect/html/sites/all/modules/conditional_fields/conditional_fields.module on line 899

Thanks,

Sam

Moving to 6.x

hi, any solution for use this module with content taxonomy ,or better, with core taxonomy?
If I can help on something, I am willing to help.

Is this on the way in 6? I really need content taxonomy support too. PS. great module!

Also need it under D6.
Subscribing.

Hi, I've made a patch for D6, please try

Hi,

I applied the patch, it's working when the fields are filled but there is a warning message when the fields are empty.

Please check this thread : http://drupal.org/node/250748#comment-1667274.

Please have Conditional Fields be compatible with Content Taxonomy as soon as possible. Thanks.

come one, critical is everything else. Does this missing feature break your full site? NO!

So its not critical.

I Guess the #18 patch works here, but needs some more work so help there.

Subscribe

Can you let me know how to reproduce the issue? I've tested creating a node using an empty vocabulary and there's no error message. Thanks.

It would be great to be able to use content taxonomy with conditional fields...subscribing

Changing component, and just letting know that Conditional Fields 1.0 will be out next week if no new bug is found!

Great to hear that. I am waiting for the release, can't wait!!! Conditional field + content taxonomy is a make/break feature on my site so I am really looking forward to your release so I can continue working on my site.

Hi,

there is a strange behaviour which I can't correctly assign to content_taxonomy or conditional_fields (or the special connection between them).

I have four fields in one group, with the first field controlling the latter three. For each controlled field there is exactly one entry in the controlling field and all four fields are of type content_taxonomy.

When editing a node, everything looks fine, selecting one of the controlling values triggers the controlled field to be shown. But even in preview and also after saving the node the value of the controlled field is not shown while the value of the controlling field is visible.

I played a little with the available options and two settings are making this field visible again:

• the setting "Administrators see all fields"; but obviously this only works for users with "administer conditional fields" rights
• the setting "on node view: show" in the option group "Orphaned controlled fields settings"

For me this looks like the controlled field is treated like an orphaned one but in fact it isn't. Actually I use the second example and also turned on the option "Reset untriggered fields to default values" so there should not be any real "orphaned" fields. But I guess, this is not the way it was supposed to be.

Does anybody know about this behaviour? Might there be some other settings where I could change this behaviour? Or is this a bug?

I'm using D 6.14, conditional_fields dev as of aug, 16th, the patch from #18 and content_taxonomy 1.0rc2

(I hope this is not the wrong place for this question but there is actually no better place I know of)

I look forward to help testing patches for new issues.
I am also exploring conditional field + content taxonomy for my website at the moment.

subscribing

Suscribe