Received an Invalid Response from Server

+1

Is this still happening with alpha 2?

still happening as of 7.x-3.x-dev (2011-Aug-02) build.

error is ->

Warning: Missing argument 2 for _hs_new_setting_ajax(), called in /sites/all/modules/hierarchical_select/hierarchical_select.module on line 346 and defined in _hs_new_setting_ajax() (line 437 of /sites/all/modules/hierarchical_select/hierarchical_select.module).

Please test the attached patch.

Thanks for the confirmation. Committed.

http://drupalcode.org/project/hierarchical_select.git/commit/6a3a3f1

Just upgraded to the latest -dev, and still has some issues ... no longer get the Invalid message when choosing the first term, but, also getting nothing for its child levels ...

If I go to the Second term, the child levels come up ... and if I then go *back* to the 1st term, *its* Children then comes up as well ...

Same effect if I go:

-> First Term -> -> First Term

it isn't until I go to First Term a second time that I get its children ...

Also, tried the 'allow user to add term' option ... when I go to choose '', I get the 'Invalid Server Response error again, but looking in my error_log file for the web server, I'm getting no actual error there ...

Got the same problem and never answer.
I had to stop my website because of this problem :(

I am looking for another solution and fell really disappointed.

Hope one day the author will help us to find the problem solution !

So this isnt entirely fixed, then?

fully functional my end

I have a weird edge case where this happens. If I use node-clone and clone a node, then am using hierarchical select and try to create a new term in the cloned node, I receive this error. If I cancel adding the new term, you can see that the new term was actually created, but it won't let you proceed if you don't cancel the new term creation.

Please delete this post. Meant to add to a different issue.

I am getting the same issue on the current stable release 7.x-3.0-alpha5. It's really annoying because this module is just what I need, but this bug renders it unusable for taxonomy selection. any ideas? I get it when using my side as Admin, editing a node

This issue isn't fixed
"Received an invalid response from the server."

This issue isn't fixed
"Received an invalid response from the server."

Is there anymore insight into this yet?

Any progress in this? Cos this module cant be used this way:/

I have managed to figure out that this happens for me when the Botcha module is installed.

I find that the issue "Received an invalid response from the server." is from the cron, since cron always removes the form_build_id from the table {cache_form}, which will make the form_build_id to be invalid.

https://drupal.org/node/1694574#comment-7450822

I find that the issue "Received an invalid response from the server." is from the cron, since cron always removes the form_build_id from the table {cache_form}, which will make the form_build_id to be invalid.

https://drupal.org/node/1694574#comment-7450822

I was seeing this error when trying to create new taxonomy terms which ended up being more closely related to #1293166: Whole node form is saved instead of widget form, possible data loss.

Still happening in alpha9 version.

@3magnus, how can we reproduce this issue?

I've been digging around about this issue and I've been able to decipher things a little. To reproduce the problem I used two or more different browsers. I log all of them in using the same account and stay on the homepage or user account page. I didn't display the hierarchical select form on all browsers just yet. First browser, go to the form and everything works. The next browser loads the form but gets the error this thread is about. I traced it using Charles to find that they are both receiving the same form_build_id. This might put things out of sequence and voila... empty response from the server.

UPDATE: A little more digging and it looks like the issue exists when the site is cached using Varnish.

You ought to exclude the pages with a hierarchical select widget from caching. Does that fix the issue for you?

Does anyone still have this issue in the latest version, and if yes are there any details on how to reproduce this?

Yes, issue is still there. Cant get past it. It works ok when setting up content type or setting up relations, but it fails when I try to use it in the node.

I get this issue too. Everything works fine in preview section of field widget setup, but fails on new node creation form.

I`ve figured out what was the problem. In my case it was caused by AdBlock+ in my browser.
I had a field with machine name "field_advertisement_category" and so the resulting url to ajax request was
"hierarchical_select_ajax/field_advertisement_category/und".
As I understand ABP was detecting word "advertisement" in ajax request and blocked it immediately without even letting jQuery to send request to the server. Disabling ABP solved issue, renaming the field for example to "field_announcement_category" solves issue either.
As far as I know some of antivirus programs have feature of ad blocking too.

Just wondering if this is still an issue.

@RealGecko has reported it was ABP that was getting in the way. Is anyone else on this still seeing the issue or has @RealGecko's discovery been a common thing for others too?

Just wanting to tidy up the issue queue a bit. If anyone is still experiencing this detailed descriptions to replicate would be appreciated.

I'm having this issue with users on OS X and using both Safari and Chrome. I'm going to try excluding the page from the cache.

I was having this issue while using 7.x-3.0-beta3 (getting the message "Received an invalid response from the server."). I just updated from 7.x-3.0-beta3 all the way to 7.x-3.0-beta6 and am not having the issue any more.

Thanks! Closing this issue for now. The error can appear for different reasons, so feel free to open a new issue if it occurs again.

@amogiz #9: Drupal modules are contrib community work, the "author" of a module is not responsible for making your life a breeze. She/He is rather a host of a project, which we all help together to make better. If you need something working out of the box or that an author of a module fixes your problem immediately, feel free to make him an offer.

@stefan.r: I sadly have to reopen the issue since there are still many random cases where this error appears. I try to fiddle out a summary since this error occured very often in connection with HS over the years but in very different situations. We maybe should get a birds eye view on this? I try to collect all issues and write a summary if it has any connection. At the moment the error occures here after applying this patch from this issue, but I am not sure if this is really related yet.

@diqidoq: can you confirm that the error occures after appling the patch #83 from this issue https://www.drupal.org/node/2128265 ?