Closed (fixed)
Project:
Conditional Fields
Version:
7.x-3.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Dec 2009 at 13:50 UTC
Updated:
1 Oct 2013 at 22:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Bilmar commentedfyi! http://webchick.net/node/74
I look forward to helping with any testing required.
Thanks very much in advance.
Comment #2
rburgundy commentedDrupal 7 Alpha 1 has been released =)
http://drupal.org/drupal-7.0-alpha1
Can't wait to take conditional fields for a spin in drupal 7!
Comment #3
peterpoe commentedWow for Drupal 7! I bet the new state API #557272: FAPI: JavaScript States system will make conditional fields so easy to implement it will be almost useless!
Comment #4
Bilmar commentedwow, Drupal 7 is going to be awesome =)
Comment #5
BenK commentedSubscribing.... +1 for Conditional Fields in D7!
Comment #6
YK85 commented+1 subscribing
Comment #7
rburgundy commentedUpdate: Drupal 7.0 Alpha 2 has been released (http://drupal.org/drupal-7.0-alpha2)
Comment #8
robby.smith commented+1 subscribing
any plans for this in the near future?
Comment #9
xjmTracking.
Comment #10
darora commentedsubscribing
Comment #11
servantleader commentedHope this happens soon. Will only need to port the UI. The low level stuff is covered with the #states system. Great session on this at drupalconSF : http://sf2010.drupal.org/conference/sessions/instant-dynamic-forms-states
Comment #12
Encarte commentedsubscribe
Comment #13
sam mooresubscribe
Comment #14
Fidelix commentedSubscribing...
Comment #15
EndEd commented+1
Comment #16
vhwouter commented+1
Comment #17
Shadlington commented+1
Comment #18
tesmon commentedSubscribing!
Comment #19
fuzzy_texan commented+1
Comment #20
ximo commentedAny news? D7 is now in beta1, if there was a D7 branch for Conditional Fields I'd be happy to test it and help out.
Comment #21
Coupon Code Swap commented+1 subscribe
Comment #22
tsvenson commented+1 for Drupal 7 version, would be most useful in some of the projects I am working on.
Comment #23
vitok-dupe commentedsubscribe
Comment #24
gorillaz.f commentedsubscribe
Comment #25
dgastudio commentedsubscribe
Comment #26
thekevinday commentedsubscribe
Comment #27
sthzg commentedsubscribe
Comment #28
jzornig commentedsubscribe
Comment #29
maheve commentedsubscribe
Comment #30
simplyManu commentedsubscribe
Comment #31
avo_liao commentedsuscribe
Comment #32
vitok-dupe commentedWhen we saw Conditional Fields for D7? D7 is now released...
Comment #33
design.er commentedoh yes, we need this module for an outstanding D7 project. is there a timeline/plan for a release?
Comment #34
peronas commentedsubscribe
Comment #35
fresnizky commented+1 subscribe
Comment #36
podaroksubscribe
Comment #37
ccheu commentedsubscribe
Comment #38
jcarlson34 commentedSubscribing
Comment #39
JockeL commentedSubscribing
Comment #40
olamaekle commentedSubscribing as well. Are you working on it?
Comment #41
kbond commentedsubscribe
Comment #42
webankit commented+1 any work going on?
Comment #43
jcarlson34 commentedpeterpoe's link in #3 above led me to the API documentaion for the 'states' conditional JavaScript options for forms in D7:
http://api.drupal.org/api/drupal/includes--common.inc/function/drupal_pr....
It might be a good place to start until Conditional Fields is ported.
Also there is a good example of how to use this in the Examples module.
Comment #44
anruethertrupal, if each subsciber would support you with 10 bucks you would do the port?? ;)
Honestly, CF is one of the most useful and practical modules i used until now...
Comment #45
Bilmar commentedIf I had the skills, I'd do it for free because this module and the community is so awesome =) Unfortunately, I have no programming skills. I think we have many potential testers, and we can only patiently wait for someone to take the lead on the port.
Comment #46
carwin commentedsubscribe. I'd also chip in $10 for this.
Comment #47
anruetherOh, right, we should offer that to peterpoe :)
Comment #48
alioso commentedSubscribing...
Comment #49
felipe commented+1!
Comment #50
NathanM commented+1 subscribing.
Comment #51
ropaolle commentedSubscribe
Comment #52
Ciprian Oancia commentedSubscribe
Comment #53
Breakerandi commentedsubscribe
Comment #54
bryancasler commentedsubscribe
Comment #55
carwin commentedsubscribe $10 too
Comment #56
peem83 commentedI've made already alternative module for drupal 7 which contain the same functionality what conditional fields does and even more, but I'm still waiting for acceptance, it takes already more than 3 weeks :/
Comment #57
vitok-dupe commentedpeem83
Where we can download your work right now?
Comment #58
design.er commentedhttp://drupal.org/node/1025338#comment-4073558
Comment #59
vitok-dupe commenteddesign.er thx!
peem83 nice one!!! field_conditional_state awesome work!
Comment #60
clashar commentedsubscribe
Comment #61
no2e commentedsubscribe
Comment #62
skottler commentedtrupal218, I am willing to port the module to D7. Its an incredibly import module for webform and content profile users.
Please contact me and let's do this!
Comment #63
YK85 commentedI think we should wait to see if Conditional States will have an upgrade path from Drupal 6 Conditional Fields (http://drupal.org/sandbox/peem/1073388). I just asked peem83 by message and waiting for a reply.
If there is a chance of an upgrade path, then I think work will need to be put into D6 Conditional Fields to match the functionalities in Conditional States which seems to be already far more advanced, such as #719068: show if ANY of controller fields are selected (OR vs AND controllers)
What do you all think? Is this possible?
Conditional States cannot be backported to D6 as Drupal 6 does not have #states
But I hope Conditional Fields can be further developed to support the advanced functionalities that would make the module even more powerful than it is now.
Thank you very much
Comment #64
z3cka commentedsubscribe
Comment #65
YK85 commentedpeem83 confirmed via email that there will be no upgrade path to Field Conditional States module.
@Skottler - have you started your work on D7 CF?
Comment #66
skottler commented@YK85, not yet since there has been so much chatter around the subject. Now that we have confirmation, I will get rolling!
Comment #67
wcarpent commented@skottler, Thanks for your initiative and I look forward to implementing what you come up with!
Comment #68
kumy commentedsubscribe
Comment #69
Jerome F commentedsubscribing (tired of subscribing ? http://drupal.org/node/34496 - http://3281d.com/2009/03/27/death-to-subscribe-comments)
Comment #70
shiraz dindarlol.
subscribe
Comment #71
Stefan Haas commentedsubscribe
Comment #72
Anonymous (not verified) commentedsubscribe
Comment #73
jimmynail commentedsubscribe
Comment #74
geek-merlingood time to join forces:
Conditional fields: #658012: Plans for Drupal 7 Conditional Fields, #281757: Dependent field module vs Conditional fields?
Dependent Field: #1014984: Dependent Fields: D7 Port, #1036226: Difference with Conditional Fields module
Comment #75
geek-merlingood time to join forces:
Conditional fields: #658012: Plans for Drupal 7 Conditional Fields, #281757: Dependent field module vs Conditional fields?
Dependent Field: #1014984: Dependent Fields: D7 Port, #1036226: Difference with Conditional Fields module
Comment #76
jdufaur commentedSubscribe
Comment #77
jarush commentedany update?
Comment #78
tesmon commentedsubscribing
Comment #79
Golem07 commentedsubscribing
Comment #80
robloachpeem83's Field conditional state should be Conditional Fields in Drupal 7. We should move that into the Drupal 7 branch of Conditional Fields and change its namespace. Seriously, that module rules, peem83 blew my mind.
Comment #81
bryancasler commentedI agree, I've been using that module as well and I have't had a singlee problem.
Comment #82
Breakerandi commentedI totally agree!
Comment #83
Jerome F commentedI tested it too and it works well.
EDIT : Peem83' module is very nice and good to go as far as I know, all the issues I found have been solved now.
Comment #84
midmood commentedsubscribe
Comment #85
tesmon commentedsubscribe
Comment #86
tesmon commentedsubscribe
Comment #87
patoshi commentedSUBSRIBEEE
Comment #88
BazzeFTW commentedI cloned the field_conditional_state from peem's repository and it works fine, BUT the issue I found is that if you make a field compulsory that, for example, is only shown if the previous field is marked as 'yes' and the field isn't marked as 'yes', then it won't be able to save the node since no value for the field is provided.
Comment #89
Jerome F commented@BazzeFTW did you post an issue to report that? (I didn't see any issue in its issue queue http://drupal.org/project/issues/1073388)
Comment #90
CUclimber commentedSubscribing. This would be a *massive* help to my newest site.
Comment #91
rogical commented+1
Comment #92
andrebonfanti commented+1
Comment #93
peterpoe commentedWe now have a dev channel for Drupal 7!
- Based on entities
- Leverages an updated version of the States API currently in development that will probably be included in a later D7 release: #735528: FAPI #states: Fix conditionals to allow OR and XOR constructions
For testing: Users with the “administer site configuration” permission (will change) can administer dependencies at admin/structure/dependencies.
There is still much work to do but most of the basic functionality is already there.
About Field Conditional States: when I learned about the module, cf3 was almost ready, sitting in my hard drive waiting for a couple of days of spare time to make it usable for testing. I decided to go forward with my code, but we could integrate it with ideas from FCS.
Marking this issue as fixed. Please report bugs in their own separate issues.
Comment #94
clashar commentedThank you for good news!
I would like to see more documentation, for example now there are following available options for dependencies:
Enabled
Disabled
Visible
Invisible
Checked
Unchecked
Value
I'm not sure about difference for example between "Enabled" and "Checked"
Comment #95
clashar commentedand another question if there is compatibility problem between one module and CF where should I post a bug, in other module's issue bug or in CF issue bug?
Comment #96
peterpoe commented#94: Documentation is coming soon. The options you mentioned are the states implemented by the States API: http://api.drupal.org/api/drupal/includes--common.inc/function/drupal_pr...
#95: It depends. If a field type not from core, like node reference, is not handled properly, you should probably create an issue under CF.
Comment #97
jackbravo commented@peterpoe. Have you seen the interface for field conditional state?
Here is a screenshot. Sorry for some parts being in spanish =P.
I'm editing the "Tipo" field of one of my content types. One of the tabs for this field is "Conditional States" which lets me add conditions like:
- The field tipo is "hidden" when field is set to
.
Right now seems like the dependee field can only be a field with options (select box, boolean, checkboxes, etc) and not a text field for example. And you can add several conditions with OR or AND.
Comment #99
lencrockett commentedLooking forward to this release!
Comment #100
Tamanda commentedVery important module. Thanks for the hard work. Waiting anxiously for its D7 stable version.
Comment #101
john franklin commentedAny chance of a full 7.x release sometime soon?