Unable to disable resize appearance in views. [#347213]

Comment	File	Size	Author
#2	HS_View_Settings.png	59.36 KB	plan9
#2	Resulting_HS_View.png	107.31 KB	plan9

Comment #1

plan9 CreditAttribution: plan9 commented 18 December 2008 at 22:38

Is anyone else experiencing this problem?

Log in or register to post comments

Comment #2

plan9 CreditAttribution: plan9 commented 5 January 2009 at 13:31

File	Size
Resulting_HS_View.png	107.31 KB
HS_View_Settings.png	59.36 KB

I 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.

Log in or register to post comments

Comment #3

plan9 CreditAttribution: plan9 commented 11 January 2009 at 17:30

Could somebody please confirm that they are able to control the resize appearance of HS in a view?

Thanks

Log in or register to post comments

Comment #4

plan9 CreditAttribution: plan9 commented 15 January 2009 at 20:21

I'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?

Log in or register to post comments

Comment #5

pan0s CreditAttribution: pan0s commented 24 January 2009 at 14:38

im experiencing the same problem here....

Log in or register to post comments

Comment #6

plan9 CreditAttribution: plan9 commented 24 January 2009 at 14:45

Are you using HS in conjunction with Content Taxonomy?

Log in or register to post comments

Comment #7

pan0s CreditAttribution: pan0s commented 24 January 2009 at 16:24

yeap...
more over when i go and chance my prefs of the exposed filter (in its own HS config) i get the following error :

Warning: Table 'watchdog' was not locked with LOCK TABLES query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '<em>Duplicate entry &amp;#039;hs_config_content-taxonomy-views-carsearch-field&amp;#039; for key 1\nquery: INSERT INTO variable (name, value) VALUES (&amp;#039;hs_config_content-taxonomy-views-carsearch-field_make&amp;#039;, &amp;#039;a:7:{s:9:\\&amp;quot;config_id\\&amp;quot;;s:43:\\&amp;quot;content-taxonomy-views-carsearch-field_make\\&amp;quot;;s:12:\\&amp;quot;save_lineage\\&amp;quot;;s:1:\\&amp;quot;0\\&amp;quot;;s:15:\\&amp;quot;enforce_deepest\\&amp;quot;;s:1:\\&amp;quot;1\\&amp;quot;;s:12:\\&amp;quot;entity_count\\&amp;quot;;s:1:\\&amp;quot;1\\&amp;quot;;s:9:\\&amp;quot;resizable\\&amp;quot;;s:1:\\&amp;quot;0\\&amp;quot;;s:12:\\&amp;quot;level_labels\\&amp;quot;;a:2:{s:6:\\&amp;quot;status\ in F:\VertrigoServ\www\d5\includes\database.mysql.inc on line 174

i cant really chance anything right now ...

Log in or register to post comments

Comment #8

plan9 CreditAttribution: plan9 commented 24 January 2009 at 17:44

Component:	Code - Content Taxonomy Views	» Code - Taxonomy Views
Category:	bug	» support
Priority:	Minor	» Normal

Thanks 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

Log in or register to post comments

Comment #9

plan9 CreditAttribution: plan9 commented 24 January 2009 at 17:36

Component:	Code - Taxonomy Views	» Code - Content Taxonomy Views
Category:	support	» bug
Priority:	Normal	» Minor

Updating this thread from support request to (minor) bug report

Log in or register to post comments

Comment #10

pan0s CreditAttribution: pan0s commented 22 February 2009 at 15:28

Component:	Code - Taxonomy Views	» Code - Content Taxonomy Views
Category:	support	» bug

np 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