'Received an invalid response from the server.' connected to permissions?

schvili - November 5, 2009 - 17:49
Project:Hierarchical Select
Version:6.x-3.x-dev
Component:Code - Content Taxonomy
Category:bug report
Priority:normal
Assigned:Unassigned
Status:postponed (maintainer needs more info)
Description

Hi Win.

Thank you for a great module! I got the same error as several others. Could it be connected to permissions?

Step by step:
Role: Admin
1. Install the needed modules
2. Create a new Content Type
3. Add a field in CCK that uses the Hierarchy Select widget.
4. Create new content
5. Select a term in the first level.
6. Next level expands (it works!)
7. Logout
8. Login as a 'authenticated' user, not admin
9. Create new content
10. Select a term in the first level of the hierarchy
11. Get the error message 'Received an invalid response from the server.'

Would be very grateful for support on this. We are planning to go live next week and would really like to have include you great module.

Matti

#1

esezako - November 6, 2009 - 16:28

I have the same problem, but with all users, include admin.

#2

bennos - November 21, 2009 - 05:39

Please provide a list of your modules an information of your enviroment.

there must be an incompatiblity with other taxonomy modules or with modules relatedt to sessions.

#3

lavjaman - November 23, 2009 - 14:32

same here when i use the default implementation of the hiearchy param of hs_smallhierarchy.module

$hierarchy = array(
    'win' => array(
      'label' => 'Windows',
      'children' => array(
        'xp'    => array('label' => 'XP'),
        'vista' => array(
          'label' => 'Vista',
          'children' => array(
            'x86' => array('label' => '32-bits'),
            'x64' => array('label' => '64-bits'),
          ),
        ),
      ),
    ),
  );

and the firebug console message:
Fatal error: Unsupported operand types in drupal-6.14/includes/common.inc on line 2877
this is the drupal_render() function

#4

khad - November 23, 2009 - 18:45

I get the same error, but only in nodes that have been newly created via the link that nodereference_url places in the referenced node. When I create the node via the "Create content" link (without preselecting the nodereference) everything works ok, the same when I open an existing node (where the nodereference field is not write-protected). Looking at the firebug output, all that I can see (I'm not a developer) is that in the defunct case, the "Params" tab shows just "q" while in the working case it shows "q hierarchical_select_json".
Hope that helps

#5

VDMi.Frans - November 26, 2009 - 09:27

I had the same error.

I noticed that the path that was queried is [lang-code]/hierarchical_select_json that gave a 404.
i redirected that to hierarchical_select_json and we are up and running.

Something totdo with the language selections?

#6

lavjaman - November 27, 2009 - 10:35
Status:active» needs work

#7

Wim Leers - November 27, 2009 - 12:20
Status:needs work» postponed (maintainer needs more info)

@VDMi.Frans: It's very well this is connected to using i18n. Can somebody please research that?

Also, can somebody reproduce the problem by following the steps posted by schvili?

#8

VDMi.Frans - November 27, 2009 - 15:28

Indeed!
It has todo with language selection other then english as default on admin/settings/language

Set the default language to dutch and it will do its request on nl/hierarchical_select_json. Set the default language to english and it will do the request on hierarchical_select_json.

I don't know enough of i18n to point you to code where the path is expanded. But i use this modules (and their dependencies) regarding internationalization and paths.

i18n
path_redirect
pathauto
transliteration
uploadpath
filefield_paths

Hope that helps.

#9

Wim Leers - November 27, 2009 - 16:36

I don't have the time to test those combinations. I know that just i18n works fine — because several people have posted patches to fix translation of terms in HS in Drupal 6 (it worked fine in 5, but changed in 6).

So, if you want to see this fixed, you're going to have track down which of those modules causes the problem. I can tell you with 99% certainty that pathauto, uploadpath and filefield_paths are not the causes, so I'd start with the other three modules.

 
 

Drupal is a registered trademark of Dries Buytaert.