Hello,
Thank you very much for developping hierarchical_select module ! I have been using it for 3 weeks now.
I have a vocabulary like so :

  • Furniture
    • Beds
    • Desks
  • Decoration
    • Sheets
    • Lights

I basically want :

  1. this vocabulary (and only this vocabulary) to have a max 2 levels-depth (ie. root + 1 child level)
      This implies admins cannot assign terms as children of level-1 terms.
  2. end-users to be able to choose only from level-1 terms (eg. Beds, Desks, Sheets, Light) when editing some content type

I have spent some time overriding the _select's theme function behaviour with code that I have attached to this support request. My big issue is that it seems almost impossible to detect the current editing context (eg. what vocabulary ? term edit form or node edit form ?), detecting it on first (ie. non-ajax) rendering is OK, but for following AJAX request it isn't (right now, I'm thinking I should look at the HTTP referrer but that still is not very clean).

Could you tell me if there's some simple way to get what I want ? Should I write a full new module following the HS tutorial ? Is there some easy way to make what I want as few as posible HS- or other modules-hooks ?

Thanks in advance for your kind support and advices !

CommentFileSizeAuthor
aw_phototheque_HS_code.module.install.php_.txt5.15 KBmyselfhimself

Comments

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.