Closed (duplicate)
Project:
Hierarchical Select
Version:
6.x-3.x-dev
Component:
Miscellaneous
Priority:
Minor
Category:
Feature request
Assigned:
Reporter:
Created:
4 Apr 2008 at 16:55 UTC
Updated:
3 Aug 2009 at 21:59 UTC
Jump to comment: Most recent file
Comments
Comment #1
wim leersWhich browser is this? Are you sure you're using an unmodified version? Did any Javascript errors occur?
It's because the JS failed to hide the multiple select, for some odd reason.
Comment #2
mdowsett commentedMAC FireFox. No JS errors...and it is unmodified.
I'm getting some other strange behaviours and I can't figure out what's going on...I'm getting frustrated and need to take a break
I am creating a taxonomy term as this hierarchical tree and then adding it as a CCK field to a Bio content type....that should work right?
Comment #3
wim leersDo you have any other JS-powered modules installed?
Comment #4
BladeRider commentedI might have some additional information to help trace the cause of this behaviour.
First of all, it is only happening when there are multiple vocabularies assigned to a content-type. If there is only one vocabculary then everything works as expected.
Tested on a clean Drupal install, with jquery_update/jquery_interface modules correctly installed
Attached are two screenshots, one from Firefox and the other Safari.
*** ADDITIONAL INFO *** - AFter posting this ticket, just discovered that the problem goes away if the Categories fieldset is NOT collapsed by default. I was collapsing programmatically in a custom module, and having it expanded by default made the odd behaviour go away.
Comment #5
wim leersHm, does this mean the issue is solved now?
Comment #6
BladeRider commentedI guess I'm happy enough now! Will examine source though as I have a feeling the 'bug' may be something as simple as a jQuery .toggle() that's conflicting with the already-hidden standard Taxonomy fields i.e. The behaviour is now reversed.
Comment #7
mdowsett commentedI think it is fixed.....I was so frustrated with it the other night, I walked away in disgust after posting this! (well, maybe that is a bit extreme...) :)
All I did today was make sure those field sets were set to 'always open' and it all 'seems' to be working as I had hoped. I'm uncertain if this was the solution but at least it is working! :) I'm afraid to change it back in fears it will break it.
The only other thing that isn't really working now is that when you view the node (in this case a Bio) it shows the term selections as a list instead of the 'table' it shows in the node edit screen. See attachments.
Should I start a new support request for this?
MANY thanks.
Comment #8
wim leersYou'll have to theme it as that kind of table yourself. Hierarchical Select just provides an input widget… I guess I could provide a helper theme function to do this though.
Comment #9
mdowsett commentedI'm not a coder so I don't have the skills to do so.
I was surprised that wasn't the default result since that is what is posted in the edit screen.
If you could provide the helper theme function, that would be fantastic.
Comment #10
mdowsett commentedComment #11
wim leersActually, in HS 2, there already is such a function:
theme_hierarchical_select_render_dropbox(). Just feed it the information in the right format and it will work.So, now moving to HS 3.
In HS 3, I use the Forms API to render everything, so it won't be very easy to provide similar functionality there. I've not yet decided whether I want to add support for it there as well, because that'd become… pretty tricky, or at least very ugly for the themer.
Definitely postponed.
Comment #12
wim leersBetter title.
Comment #13
wim leersOn second thought, what you have requested, is a non-issue. All you have to do, is write a mini form like and render it:
*But*:
- you still get the hierarchical select then
- the "Remove" links are still there
Which is at the very least confusing.
So if I want to fix all that (i.e. fix the *real* issue), I will indeed have to provide a function to which you can pass the selected items, the parameters for rendering (since you also need to rebuild the hierarchy for just rendering this seemingly simple table) and then it's ready. This is ultra-low priority though (most people want output to be different from input), so this might take … many months. Sorry.
Comment #14
wim leersComment #15
wim leersSee #516782: Theme function to display lineages when viewing nodes, where exactly this is implemented.