hierarchical_select 5.x-3.0-rc1

Changes since DRUPAL-5--3-0-BETA2:

• Also use Hierarchical Select for the forum 'forum' form.
• Implemented #263684: Hierarchical Select Flat List: new mode that doesn't support hierarchies, but does allow usage of the dropbox
• Fixed minor bug in developer mode.
• Added 2 new sections to the README: "Limitations" and "Maximum scalability".
• Improved handling of the max_levels setting; allow 0 for unlimited levels.
• Disallow the user to create new items without labels.
• Fixed #276945: HS Content Taxonomy: "Multiple values" field setting not set when save_lineage or the dropbox are enabled
• Fixed: the flat select would *always* have set #multiple = TRUE, which causes problems (e.g. when using Views exposed filters with "Force single"). Also some cosmetic changes.
• Fixed: The flat select uses the selection from the *calculated* selection, instead of the *generated* selection (e.g. enforce_deepest wasn't being applied).
• - New: you can now pass extra information that will be POSTed when you trigger the 'enforce-update' event.
  -New: a 'disable-updates' event. When you trigger this event, you can handle updates of HS yourself.
• Added work-around for #109459. This was necessary when a HS can be used by anonymous users and when you're using a version of Drupal older than 5.8.
• Make sure HS keeps working as good as it can even when the user makes drastic changes to the content_taxonomy configuration: when he changes the root term.
• Another content_taxonomy weirdness work-around.
• Follow-up patch by jrbeeman for #268639: Add "before" JS triggers and pass hsid and settings through
• Renamed 'node_count' to 'entity_count'.
• #277522: Always allow access to server callback *and* Multiple values setting not maintained when saving the field form
• Added a gotcha to the API documentation based on feedback from jrbeeman.
• Guide the user when he enables the save_lineage setting of an exposed taxonomy or content_taxonomy filter in a view.