Closed (outdated)
Project:
Conditional Fields
Version:
7.x-3.x-dev
Component:
Compatibility w/ other modules
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Jun 2011 at 22:24 UTC
Updated:
4 Mar 2024 at 01:49 UTC
Jump to comment: Most recent
Comments
Comment #1
mstrelan commentedNot sure that the original post makes sense, but +1, this is not working for location fields. I am using location 7.x-3.x-dev and trying to hide the location field based on the value of a taxonomy term field.
The description of my field dependency:
field_location is visible when field_exhibition_type has value "exhibition".Comment #2
mstrelan commentedAs a dependant field, is this as simple as:
Or is there more to it?
There is almost certainly much more to it for it to be a dependee.
Comment #3
peterpoe commentedNo patch, and the solution in #2 doesn't apply anymore.
Comment #4
ethanw commentedWhat's the current status of this issue? We're experiencing the same bug on a current project, any recommendations on where we might look to implement a fix?
Comment #5
Berliner-dupe commentedSame problem here.
When i use a Location CCK Field as "Dependent" and a checkbox-Field as Dependees and i fill out the Location Field then its only empty after Node Save. When i deactivate dependency for this field, it works correct.
Any news or tips available?
Comment #6
ikeigenwijs commentedstill an issue
using checkbox does not work.
Comment #7
ikeigenwijs commentedmaby add in .module +-line 886
case 'location':
$entity_property = 'field_item_location';
break;
field_item_location is exposed by location_entity.module and thats a part of Location module
Comment #8
nancydruI have this problem without Location_entity, so I think we can rule that out.
I suspect that the real issue is that Location is acting more like a field_group than a field. The node definition has only one field for the location, but when the node is edited, there are several fields, none of which is named "field_location" therefore they don't get acted upon.
Comment #9
nancydruAlso, I am using it with Inline Entity Form, so
hook_form_alter()may not be fired in this case.Comment #10
nancydruIf I go to the node in standard edit, the Conditional Fields stuff works just fine, but under Inline Entity Form, it does not.
Comment #11
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.