Hi there,
I´ve installed this module to be used with taxonomy selection.
And it works.

The problem is that a lot of times, when using chrome, I select the taxonomy, and instead of showing me the second level to be selected, it returns into "none selected". It´s like it doesn´t "take" it. I have to go and click there again in order to select it.

How may I avoid this?

Thanks for your help!
Rosamunda

CommentFileSizeAuthor
#3 hs_select_issue.mov_.tar_.gz1.33 MBchaunceyt
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Kars-T’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs steps to reproduce

Dear fellow Drupal enthusiasts,

I have set this issue to "Postponed (Maintainer needs more information)".

If not already done please add an issue summary and steps how to reproduce the problem.
And please read again, "Making an issue report".

Help about how to do this can be found on IRC and in the user groups.

After there is new information, please re-open the issue by changing the status to active.

--
This issue was edited with the help of Issue Helper

Leeteq’s picture

I can confirm that on several computers, both in recent Firefox versions and Chrome versions, we have to click 2 (mostly) or 3 times on the "Add" button in order to actually get the selected term to appear in the list below.

A second thing that happens is that often when adding new terms on the fly, we are redirected to the front page with a green "term created successfully" message when clicking on the button that is supposed to create the term in the small modal window that appears, and then nothing we did on that edit page has been saved (all lost, and the term has not been added or even created...)

These two javascript issues are perhaps related to the same piece of code, not sure.

Could this be related to PHP 5.4?
Right now I have only used alpha6 on drupal 7.23 on two different sites/servers who are both running PHP 5.4.

@Rosamunda: please confirm which PHP version your server is using.

chaunceyt’s picture

I'm having this problem also. I've attached a screencast of the behavior.

Issue as I see it: Selecting a term from a vocabulary, causes the input field to close and not return. It acts as if it's going to get the child terms for the selected term, but gets stuck.

Environment
drupal 7.23
phpversion: 5.3.x

How I'm using the API

    // Hierachical Select form field.
    module_load_include('inc', 'hierarchical_select', 'includes/common');

    $office = isset($form_state['values']['filters']['offices']) ? $form_state['values']['filters']['offices'] : array_keys($bean->filters['offices']);
    $vid = energy_content_get_taxonomy_tid($office);

    $form['filters']['office_taxonomy'] = array(
      '#title' => t('Office Taxonomy'),
      '#type'          => 'hierarchical_select',
      '#config'        => array(
        'module' => 'hs_taxonomy',
        'params' => array(
          'vid' => $vid,
        ),
        'dropbox' => array(
          'status' => 1,
          'reset_hs' => 0,
          'limit'    => 0,
        ),
        'save_lineage'    => 1,
        'enforce_deepest' => 0,
        'entity_count'    => 0,
        'require_entity'  => 0,
        'editability' => array(
          'status'  => 0,
        ),
      ),
      '#prefix' => "<div id=\"office-taxonomy-div\">",
      '#suffix' => '</div>',
    );

    if (count($bean->filters['office_taxonomy']) > 0) {
      $filters_office_taxonomy = array();
      foreach ($bean->filters['office_taxonomy'] as $office_taxonomy) {
        $filters_office_taxonomy[$office_taxonomy] = $office_taxonomy;
      }
    }

    if (count($filters_office_taxonomy) > 0) {
      $form['filters']['office_taxonomy']['#default_value'] = $filters_office_taxonomy;
    }
langweer’s picture

Hej,

I run Drupal 7.23 (PHP 5.2.12-nmm4) using "Hierarchical Select" for taxonomy selection and experienced a similar problem after updating "Hierarchical Select" from 7.x-3.0-alpha5 to 7.x-3.0-alpha6: The "add" button doesn't work properly. Instead after pressing "add" the page seems to be reloaded but no taxonomy item is added to the list. After this reload the "add" button works fine for one time. Then the circle starts over.

I switched back to "Hierarchical Select" 7.x-3.0-alpha5 and found the selection process working fine.

My conclusion: somewhere in 7.x-3.0-alpha6 is a change that bothers us. If this description helps the developer, I am glad. If you need more information, let me know.

All the best - Andreas

fox mulder’s picture

Downgrading to alpha5 works for me too. Many thanks langweer!

chaunceyt’s picture

Interesting I'm currently using 7.x-3.0-alpha5 and it's not working.

richsky’s picture

Maybe, but have you applied any patch?

chaunceyt’s picture

@richsky if you're asking me if I've applied any patch. No. I even tried alpha6 and had the same issue.

Thanks

Summit’s picture

Hi, I have the same situation with latest alpha, you need to select twice! Greetings, Martijn

ohthehugemanatee’s picture

alpha6 is known broken with this behavior - please try alpha7 or current dev. See #828418: Drupal.attachBehaviors() used with an incorrect context? .

Chimos’s picture

I had the same problem and other issues with Hierarchical Select.

Installing 7.x-3.x-dev (2013-Oct-28) solved ALL them. So probably, the next release after 7.x-3.0-alpha6 will solve them too.

Hope it helps. Cheers

Pablo Gosse’s picture

Issue summary: View changes

You can use the patch in the issue linked in #10 to resolve this issue. I diff'd alpha6 and the change in the patch is the only difference between alpha6 and the dev version (other than packaging info in the .info files).

http://drupal.org/files/issues/hierarchical_select_attachbehavior-828418...

Pablo

shahidbscs’s picture

I'm using 7.x-3.0-alpha6 and jquery_update. Its not work for me?

Pablo Gosse’s picture

@shahidbscs, please see post #10. The problem is a known issue with alpha6. Upgrade to alpha7 or use the dev version.

shahidbscs’s picture

Thanks @Pablo Gosse, 7.x-3.0-alpha7+1-dev work perfect for me.

themic8’s picture

I also had this issue. Using the dev version did the trick.

Gold’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

It's been 4 years since the last comment on this. All the major browsers have advanced a lot. This module has advanced a lot. In the last week or so I've spent a lot of time in the issue queue and have not seen this described behaviour.

I'm going to assume that this is now an outdated task.

If it is found to still be current please provide detailed steps to reproduce it starting from a clean install of D7 with the Standard profile.