Hey there,

I just installed Conditional Fields 6.2.0 with CCK 2.9 and don't see the "Conditional Fields" section on the CCK field edit page: /admin/content/node-type/[content-type]/fields/[field-item]

I do see the "Conditional Fields" content type options tab for stuff like transition type. Am I just missing something? I thought that the Conditional Fields section was underneath Default Value on the field edit page.

Thanks!

CommentFileSizeAuthor
#8 condfield_ddd.jpg103.03 KBsahuni
#5 cond-field.jpg110.07 KBsahuni

Comments

roball’s picture

Category: bug » support

There is no problem with CCK 2.9, thus this issue is not a bug report.

trailrunner’s picture

Interesting. My install shows no way to set a conditional field. Am I missing something here?

xarbot’s picture

Subscribing. I have the same problem

Xarbot

newtoid’s picture

+1

sahuni’s picture

Category: support » bug
StatusFileSize
new110.07 KB

No section for conditional fields with cck 2.9 and drupal 6.22, when managing a field in /admin/content/node-type/mycontenttype/fields/field_myfield
(But it's OK with cck 2.8).
I know you said it's not a bug, but I'm not sure you are right.
I tried a fresh install drupal 6.22 with just cck 2.9 and conditional fields. Look at attached file

roball’s picture

Your screenshot gives the error that you need to specify allowed values.

sahuni’s picture

Sorry, my example was not perfect. It's because I tried it with severall fields, and I don't finish the setting for the select list.
What I wanted to show is not that error message : it's that there is no fieldset for Conditional fields settings

sahuni’s picture

StatusFileSize
new103.03 KB

Then, here is another example with a basic textfield. Where to click to adjust the conditional field for my field ddd?

sahuni’s picture

Title: CCK 2.9 Compatability » CCK 2.9 Compatibility

I'd like to know if problem is just mine or if it's a well known problem.
I can't upgrade cck from 2.8 to 2.9 because of that problem.

sahuni’s picture

I did some debugging in conditional_fields.module.
IN function conditional_fields_content_admin_field(&$form), following test does not let it continue (line 368) :

// - Exclude fields without Allowed values
    if (!$allowed_values[$field['field_name']] = conditional_fields_allowed_values($field)) {
      continue;
    } 

conditional_fields_allowed_values($field) is an empty array
!$allowed_values[$field['field_name']] = 1 (I must say I don't undestand the ! before the field)

So we cannot work with conditional fieldset.

peterpoe’s picture

Only fields with allowed values can be controlling fields in cf 6.x. If your content type has no field with allowed values, the "Conditional fields settings" fieldset will not appear (it's located just under the "Default value" fieldset).

If you have fields with allowed values and these are not showing up, then this is actually a bug. Please provide more details if this is the case, otherwise, I'll mark this "works as designed".

sahuni’s picture

Category: bug » support

Thank your for your explicite reply.
I never realised that we needed at least 1 field with allowed value for "Conditional fields settings" fieldset to appear.
And it's logical, shame of me!
We need fields with widget list, radio button or just text field with some allowed values.

My test in fresh db with cck 2.9 was done with not enough fields (my purpose was to test fieldsets with conditional fields), and I confess there was no fields with allowed values. And as it was working on server with cck 2.8, I jump to conclusion that it was cck 2.9 the problem. But in fact, on server I have more fields, and amongs them fields with allowed values.

Well, I remove my bug report.
Only thing I can report is a big thanks for excellent module.

roball’s picture

Title: CCK 2.9 Compatibility » Help regarding controlling fields
Status: Active » Fixed

So you finally agree that there is really no problem with CCK 2.9, as mentioned in first reply above.

roball’s picture

Component: Compatibility w/ other modules » Documentation

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.