True multiple select support

2 possible solutions:

1) use multiple content_taxonomy fields, this may not be really what you want
2) sponsor me to write a better way for doing this: http://drupal.org/node/176936#comment-606565 (see the attached image)

I'm afraid you'll have to wait until somebody sponsors it or until I have time and finished higher priority work.

Just putting myself on the waiting list...

Michelle

Just out of interest what level of sponsorship might you be looking for?

Please contact me via my contact tab here at Drupal.org or via http://wimleers.com/contact.

The initial version with multiple select support has been committed: http://drupal.org/cvs?commit=93142. The "Remove" button does not yet work though, that's for the next revision.

Thanks very much for doing this. The demo looked awesome. I can't wait to try it out!

Michelle

And now it is complete.

People who are interested in this new feature, please start testing it and file bug reports! (I hope there won't be too many, of course.)

If $dropbox->lineages is not set i get errors on line 532, 537, 333

is wrapping it in if ($dropbox->lineages) { ... } a solution?

I had some thoughts on layout. the width of 10% lets lines wrap too early for longer lineages and the add button is one line below the hierarchical select, is this on purpose?

What about this in the css file?

div.hierarchical-select-dropbox {
  width: 70%;
}

input.hierarchical-select-add-to-dropbox {
  margin-top:0;
}

AND
.hide() in hierarchical_select.js line 92 is commented ;)

Sorry, tell me if this is not my responsibility. Setting it to active.

70% is super ugly, because then there will be too much whitespace. Feel free to improve the CSS, I agree that it could be improved *a lot*, but I'm no CSS wizard... Please continue CSS improvements in another issue.

I'm working on the bug you've reported.

Fixed now.

The changes you suggested wouldn't have been sufficient. Check the diff from version 1.12 to version 1.14 of the .module file if you want to know what had to be changed.

And please report bugs as new issues the next time, that's exactly what the issue tracker is for!