i have created one vocabulary,
location having HS enabled, with options enabled for "Save term lineage".

My Vocabulary have hierarchy as,
- location
- country
-usa
-alamba

Now i have created one view where i want to show the hierarchical select filter(exposed) the one user can select.
1. in the filter option i have enabled option for filter Taxonomy: Term
2. vocab is location as mentioned above.
3. selection type is Hierarchical Select.
ISSUE : when on update i select "Select terms from vocabulary Location: " i am getting error as "Received an invalid response from the server."

Am i missing anything in the configuration?

Comments

shima’s picture

shima CreditAttribution: shima commented

I love this module & if I can use it many problems clear for me :) but I have the same problem and I search for solve this problem but I didn't found any useful post :(

pleas help us

briand44’s picture

briand44 CreditAttribution: briand44 commented

I was having the same problem and found out that it was a form override in my template.php file that was causing the error. My form override was changing the text on the submit button and re-rendering the form. Try changing your theme and see if you still get the error. Hope this helps.

jergason’s picture

jergason CreditAttribution: jergason commented
Status: Active » Needs review

I was having this problem when trying to expose a Taxonomy filter in Views. I had added, configured, and exposed the filter without saving my view, and was testing the filter in the Views live preview. Every time I selected an element, I got the "Received an invalid response from the server" error. However, when I clicked "Save" to save the view, the error disappeared. This is on a development install of Drupal 6.13 with tons of modules installed an enabled, and I have not confirmed this behavior on a vanilla version. I will when I have time.
Long story short, if you are getting this problem in an exposed filter on a view, try saving the view and testing again.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers commented
Category: bug » support
Status: Needs review » Fixed

Thanks for the answer jergason!

bensemmel’s picture

bensemmel CreditAttribution: bensemmel commented

Thank you jergason, saving helped for me as well!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

VVVi’s picture

VVVi CreditAttribution: VVVi commented

Thanks jergason, you helped me also!

I have used Drupal 6.16, Views 6.x-2.10, Hierarchical Select 6.x-3.1

pinkonomy’s picture

pinkonomy CreditAttribution: pinkonomy commented

Unfortunately I still have this problem on a Acquia Commons 2.2 installation.
I tried saving the view but didn't help at all.
Any other suggestions?
Thanks

pinkonomy’s picture

pinkonomy CreditAttribution: pinkonomy commented
Status: Closed (fixed) » Active

Unfortunately I still have this problem on a Acquia Commons 2.2 installation.
I tried saving the view but didn't help at all.
Any other suggestions?
Thanks

BenMirkhah’s picture

BenMirkhah CreditAttribution: BenMirkhah commented

I had the same problem, spent a few hours playing with it until I accidentally found a fix, make sure to create your exposed filter on the DEFAULT display and not on block/page, mine was on a page display and I kept getting the "Received an invalid response from the server" error because the HS ajax call was getting a 404 trying to reach ( http://mysite.com/hs_taxonomy_views_json/taxonomy_term/page_1 ) where page_1 is the display id, now it gets the data from http://mysite.com/hs_taxonomy_views_json/taxonomy_term/default

Kars-T’s picture

Kars-T CreditAttribution: Kars-T commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.