I noticed on our site, www.musicoutbreak.com/members/register_artist , that when you select the parent, the next 3 child levels display all at the same time. We have deepest level required selected when this happens. When we deselect deepest required, it works fine populating the next child when you select the parent.

Is this a known issue? We do require our users to select the deepest level (neighborhood). If this is normal we can deal with it and not require deepest through your module and hard code the requirement.

Just thought I would bring it up and see if anyone else has had this issue. I have searched for a week now trying to find a similar issue on drupal, but could not find any.

Thanks,

CommentFileSizeAuthor
Untitled.png1.15 MBGroovyFX-Matts
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Wim Leers’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

I don't see what the problem is. If you have enforce_deepest enabled, then this makes sense: it forces the user to select something from the deepest level by showing the deepest level (which implies that previous levels are also shown). What's wrong with this?

Is this different from what you're seeing at http://wimleers.com/demo/hierarchical-select/taxonomy?

Kars-T’s picture

Assigned: GroovyFX-Matts » Unassigned
Status: Postponed (maintainer needs more info) » 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.

hexblot’s picture

Version: 6.x-3.7 » 6.x-3.x-dev
Status: Closed (fixed) » Needs work

I can personally attest to the fact that this behavior is still present in latest dev for the 6.x branch.

As discussed in a similar issue (#316267: Enforce deepest + required without prepopulated defaults unfortunately the link doesn't work, and the behavior is unchanged ) there is a good reason for wanting a behavior that is similar to not having "enforce deeper" ( ie having each level unfold on its own, possibly even with a "" option ), with the addition of failing validation after the form is submitted.

The current behavior is more than likely suitable to most, however if there are enough levels, most users only try to change the deepest level and complain about the lack of choices. Even worse, if the server is loaded, they move on while next levels themselves are being loaded (since they are more than a few if multiple levels are being loaded), and an improper value is stored.

I'm more than willing to help test this, and will look into it since a client has stumbled upon it, but it probably will be a lot faster for someone familiar with the code.

Thank you in advance for any insight.

Tschet’s picture

Issue summary: View changes

The current behavior is more than likely suitable to most, however if there are enough levels, most users only try to change the deepest level and complain about the lack of choices.

A lot of time has passed, and I'm seeing the same issue with 7.x-3.0-beta2. Any progress here?

vineetians’s picture

Is this any update at Drupal 7
I have to make mandatory parent > Child both in Hierarchical Select

How would i do Please suggest any One