Hi Wim, I understand that you probably no longer support Drupal 5 anymore, but I'm hoping you might have some advice for me. I have HS 5.x-3.4 with Taxonomy and Taxonomy Views enabled installed on Drupal 5.23 and Views 5.x-1.8 - in other words all latest versions of all components for D5.

HS seems to work fine when editing a node, and it seems to be functioning correctly when the view is first presented. In my search View I have 3 HS dropdowns for different taxonomy terms, and HS appears to behave as expected. When the view is submitted, the correct results are returned, but two of the 3 HS elements always have the "You don't have Javascript enabled" message displayed.

Worse, the form seems to be broken from that point on. Submitting the view search again without making any changes results in no items returned. Making a selection in a HS dropdown and clicking Update leads to unpredictable results, from making the wrong selection, to replacing its contents with that of a different HS element.

I have followed the D6 thread at http://drupal.org/node/734178 and do not seem to have duplicated JS files, I have updated jquery_update, I don't have caching turned on, the system weights seem to be correct (actually I had to manually update them since all the HS modules installed themselves with the same weight), I'm not using custom field validation, I'm not using Application Toolbar, and I'm not using AHAH. It's just a view with exposed taxonomy filters.

Any ideas?

Comments

scott.whittaker’s picture

Just a quick update: with javascript actually turned off in the browser, the dropdown update behaviour is buggy too. No matter what you select in a HS dropdown, when the update button is pressed ALL HS fields default to the first value which is not < all > or < none > making it impossible to keep default selection values of < none >, < all > or even allow any selection other than the first item in each level of the hierarchy.

Something is pretty messed up.

Wim Leers’s picture

Status: Active » Closed (won't fix)

The Drupal 5 version is no longer supported. Sorry. See the project page:

The Drupal 5 version has been maintained for years and has received feature equality with the Drupal 6 version. This has cost me a *lot* of my free time. Very few module maintainers have done this. But with Drupal 5 unsupported since the Drupal 7 release, the Drupal 5 release will also no longer be maintained. Only security fixes will still be applied. But with a very solid security track record, I don't expect that to be necessary.

scott.whittaker’s picture

Yes, I completely understand. Any hints you can give me at all?

scott.whittaker’s picture

OK I fixed it. I followed all the related issues for D5 and D6 and finally found the answer in a patch for the D6 version here. Manually copying and pasting the changed code into the D5 version at line 318 fixed it for me on D5.

 function hierarchical_select_process($element, $edit, &$form_state, $form) {
-  if (!isset($element['#value']['hsid'])) {
+  if (!is_array($element['#value']) || !isset($element['#value']['hsid'])) {

I'll leave it up to you to decide if it's worth updating the D5 version, but this one line update changed it from being unusable to awesome. Cheers!

Wim Leers’s picture

Status: Closed (won't fix) » Postponed (maintainer needs more info)

Please post a patch then :)

1kenthomas’s picture

Status: Postponed (maintainer needs more info) » Needs review

For one line? Come on :).

stefan.r’s picture

Status: Needs review » Closed (won't fix)

5.x issue without activity for over 3 years, closing.

Please reopen if this is still an issue in 7.x.