Tough the sandbox project was able do the same ...
plz help

Comments

mstrelan’s picture

Component: Code » Compatibility w/ other modules

Not 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".

mstrelan’s picture

Status: Active » Needs review

As a dependant field, is this as simple as:

--- sites/all/modules/conditional_fields/conditional_fields.module	(revision 9282)
+++ sites/all/modules/conditional_fields/conditional_fields.module	(working copy)
@@ -655,6 +655,7 @@
     case 'date_text':
     case 'date_popup':
     case 'link_field':
+    case 'location':
     case 'cck_select_other':
     case 'field_collection_embed':
     case 'field_collection_hidden':

Or is there more to it?

There is almost certainly much more to it for it to be a dependee.

peterpoe’s picture

Priority: Major » Normal
Status: Needs review » Active

No patch, and the solution in #2 doesn't apply anymore.

ethanw’s picture

What'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?

Berliner-dupe’s picture

Same 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?

ikeigenwijs’s picture

Issue summary: View changes

still an issue
using checkbox does not work.

ikeigenwijs’s picture

maby 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

NancyDru’s picture

I 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.

NancyDru’s picture

Priority: Normal » Major

Also, I am using it with Inline Entity Form, so hook_form_alter() may not be fired in this case.

NancyDru’s picture

If I go to the node in standard edit, the Conditional Fields stuff works just fine, but under Inline Entity Form, it does not.

dqd’s picture

Priority: Major » Normal
Status: Active » Closed (outdated)

Thanks 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.