Now that Conditional Fields 1.0 is out, we can focus on new features for the next version.
The most common problem with CF is compatibility with non-core CCK modules.
Many patches have been proposed to fix issues with single modules (like Date and Content Taxonomy), but I think that we can't simply add them to the main module, because it would become in brief bloated and unmaintainable.
The best long term solution is to add a plug-in system to CF, so every widget has its own conditional settings that allow it to work. To do this, we need to identify the things that conditional fields needs to know to guarantee compatibility.
My ideas are still not clear on the subject, so contributions – also theoretical – are very welcome.
Comments
Comment #1
peterpoe CreditAttribution: peterpoe commentedA possible approach was outlined here #227416: Custom conditional fields.
Comment #2
Bilmar CreditAttribution: Bilmar commentedsubscibing - will be available for any future testing if required.
thanks
Comment #3
rburgundy CreditAttribution: rburgundy commented+1 subscribing
Comment #4
benone CreditAttribution: benone commented+
Comment #5
robby.smith CreditAttribution: robby.smith commented+1 this is the last feature stopping me from launching my new website. looking forward to updates
Comment #6
easp CreditAttribution: easp commentedsubscribing
Comment #7
YK85 CreditAttribution: YK85 commented+1 subscribing
Comment #8
capellicFor those looking for a solution and for those contemplating how to build it out, some consideration may give given to the Rules module and how it can solve problems. In my case, I had a controlling field to show/hide a Link field and FileField.
The case and solution are here:
http://drupal.org/node/596612
Comment #9
YK85 CreditAttribution: YK85 commentedHello,
I was wondering if all the current compatibility fixes for 2.x is related to the develpment of this plugin system?
Thanks!
Comment #10
peterpoe CreditAttribution: peterpoe commented#9: no, they were easy abstractions that do not include any module-specific code. Look what I did for allowed values (copying cck):
This isn't only for Content Taxonomy, but also for any other module that uses the convention MODULE_NAME_allowed_values.
Comment #11
clashar CreditAttribution: clashar commentedsubscribe
would be super to see the compatibility of Conditional Fields with Multigroup
Comment #12
shopdogg CreditAttribution: shopdogg commentedsubscribe
Comment #13
robby.smith CreditAttribution: robby.smith commentedhello, I was wondering if there has been any further development in this area?
should we post in drupal module forum for help in this development for conditional fields?
great module and hope to see this module continue to get better!
thanks!
Comment #14
locomo CreditAttribution: locomo commented+1 would love this functionality.. particularly for imagefield
Comment #15
kscheirerHow about at least adding support for the standard taxonomy module? That seems like a natural for use as a controlling field.
Comment #16
pdevillo CreditAttribution: pdevillo commentedSupport for standard taxonomies as a controlling field would save my day!
Comment #17
pdevillo CreditAttribution: pdevillo commentedI would love to have the ability to choose values from multiple controlling fields - right now we are limited to one:
example: if field1 value = a and field2 value = c show the conditional field.
Comment #18
YK85 CreditAttribution: YK85 commentedHi Peterpoe,
I was wondering if you have had time to develop the 3.x version you mentioned a few months back?
Really looking for the AND/OR conditional fields support.
Regards
Comment #19
Swipular CreditAttribution: Swipular commented+1 subscribing
Comment #20
achtonSubscribing too. Any status updates?
Comment #21
davidwhthomas CreditAttribution: davidwhthomas commentedI'm looking for taxonomy / content_taxonomy support, any general thoughts on the process / what would need to change to add this support?
Happy to put together a patch.
DT
Comment #22
kenorb CreditAttribution: kenorb commented+1
Comment #23
joeysantiago CreditAttribution: joeysantiago commentedI'd like to have fields depending on taxonomy terms too... :)
Comment #24
Zuzuesque CreditAttribution: Zuzuesque commentedTaxonomy support would be awsome. I am more than willing to test too, but I am not good enough coding to help much with patches I am afraid.
Comment #25
huba CreditAttribution: huba commentedsubscribing
Comment #26
zet CreditAttribution: zet commented+1 for core user Profile registration/edit fields
Comment #27
jonathanmd CreditAttribution: jonathanmd commented+1
Comment #28
fourmi4x CreditAttribution: fourmi4x commentedSuscribing, would love to have compatibility with Link module, to solve the "required" problem mentioned here : http://drupal.org/node/549362
Comment #29
fourmi4x CreditAttribution: fourmi4x commentedOk I've found a quick fix for the problem related to the validation of required non-core conditional cck fields.
It works at least for the Link module, but should work for a bunch of other "CCK field modules" too.
There was 2 problems:
- Error when the required conditional field is not visible (condition has not been triggered), asking for filling it in.
- Error when the required conditional field is visible (condition has been triggered), asking for filling it in.
So basically it was not working at all :)
- First problem can be fixed with http://drupal.org/node/919348#comment-4543638
- Second problem can be fixed by modifying the conditional_fields.module file:
In 6.x-2.x-dev, at line 996, add the lines between the comments:
With these two fixes I finally get a conditional required link field to work!
Comment #30
Encarte CreditAttribution: Encarte commentedsubscribe
Comment #31
nclavaud CreditAttribution: nclavaud commentedsame dirty hack for CCK Email Field, works great :
Comment #32
Drupa1ish CreditAttribution: Drupa1ish commentedVersion 7.x-3.x-dev works by default with https://drupal.org/project/rolereference and https://drupal.org/project/entityreference ( select list widget tested so far)
Comment #33
kscheirerAs EuroDomenii mentioned, using 7.x-3x.dev works great with Taxonomy, thanks!
Comment #34
Honza Pobořil CreditAttribution: Honza Pobořil as a volunteer commentedIs there some guide how to add support for some other widget? Or at least list what should work (to decide if it is for bug report or feature request)?
Comment #35
Honza Pobořil CreditAttribution: Honza Pobořil as a volunteer commentedIdea: Will be more user friendly if the UI can tell user if this widget is supporter or not.
Comment #36
dqdThanks for the report and all the efforts in here. But due to inactivity in this issue for some years and because of the upcoming EOL of Drupal 7, I will close this issue on the way by cleaning up the issue queue.
Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others on this outdated version.
If you think this issue or missing feature should be addressed in a newer Drupal core 8 and above compatible version of this project, then please file a new issue to the latest dev.