hierarchical_select 5.x-3.0-rc4

Final Release Candidate! :)

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

• #248497 by fago and myself: nodeprofile/subform_element compatibility
• Fixed #301692: Can't change multiple select setting for a vocabulary when HS is disabled for it
• Fixed #301660: Improving the HS UX
• Fixed #296254: Unable to set the parent of a term/container/forum
• Implemented #308823: Hierarchical formatters for Content Taxonomy fields
• Fixed a bug in the show/hide JS on the common config form that prevented the editability[max_levels] setting from being displayed in one case.
• Prevent JS error in the resizable code when creating a new item (it shouldn't run, because no selects are present).
• The selects would still be enabled after the dropbox limit was exceeded.
• Resizing one HS would resize all next HSes as well, because of a wrong selector.
• The size the user resized to wasn't properly being maintained when #size > 1 and an update of the HS was triggered.
• Apostrophes were not being escaped in the config exporting code.
• Allow for a custom separator in the hierarchical formatter for the content_taxonomy field.
• Implemented #311338: Provide performance analysis tools and do console.log() output instead of dpm()
• #314498 by ricardo37: Fix example in API documentation
• Fixed #315066: HS is appearing when editing the first-level book node (it should not)
• Fixed #316157: Vocabulary form does not remember the "Use HS for this vocabulary" setting
• Fixed #316200: Resizable setting is always enabled
• Fixed #316712: HS Menu implementation doesn't pick up "restrict parent" settings
• Implemented #310851: Support [lineage_termpath] token
• Fixed #248497: HS doesn't work on nodeprofiles in IE
• Implemented #180691: Child indicators
• Follow-up commit for #180691.
• Fixed #305099: enforce_deepest not functioning correctly in very specific circumstances