Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I tried to set up the Hierarchical select module to select an exposed filter of a view,but it returns an error.Could anyone help on this?
Thanks
Comments
Comment #1
pinkonomy CreditAttribution: pinkonomy commentedIs there any other option apart from Hierarchical select for Taxonomy Terms?
Comment #2
pinkonomy CreditAttribution: pinkonomy commentedWhen I select a Taxonomy Term that has children as a views exposed filter,I take the error message: "Received an invalid response from the server".
Any suggestions for this?
Comment #3
lightsurge CreditAttribution: lightsurge commentedI remember having this problem before... When I had taxonomy relationships in a view, and some of the content displayed by that view didn't have at least 1 term attached to it from the vocabularies involved in the query, I got exactly the same problem.
In the end I couldn't solve it, but as it turned out I wanted to make users select at least one term from each vocabulary anyway when creating content, so I ignored the problem.
Comment #4
beez CreditAttribution: beez commentedFor me there was an access permissions problem particular to Drupal Commons and Hierarchical Select User Terms. I was attempting to use a two-deep taxonomy hierarchy similar to Country->City. I made this a required field during registration. First the user selects Country, then a list of cities becomes available, from which the user selects one. But I was getting "Received an invalid response from the server" error message after the user selected Country.
Apache logs showed the Hierarchical Select field was making a call to server to the Apache server (http://mysite.com/site/hierarchical_select_json). That path was not accessible because I had Site Configuration->Drupal Commons settings set to "Force users to login" and the path "site/hierarchical_select_json" was not specified in "Allowed paths".
Adding "site/hierarchical_select_json" to Allowed paths solved the problem for me.
Comment #5
ezra-g CreditAttribution: ezra-g commentedWhile I agree that the implementation of the "require users to login" feature isn't ideal, I would expect that being logged in would prevent it from interrupting the Hierarchical Select callback.
Can you clarify why that's not the case?