Simple hierarchical select and conditional field are not working together?

Added a states handler for conditional fields to SHS.

Thanks for your reply. I have again tried it with
Drupal: 7.24
conditional field: 7.x-3.0-alpha1
SHS: 7.x-1.x-dev (18th Dec 2013)

but it is still not working. However, I have noticed that handler was added in shs.module file. Unable to figure out the issue. Please if anyone can help me in this issue.

thanking you again.

I managed to get this working by placing the code below inside the updateFieldValue function in shs.js:

$field_orig.trigger('change');

I also had to manually adjust the dependee selector inside the "Advanced edit context settings" fieldset in the conditional field module, because this was being saved incorrectly.

I tested it with latest dev versions of both modules and got following errors:

    Notice: Array to string conversion in conditional_fields_form_after_build() (line 534 of ../conditional_fields/conditional_fields.module).
    Notice: Array to string conversion in conditional_fields_form_after_build() (line 534 of ../conditional_fields/conditional_fields.module).
    Notice: Undefined index: tid in shs_conditional_fields_states_handler_shs() (line 195 of ../shs/shs.module).

So I think this should be marked as active.

Hi Adam,

Same trouble, between SHS and conditional fields...

In #4, you explained :

I managed to get this working by placing the code below inside the updateFieldValue function in shs.js:

$field_orig.trigger('change');

I also had to manually adjust the dependee selector inside the "Advanced edit context settings" fieldset in the conditional field module, because this was being saved incorrectly.

Could you give me more details (where to place the

$field_orig.trigger('change');

in shs.js) ?

What did you mean when you explained in "adjust the dependee selector" ?

Thanks in advance !

Regards.
From

Hi Frommarcq

I have attached a patch for altering the js file.

With regards to changing the conditional fields selector. Go into manage dependencies and navigate to the Advanced edit context settings fieldset. I have added a screenshot of the selector that I used to make this work.

Let me know if you have any difficulties and I will help you out.

Adam

Still not working on mine.

Hi Adam,

Thank you for this patch. I think you use the "dev" version. So I installed it too. I followed your instructions, without any change :

the dependant is always displayed, even if the dependee ("field_rubrique") is different of "2" (or empty).

If I change the widget to "select list" instead of "shs" (and remove '[name="field_rubrique[%lang][%key][%tid]"]' from "Custom jQuery selector for dependee" field, the dependant is only displayed if the dependee is equal to "2".

Here's the field dependency's screenshot (maybe it is wrong ?)

Regards.

From

Hi,
Anyone have SHS working with Conditional Fields normally?
Thanks for sharing how to than.
greetings, Martijn

Hi!

I have the very same probleme here. The interesting thing about my version is that I'm not using any SHS widget type either in the dependent or the dependee fields. In my content type, I have a term reference field, which is using SHS as widget, and I have two other fields, one is a simple Logical field with Yes and No options and the other one is an Entity Reference which has two values and is only active when the Logical field is set to Yes.
I'm not an experienced coder, but I guess SHS has something to do with my Entity Reference field because I could select SHS as a widget type there (but I did not... It is an Autocomplete textbox and it refers other ones from the same content type it's in). Or maybe when I'm trying to add a new one of that content type, SHS and Conditional Fields detect each other and just droping the error messages mentioned in the fifth comment.

I'm fairly new to Drupal, and I don't know if it's the key to solve this issue, but I hope there is someone out there with a solution. And I hope it helps a bit.

I had the same problem as #12. Error logs showed a fatal error triggered at line 195 of shs.module:

PHP Fatal error:  Cannot use string offset as an array in /var/www/SITENAME/sites/all/modules/contrib/shs/shs.module on line 195

I managed to fix / work around the error using the patch attached, but to be honest, I don't have a clue what the shs_conditional_fields_states_handler_shs() function is supposed to do and I cannot guarantee that it will solve anyone's problem except my own :-)

Thanks marcvangend!
It solved my problem partially. I don't get the 3rd notice described in comment #5 but the other two is still shown. I have no functional problems though. Definitely one step closer. :)

Thanks for the feedback, smallgab. You're probably right, in my case I only got the 3rd notice so I didn't fix the other two.

