Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Running Drupal 5.5. After installing (removing the offending line in conditional_fields.info), the "Conditional fields" tab is available, but there are no extra fields in the content type editing form. Actually, they appeared once, but never appeared thereafter, even after subsequent uninstall/reinstalls of the module.
Comment | File | Size | Author |
---|---|---|---|
#4 | content export.txt | 2.04 KB | paulowsky |
Comments
Comment #1
peterpoe CreditAttribution: peterpoe commentedPlease read the enclosed README.txt for usage instructions. Conditional Fields doesn't actually create any new cck field type, only adds conditional options to existing fields with allowed values.
Comment #2
richv CreditAttribution: richv commentedYeah, sorry, I didn't say that too clearly. I'm not getting any conditional options on any of my existing fields while in those fields' editing forms.
Comment #3
peterpoe CreditAttribution: peterpoe commentedPlease see this other issue: http://drupal.org/node/206332
If you still don't see any option, could you please export your content type so I can look into it?
Comment #4
paulowsky CreditAttribution: paulowsky commentedCannot see the field editing options to set controllers and controlled fields but can see "Conditional fields" tab.
No groups used. Drupal 5.6. Administration is checked for Conditional Fields. I also read that http://drupal.org/node/206332 but still don't know why I cannot see the fields option.
I used nodereference field type (not in the export content type that you can see in the attached file, but its On in CCK Module) but I think it does not matter, as I read it works for all fields type on select/checkbox/radio buttons fields.
I attach the content type export (if it helps).
Great job.
Comment #5
peterpoe CreditAttribution: peterpoe commentedFor what I understand, you can't see any conditional fields options because you are trying to use a nodereference field type, which doesn't have allowed values configuration options. Only fields with allowed values can be set as controlling fields at this time. See also this discussion: #213275: Use taxonomy as controlling field.
Comment #6
peterpoe CreditAttribution: peterpoe commented