Hello,

Repeatable: Always

When does it happens:
Only when adding a new node of the specific content type provided by the ecommerce module ("Product") which uses a taxonomy vocabulary with more than one hierarchy level.

If I disable Javascript on this add a new node form and I use the "Update" button, it works as expected (content of the second taxonomy list is present and there is no error).

The edit form of a node of this content type does not cause this problem at all and works as expected.

How to reproduce it:
On a clean Drupal 6 install with only ecommerce (and its dependencies: ctools, rules, token, views, views_bulk_operations) and hierarchical_select. Enable the module "Store" (which will enable few others dependencies) and HS. Create a taxonomy, add 2 terms and make one the children of the other. Edit the taxonomy and tick "Use the Hierarchical Select form element for this vocabulary." and choose the ecommerce's node type named "Product" as one of the Content Types.

Now click on in the menu "Create content > Product", it offers two "sub-types" of the "Product" content type (which is most likely the source of the problem) : Generic Product and Shippable Product... You can ch0ose either, the problem will be the same on both. In the add form if you try to select the first taxonomy term of your vocabulary (which is the parent of the other term you created) it will issue the AJAX request for the data and then prompt you with the error "Received an invalid response from the server."

Possible cause
The ecommerce module provides this sort of subtype of content type because it offers different features (inventory management, etc.) in function of the subtype and to achieve this they use a different URL when you add a product (node) for the form than a typical node.
When you click on "Create content > Product" it goes to "/node/add/product/listing", then you need to choose between the two types of products "Generic Product" (/node/add/product/generic) or "Shippable Product" (/node/add/product/tangible). When usually the node add form URL is "/node/add/", so I guess this breaks the way HS is building the URL submitted through AJAX to retrieve the next hierarchical level.

One thing that makes it possible to use HS on a "Product" is to edit the content type setting and disable either one of the two "subtypes", then the add form URL is back to normal... but unfortunately it means that it's not possible to have more than one subtype at the same time which is not always possible.

I hope there is a way to integrate this possibility of a different node add form URL in HS because I feel that other modules can work the same way (with different URL). I wondered if this would be more appropriate in ecommerce issue queue but I figured that they were not breaking any convention in Drupal by adding parameters after the part of the node add form URL so maybe it's HS that should support this kind of paths.

#352510: HS and Ecommerce 6.x-4.x is probably the same issue, I found it in ecommerce queue but as I said I do not think ecommerce is doing something particularly wrong by having a custom node add URL.

Comments

Gold’s picture

Status: Active » Closed (won't fix)

Tidying up the issue queue. The 6.x version is no longer supported. Only reopen this if it also applies to the 7.x.