Unsupported operand types

Either upgrade to the latest CVS version and report the new line number, or tell me the the version number listed at the top of the file.

I can't reproduce this. I think you need to tell me what your exact settings are… The easiest way to do that, is by looking at the variable table and sending me the value of the hierarchical_select_config_taxonomy-1 entry.

Uhm yes, I'm talking about the "variable" table in your MySQL database.

Bump! Got more information?

I get this error too:

Fatal error: Unsupported operand types in /home/xxxxxx/public_html/sites/all/modules/hierarchical_select/hierarchical_select.module on line 1339

My hs_config_taxonomy-1 =

a:5:{s:9:"config_id";s:10:"taxonomy-1";s:12:"save_lineage";i:0;s:15:"enforce_deepest";i:0;s:12:"level_labels";a:2:{s:6:"status";i:0;s:6:"labels";a:0:{}}s:7:"dropbox";a:3:{s:6:"status";i:0;s:5:"title";i:0;s:5:"limit";i:0;}}

Marked critical because, in my case at least, this is enough to break my site pretty badly.

OK, in discussion with dgtlmoon, thinking about your code at 1339:

$hierarchy->levels[0] = array('none' => '<'. t('none') .'>') + $hierarchy->levels[0];

we believe the above should be replaced with:

$hierarchy->levels[0][] = array('none' => '<'. t('none') .'>');

This array appendage is done several times in your code; not sure if they all should be modified to the above syntax. Thoughts?

It seems I got the above error due to a code conflict from vocabselect.module. Still not sure if the above code is potentially problematic though; please close this issue if you wish.

Jeff: the code you mention in #9 is correct, it is to *prepend* the "<none>" option before all other options. Similarly for all other times that I use that syntax.

I'll try to reproduce the problem with the vocabselect module.

Ah yes of course. Sorry :(

Do you still have this problem after updating to the newest version of HS?

If yes, please send me your config *again*, but use http://wimleers.local/hs3/admin/settings/hierarchical_select/configs this time to export your config.

I very strongly suspect this has been solved indirectly in my patching spree of the past 2 days. Feel free to reactivate if it turns out that this is not fixed. Cleaning up the issue queue :)