Closed (fixed)
Project:
Hierarchical Select
Version:
5.x-3.x-dev
Component:
Code - Content Taxonomy
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
7 Apr 2008 at 20:12 UTC
Updated:
21 May 2008 at 02:04 UTC
so I got this working on one content type....and then I went to add the same CCK field to a second content type and when you go to enter a new node item (for this second node type) it shows it in the list view....no AJAX.
All the fields settings are exactly the same....after all, all the hierarchical settings are done in the Taxonomy/Category setup....
see screenshots:
| Comment | File | Size | Author |
|---|---|---|---|
| node_type2-not-OK.png | 14.43 KB | mdowsett | |
| node_type1-OK.png | 9.2 KB | mdowsett |
Comments
Comment #1
wim leersThis is a Content Taxonomy field?
Comment #2
mdowsett commentedyes. As I said, it worked on the first node type but not on the second...
Comment #3
32940stf commentedI am having the exact same issue. It is interest that if I create a new field on the same content type that references the same vocabulary as the first broken field, the new field works as expected.
Comment #4
mdowsett commentedI'm somewhat glad someone else has this issue.
So Wim....is this a bug? Can you fix?
Comment #5
wim leersI'm not fixing any bugs against HS 2. HS 3 is coming soon! :) If the issue persists in that version, I'll of course fix it.
See http://drupal.org/node/226067.
Comment #6
mdowsett commentedThat link didn't seem to help.
I'm using this in a Bio node...and the admin has access to the HS tables when editing a user's Bio or when going to /node/add/bio but if they go to create a new user (/admin/user/user/create) they get the multi-select list as seen in the 'node_type2-not-OK.png' above.
Also when a site visitor goes to signup for a new account, the multi-select list is what is shown.
If a registered user goes to edit their Bio, they are given both the multiselect list (which eventho it is set to allow multiple values, only allows one value to be added AND won't allow the sub-items to be selected) AND they are given the JS list which works (allows you to dig into the sub-lists) and allows you to add multiple values.
Another issue I have is when you look at the completed node, it shows a jumbled list of selections rather than the llist of selections generated by the AJAX selection in the edit mode.
I'm really looking forward to getting this module working, it has great potential and hopefully will work really slick with AJAX.
Thanks for your efforts.
Comment #7
wim leersI'm sorry that I didn't make that clear. That's the issue that will push HS's version number to 3. It's not yet ready for consumption! :) I'll let you know here when you can test again.
Comment #8
mdowsett commentedthx - looking forward to it.
I don't mean to pressure you, but any idea of a time frame?
Comment #9
wim leersA couple of days. I first want feedback from those involved with that issue. After that, I'll gladly welcome your testing. :)
Comment #10
mdowsett commentedI'll be waiting! :)
Comment #11
wim leersIt's committed. You can wait for the 3.x-dev release to be published (will take up to 24 hours), or check it out from CVS yourself, or download it from here: http://drupal.org/files/issues/hierarchical_select_5.zip.
Comment #12
32940stf commentedHey guys,
I have tried out HS 3 and unfortunately it didn't seem the fix the problem. I am going to keep testing.
Comment #13
wim leersIn that case, it's the form altering that's not working properly. Could you perhaps give me access to a live site where this is happening? I'll need both Drupal and FTP (or SSH) users.
Comment #14
32940stf commentedRight now I have this all running on my laptop as I have just started my development. I am planning on getting up to a server shortly (hopefully this week) and can provide the l/p once that has been completed
Comment #15
wim leersA HS CCK widget for content_taxonomy has been committed: http://drupal.org/node/229315. Please test again and create a new issue!
Comment #16
32940stf commentedI have tried with the latest tarball and after going into each content type and changing the widget type to Hierarchical Select for the affected field, the result is much better. It seems to be working as expected.
Thanks Wim
Comment #17
32940stf commentedI take it back... it looks to work on initial glance but if I select the initial root level, the ajax does not work to expand out to the children. The widget behaves as expected on the first content type but does not on subsquent content types.
Comment #18
wim leersPlease create a new issue :)
Comment #19
32940stf commentedI believe I have figured it out. In order to use the same content taxonomy field in mulitple content types (and migrate your HS v2 implementation) there are two things on each content type which needs to happen:
1) Change the widget to "Hierarchical Select" and save the field.
2) Go back in the field configuration form and then open the Hierarchical Select configuration form and just save it.