Closed (fixed)
Project:
Hierarchical Select
Version:
5.x-3.0-beta1
Component:
Code - Content Taxonomy
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
29 Jun 2008 at 14:31 UTC
Updated:
23 Jul 2008 at 10:56 UTC
Hi,
I have updated HS to 5.x.3.0-beta1 and changed the file as per CVS http://drupal.org/project/cvs/172915
Problem.
If I set the HS as below, it crash and freeze the parent terms
Save lineage: Save only the deepest term
Level choice: Force the user to choose a term from a deepest level
$config = array(
'config_id' => 'content-taxonomy-field_t',
'save_lineage' => 0,
'enforce_deepest' => 1,
'node_count' => 0,
'level_labels' => array(
'status' => 0,
'labels' => array(
0 => '',
1 => '',
2 => '',
),
),
'dropbox' => array(
'status' => 0,
'title' => '',
'limit' => 0,
'reset_hs' => 1,
),
'editability' => array(
'status' => 0,
'item_types' => array(
0 => '',
1 => '',
2 => '',
),
'allow_new_levels' => 0,
'max_levels' => 2,
),
);
Is it a bug?
Comments
Comment #1
wim leersGo to admin/logs/status to see if there are problems with your installation.
Comment #2
carlogen commentedWim
I had already checked and no errors in log.
Comment #3
wim leersNot the log, the *status report*. I think you've got jQuery Update 1 installed, but you need 2.
Comment #4
carlogen commentedYes sorry.
I did check this.2
no errors and my Jquery version is "The current installed version of jQuery is 1.2.6".
Comment #5
wim leersOk. Next question: how did you configure the "depth" setting of your content_taxonomy CCK field?
Comment #6
wim leers(Or: go to admin/content/types/export and export just the one field and post it here.)
Comment #7
carlogen commentedfind below configuration
I hope it helps
Comment #8
summit commentedHi Wim,
Having the same situation. The widget hangs on IE6 and Firefox.
Configuration:
greetings, Martijn
Comment #9
wim leersDarn, really must be a bug then :(
Probably due to something that hasn't been renamed properly. That's what you get for renaming things en masse.
I'll look at it Wednesday, after my exam. Wednesday night you can also expect beta 2.
Comment #10
wim leersCould you guys please upgrade to the latest dev release? That appears to be working! (Which would make sense because it's working here…)
I also fixed (mere moments ago) a bug in the JS which may have caused problems in browsers other than Safari (in Safari it kept working, but not entirely correctly), which might help in fixing this problem.
Comment #11
summit commentedThe 29th june version also gives the slowdown/hanging on IE6 and firefox in mine installation. Sorry Wim..
greetings,
Martijn
Comment #12
carlogen commentedWim,
I did the test with new dev version:
Wim Leers - April 15, 2008 - 21:29
Nightly development snapshot from CVS branch: HEAD
Download: hierarchical_select-5.x-3.x-dev.tar.gz
Size: 67.51 KB
md5_file hash: 314fb207d05875391980bd6b1ca8f006
First released: April 15, 2008 - 21:29
Last updated: July 1, 2008 - 00:04
Hierarchical Select 3 development snapshot.
It is working (a little bit slower) with this configuration.
1.
Save lineage: Save term lineage
Level choice: Force the user to choose a term from a deepest level
It still freeze with this configuration.
2.
Save lineage: Save only the deepest term
Level choice: Force the user to choose a term from a deepest level
I tried the remaining configurations
3.
Save lineage: Save only the deepest term
Level choice: Allow the user to choose a term from any level
Freeze
------
4.
Save lineage: Save term lineage
Level choice: Allow the user to choose a term from any level
This is OK
Regards
Carlo
Comment #13
summit commentedHi Wim.
Thanks to Carlogen, it looks like it freezes with:
Greetings,
Martijn
Comment #14
wim leerscarlogen: did you check your status report? I think you still have to perform the last database update!
all: I'm still not able to reproduce this…
Comment #15
summit commentedHi Wim,
what info do you need to reproducte this please?
Greetings,
Martijn
Comment #16
carlogen commentedWim,
I did check the status report.
I have processed a brand new installation of drupal and HS (I have downloaded the last dev file).
The problem is still there always the same.
If you are not able to reproduce the bug.
I could send by email a copy of database and drupal folder, so you can reproduce it on your PC.
Let me know
Comment #17
wim leersIt'd help a lot of one, or both of you could provide me with FTP/SSH + Drupal admin access. You of course have my word that I won't abuse this, and I won't delete any data or change settings.
Comment #18
wim leersFinally reproduced this, while testing for another issue!
This happens only for Content Taxonomy, when you didn't select a "root term" for the vocabulary.
Comment #19
summit commentedHi Wim,
great you could reproduce it!
But.. I do not want to choose a root term. I selected -- on purpose, my root terms for my regional vocabulairy are countries, and thats fine for my purposes. Or I need to make an artificial rootterm to get this working, or are you thinking another way?
Greetings,
Martijn
Comment #20
summit commentedHi Wim,
great you could reproduce it! and thank you a lot for all your support Wim, thanks allready for that, during your exams, really great!
We'll see what the best solution is then. Greetings, Martijn
Comment #21
wim leersOf course you don't have to select a root term. I'm just saying that that is what triggers it, I'm going to fix it ;) :)
Comment #22
summit commentedGreat! looking forward to the fix!
Greetings, Martijn
Comment #23
wim leersFound it! Fixed now :)
Comment #24
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.