Apologies if this is answered already, but I have searched for a couple of hours without finding an answer.

I have a form where the category selection is required. If I enable the dropbox to allow multiple categories and do not click add, the node is saved without a category and no error generated. If any categories are chosen they are saved as normal. If I disable the dropbox, whatever is currently listed in HS is saved (which I would expect).

If I disable HS for that category, then an error is generated when no selection is made either on single or multiple selection setting.

Comments

wim leers’s picture

Assigned: Unassigned » wim leers
Category: support » bug
Status: Active » Postponed (maintainer needs more info)

Sounds like a bug indeed. Will try to reproduce. If you could provide a step-by-step guide for a fresh D5 install on how to reproduce this, that'd be great.

Balefire’s picture

Hi there, have done as asked - completely clean and fresh install on my dev box.

Each of these are freshly downloaded from drupal.org:
Drupal 5.9
Hierarchical Select 5.x-3.0-rc1
jQuery Update 5.x-2.0

Have enabled the following over and above the default settings:
jQuery Update (copied the contents of Jquery_update/misc to /misc, overwriting any existing files)
Hierarchical Select
Herarchical Select Taxonomy

Created a new category with the following structure:
Simple
-First
--Child of first
-second
--Child of second
-Third
--Child of third
--Another child of third
-Fourth

Category Settings:
Name: Simple
Type: page
Hierarchy: Single
Required
use Hierarchical Select
Enable dropbox
dropbox title = Selected categories
Enable reset selection

All others as originally set.

Can still add page nodes without categories. I can attached a dump of the DB if that is of any use to you. Hope this helps you with finding a solution.

wim leers’s picture

Version: 5.x-3.0-rc1 » 5.x-3.x-dev
Status: Postponed (maintainer needs more info) » Active

Unfortunately, you're right :(

wim leers’s picture

Title: Node saves without category even when required is set » #required not respected
Component: Code - Taxonomy » Code
Status: Active » Fixed

This is a regression caused by this change, which is in fact a work-around for a bug in core. But this isn't the place to fix core, and as a punishment, I got this bug slapped back at me.

Balefire’s picture

Thanks for the update, good to know you are able to locate the issue. Pity it's caused by a workaround for a bug in core. Hope you are able to either 'fix' the core bug in your code or convince the Drupal maintainers fix the bug in core :)

I'm working around the relatively minor issue using level labels to prompt people to click the add button.

wim leers’s picture

No, you misunderstood me, I removed my 'fix', since it's not that important and actually fixed this issue :)

Balefire’s picture

Status: Fixed » Closed (fixed)

Apologies for not getting back sooner - just a quick FYI everything is working as it should :)

I've set this to closed, not sure if I should but as the fault has gone away ...

Thanks for the module. Saved me many hours of figuring out how to do something similar myself.