| Attribute | Average |
|---|---|
| Features | 4 / 5 |
| Reliability | 3.5 / 5 |
| Ease Of Use | 5 / 5 |
| Documentation | 5 / 5 |
| Vote Count | 2 |
Content fields and groups visibility based on the values of user defined 'trigger' fields. Description Conditional Fields allows you to assign CCK fields with allowed values as ‘controlling fields’ for other fields and groups. When a field or group is ‘controlled’, it will only be available... [More...]
| Maintainer: | peterpoe |
| Links: | |
| Categories: | Content, Content Construction Kit (CCK), Content display |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.1 | 2010-Jan-14 | Download | Recommended |
| 6.x-2.x-dev | 2010-Feb-18 | Download | Development |
| 6.x-2.0-beta1 | 2010-Feb-17 | Download | Other |
Options: Add a review
The Conditional Fields beta is a breath of fresh air after years of buggy, incomplete contrib solutions for dependent field functionality in CCK. It is simple to configure and reasonably stable. It could use some more features, but even just the basic functionality is a huge step forward in node form usability.
The module does have some bugs, particularly related to fields that aren't bundled with CCK itself. However, in many cases, patches for other field types are available for testing in the module's issue queue.
Hi there, I use the Conditional Fields for the registration with the (node_profile).
After installing, for every field is a tab "Conditional field", here you can choose if this field will show up when a user selected a certian term.
Very useful for registration and many other content types.
I´d like to have the ability to turn on/off the requirement for fields too.
"These days, Google Analytics is essential for a website. Get an account and this module. Set the code..."
"Just the answer I needed for a new website I was making. Well, the domain is new but the content old...."
"This module more or less allows you to write mini-modules in a GUI. Having them written by Rules instead..."
