Hello,
I'm trying to use HS (7.x-3.0-alpha2) with my taxonomy items and Drupal 7.7 : the first level items appears correctly but when I've tried to click on one item to display sub-levels, I've got an error "Received an invalid response from the server".
Here is a list of the modules I've installed :
ACL 7.x-1.0-rc1
Administration menu 7.x-3.0-rc1
Advanced Forum 7.x-2.0-alpha3
CAPTCHA 7.x-1.0-alpha3
Chain Menu Access API 7.x-1.0
Chaos tool suite (ctools) 7.x-1.0-rc1
date 7.x-2.0-alpha3
field_group 7.x-1.0
field_permissions 7.x-1.0-alpha1
forum_access 7.x-1.0-beta1
hierarchical_select 7.x-3.0-alpha2
mailsystem 7.x-2.28
masquerade 7.x-1.0-rc3
messaging 7.x-1.0-alpha1
mimemail 7.x-1.x-dev (2011-jui-30)
notifications 7.x-1.0-alpha1
references 7.x-2.0-beta3
simplenews 7.x-1.x-dev (2011-juin-12)
views 7.x-3.x-dev (2011-aoû-17)
webform 7.x-3.12
Sorry for my english and thanks in advance for any help that you can provide
Comments
Comment #1
wim leersPlease try the latest dev snapshot. If that doesn't help, try disabling field_group and field_permissions for a minute.
Comment #2
wim leersAlso try #1160694: Received an Invalid Response from Server's patch. If that doesn't help, I'll need you to report back the exact AJAX response, like it is posted in #1160694: Received an Invalid Response from Server.
Comment #3
luluthegeek commentedThanks a lot.
Development release 7.x-3.x-dev (from 2011-Aug-10) solves the problem.
Comment #4
wim leersHurray! :)
Comment #6
amogiz commentedDid not for me .
Sorry to post in every page but I spend too many hours on this …
Comment #7
sebas5384 commentedHere still the same, the error persists :(
"Received an invalid response from the server."
Comment #8
sebas5384 commentedComment #9
kars-t commentedDear 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.