Closed (duplicate)
Project:
Hierarchical Select
Version:
5.x-3.0-rc7
Component:
Code - Content Taxonomy Views
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2008 at 12:27 UTC
Updated:
4 Apr 2009 at 16:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
plan9 commentedIs anyone else experiencing this problem?
Comment #2
plan9 commentedI am attaching screenshots of a HS settings pane for a view and the resulting View. As you can see: HS views settings are not being honoured - resize option is disabled yet it still appears.
I have tried this on 2 separate Drupal 5.x installs, with the same results.
This could be a views issue of course.
Comment #3
plan9 commentedCould somebody please confirm that they are able to control the resize appearance of HS in a view?
Thanks
Comment #4
plan9 commentedI've found that this behaviour is not limited to the resize option: in fact none of the HS options accessed via a views edit page are being honoured. Does anyone know where these settings are stored in the database?
Comment #5
pan0s commentedim experiencing the same problem here....
Comment #6
plan9 commentedAre you using HS in conjunction with Content Taxonomy?
Comment #7
pan0s commentedyeap...
more over when i go and chance my prefs of the exposed filter (in its own HS config) i get the following error :
i cant really chance anything right now ...
Comment #8
plan9 commentedThanks pan0s for confirming this, I will go ahead and open this as a bug with the HS Widget. All I can advise you is not to waste any more time trying to adjust the settings - currently nothing will disable the resize option. There seem to be a few issues going on between Content taxonomy and the HS. I guess the re-size preference not being honored is pretty low down on the priories list. My main concern is Term Lineage not being saved which for my site is pretty disastrous. I've posted info and a call for paid support on this here: http://drupal.org/node/362655 and here: http://drupal.org/node/363570
Comment #9
plan9 commentedUpdating this thread from support request to (minor) bug report
Comment #10
pan0s commentednp but plan9 ....
im turning towards the conditional fields module and im asking for their use as exposed filters in views (paid task)...it would b perfect!!!!!
EDIT : i ll finally stick with HS ... :P
Comment #11
wim leersThis has been fixed in http://drupal.org/cvs?commit=180082 via http://drupal.org/node/340827#comment-1327312.
Comment #12
konordo commentedComment #13
wim leersDon't change the status please. Especially not without arguments.