Enabling Hierarchical Select Taxonomy Views causes errors in admin/settings/hierarchical_select/configs

+1

I'm getting the same error here.

I'm getting the same error here.

Hi..

Look at this http://drupal.org/node/579164

Just downloaded this module and tried to use it on two different sites and I too am getting the same error along with messages in my modules page that says:

Hierarchical Select Book>>>>>This version is incompatible with the 6.13 version of Drupal core.
Hierarchical Select Content Taxonomy>>>>>This version is incompatible with the 6.13 version of Drupal core.
Hierarchical Select Content Taxonomy Views>>>>>This version is incompatible with the 6.13 version of Drupal core.

Messages from Hierarchical Select Config Page:

warning: array_merge_recursive() [function.array-merge-recursive]: Argument #2 is not an array in ..../sites/all/modules/hierarchical_select/hierarchical_select.admin.inc on line 79.
warning: array_merge_recursive() [function.array-merge-recursive]: Argument #1 is not an array in .../sites/all/modules/hierarchical_select/hierarchical_select.admin.inc on line 79.
warning: Invalid argument supplied for foreach() in .../sites/all/modules/hierarchical_select/hierarchical_select.admin.inc on line 84.

I was hoping to use this module to help the selection of taxonomy terms on a view page.

The widget actually can be configured regardless of the above error messages. The widget appears in my view, but, if it is used, it generates errors.

Here are the error messages that appear on the views page if the Hierachical Widget is used:

* warning: Invalid argument supplied for foreach() in .../modules/views/includes/handlers.inc on line 680.

* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') count_alias' at line 5 query: SELECT COUNT(*) FROM (SELECT node.nid AS nid FROM node node LEFT JOIN content_type_websites node_data_field_overall ON node.vid = node_data_field_overall.vid WHERE ) count_alias in .../modules/views/includes/view.inc on line 729.

* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY node_data_field_overall_field_overall_rating DESC LIMIT 0, 10' at line 6 query: SELECT node.nid AS nid, node_data_field_overall.field_overall_rating AS node_data_field_overall_field_overall_rating FROM node node LEFT JOIN content_type_websites node_data_field_overall ON node.vid = node_data_field_overall.vid WHERE ORDER BY node_data_field_overall_field_overall_rating DESC LIMIT 0, 10 in .../modules/views/includes/view.inc on line 755.

the1brit: double posting is not appreciated here. More than half of what you're saying is irrelevant to this issue. Please conduct yourself properly.

I *think* I've fixed the bug by just looking at the code. So I'm not 100% sure this fixes it: http://drupal.org/cvs?commit=265568.

Although I appreciate your fix, I find your response very rude and offensive. I am simply looking for help solving a problem. I thought others would like to know that someone else is experiencing the same problem and tried to provide as much detail in my post to aid both you, and the other people that are trying to use your module. I have no idea what information you would need, so I provided everything that I could. People googling this problem may find one of the posts and not the other, so I posted in both places. Both posts are for the exact same issue and people may follow one and not the other.

I'm sorry if I offended you, the1brit. That was definitely not my intention. However, place yourself in my shoes for a minute: having to plough through boatloads of issue comments (in the case of HS, many issues are in fact inherent to Forms API's nature/design thus impossible to prevent), including offtopic comments, useless comments and even sometimes double posts.

The well-known mantra "give all details you can think of when filing a bug report" that applies to all software in general, is okay, but not good. It should also be concise, relevant and clear, otherwise the amount of data can become too overwhelming.

I guess I should have omitted the "Please conduct yourself properly.". My sincere apologies for that.

So, I'll rephrase. Please don't double post in the future, try to give more relevant feedback (although I thank you for trying to be as complete as possible) and try to use more formatting to make your message more clear.