The issue in #13 came up for me recently on a node form for a content type that did not have a term reference field much less a SHS widget. I have no idea why it was an issue there but I do use conditional fields heavily on this content type so maybe its related. The patch in #13 fixed the issue. I did not reroll it since it was just 2 new lines of code but I can if needed.

I have the same/similar problem...im using profile2 with 2 different profiles and added a shs-widget in one profile to choose the state/land/region...the funny thing: the error message also appears when editing the second profile, where no shs-widget is used. I do not use the conditions to hide or show the shs-widget but the errors appear in the profile2-edit-form. For every condition set i get 2 errors:

Notice: Array to string conversion in conditional_fields_form_after_build() (Zeile 547

#13 resolved the third error message, but the other two still remain...is there anything in progress or any idea where this bug may be fixed?

Hi all.

I tried to combine #7, #13 patches with my solution of Notice: Array to string conversion in conditional_fields_form_after_build() (line 547 of /var/www/drupal/sites/all/modules/contrib/conditional_fields/conditional_fields.module). error when shs and conditional fields are both enabled on the site (notice occurs on node add page). I use conditional fields version 7.x-3.0-alpha1 and shs version 7.x-1.6+56-dev. And this patch resolves notices and warnings.

I use the latest dev version which is just missing this part of the patch:

diff --git a/js/shs.js b/js/shs.js
index 7d08ff6..15befa4 100644
--- a/js/shs.js
+++ b/js/shs.js
@@ -538,6 +538,7 @@
           $field_orig.val(new_val);
         }
       }
+      $field_orig.trigger('change');
     }
   }

Although I added this javascript part the field which should be just visible if a specific value in my shs field is chosen is visible all the time. The other patches seem to be merged to current dev version?!

The array to string conversion notice seem to be a known issue with array comparing PHP function (https://bugs.php.net/bug.php?id=60198)... when an shs field is used as dependee the arrays checked in

if (array_intersect_assoc($handler_conditions, $dependee_form_field) == $handler_conditions) {
            $handler($dependee_form_field, $dependee_form_state, $options, $state);
          }

(conditional_fields.module, line 547)

have a nested array instead of a simple key/ value pair. This leads to this notice.

have a nested array instead of a simple key/ value pair. This leads to this notice.

yep. that's why there is

-      array(
-        'tid' => array(
-          '#type' => 'select',
-        ),
+      'tid' => array(
+        '#type' => 'select',

in this patch.

Although I added this javascript part the field which should be just visible if a specific value in my shs field is chosen is visible all the time.

I wanted to resolve notices and warning when shs and conditional fields are enabled. And at least warnings and norices are fixed.

Added 'Steps to Reproduce' section for easier review.

Patch #18 worked perfect for me

+++ b/shs.module
@@ -179,10 +179,8 @@ function shs_field_views_data_alter(&$result, &$field, $module) {
-      array(
-        'tid' => array(
...
-        ),
+      'tid' => array(
+        '#type' => 'select',

This is not correct, as the dependee form field is nested multiple times.
Debug into conditional_fields_form_after_build() and have a look on foreach ($state_handlers as $handler => $handler_conditions) { ... }. With this modification, the state handler defined in SHS is never called.
The PHP notice is caused by array_intersect_assoc() which does not work well with multi-dimensional arrays. See http://stackoverflow.com/q/19965438.

Added a (somehow hacky) fix so SHS should work with Conditional fields. To get rid of the PHP notice you will need to patch Conditional fields. See #2682015: Array to string conversion in conditional_fields_form_after_build().

For me the latest dev version still didn't work properly. It seems that the old state selector remains in the array and needs to be unset().
See the attached patch.

Patch #29 works for me on the latest dev version.

This only works if you're using the deepest level term AND setting your dependency value via the "insert value from widget" rather than the "set of values" options.

If you want the condition to be based on the highest level parent(which would have to be done via the "any of these values(OR)" setting) so that the conditional field will show for ANY of the children of a particular tree, it will not work.

It will also fail to work via "insert value from widget" if you are not forcing deepest level selection but the dependency term exists in the first level of the tree and the user goes deeper.

Same exact issue happens for the 8.x version

Is there a solution for drupal 8 version?

+1 for Drupal 8 version!

I was able to make it work on Drupal 8 by setting the Values input mode as Set of values.

Hi, Great this is also working for Drupal 8! But probably no maintainer anymore...
greetings,