Closed (fixed)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Code - Content Taxonomy
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Nov 2009 at 22:44 UTC
Updated:
25 Nov 2009 at 10:20 UTC
Hi,
I added the HS Content taxonomy widget of the latest .3-dev. It all adds fine, and the node shows the CCK HS Content Taxonomy fields, but when I click on the link of the term, it goes to the right taxonomy/term page but without showing the node I just build with it...
Underneath is the HS Content Taxonomy installation:
$config = array(
'config_id' => 'content-taxonomy-field_regio_chs',
'save_lineage' => 0,
'enforce_deepest' => 0,
'entity_count' => 0,
'require_entity' => 0,
'resizable' => 1,
'level_labels' => array(
'status' => 1,
'labels' => array(
0 => 'Land',
1 => 'Provincie',
2 => 'Stad/dorp',
),
),
'dropbox' => array(
'status' => 1,
'title' => 'All selections',
'limit' => 0,
'reset_hs' => 1,
),
'editability' => array(
'status' => 0,
'item_types' => array(
0 => '',
1 => '',
2 => '',
),
'allowed_levels' => array(
0 => 1,
1 => 1,
2 => 1,
),
'allow_new_levels' => 0,
'max_levels' => 0,
),
);
What can be the problem please?
When I add a 'normal' HS taxonomy widget, the node shows on the same term, so it has to be something with HS content_taxonomy, right?
Thanks for going into this!
Greetings,
Martijn
Comments
Comment #1
summit commentedHi,
After trying to get another term to be added to the node I got:
Hopefully this helps!
Greetings,
Martijn
Comment #2
summit commentedHi Wim,
Ahh..it was my own mistake. I needed to check: Save values additionally to the core taxonomy system (into the 'term_node' table). If this option is set, saving of terms is additionally handled by the taxonomy module. So saved terms from Content Taxonomy fields will appear as any other terms saved by the core taxonomy module. Set this option if you are using any other taxonomy application, like tagadelic. Otherwise terms are only saved in the cck tables and can only be accessed via the node or a view
I forgot this! Sorry for filing an issue. It works as advocated!
greetings,
Martijn