hi,

I don't know where or why this happened, but after using Hierarchical Select for over half a year it just stopped working properly. Maybe this is even more a jquery issue than HS..? But anyways - since it's HS that freax out I suppose this is a good starting point.

I have a 3-level taxonomy COUNTRY > CITY > VENUE and when selecting existing terms, everything is fine and smooth and so.. But when I try to add a new term, the dropdown-select-bars are becomming grey-ish and inactive - meaning I can't use them any more. Submitting the node leads to the following error message:

* warning: Missing argument 1 for drupal_retrieve_form() in /www/htdocs/ltdorg/nu2/includes/form.inc on line 179.
* warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '' was given in /www/htdocs/ltdorg/nu2/includes/form.inc on line 218.
* warning: uasort() [function.uasort]: The argument should be an array in /www/htdocs/ltdorg/nu2/includes/common.inc on line 2254.
* warning: mysql_result(): supplied argument is not a valid MySQL result resource in /www/htdocs/ltdorg/nu2/themes/zen/red1/node-gig-page.php on line 70.
* warning: mysql_result(): supplied argument is not a valid MySQL result resource in /www/htdocs/ltdorg/nu2/themes/zen/red1/node-gig-page.php on line 265.

after that I actually can edit the node and select the new term - and everything lokks nice again.

I have jquery 1.2.6 running on a dp 5.16 installation.

thnaks for any suggestions/ pointers/ whatevers..

..greetz, t..

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

Did you make any changes recently?

As you indicate yourself already, if it's been working well for such a long time, it's probably something else.

tille’s picture

tille commented

I actually did some beautyfication css-ing and so - but no new/updated modules or anything thelike.

I now actually finally took the time and updated dp to 5.19 and also updated almost all modules - et voila: it now works as it used to. No more grey-ish inactive dropdowns, only the massive error message appears after a node with a new term is submitted - but maybe that actually has nothing to do with HS? ..we'll see - first I'll to update ALL modules - including Token - then I'll report back..

thanks +greetz! t..

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Priority: Critical » Minor

Which massive error? The one in your first post?

tille’s picture

tille commented

..yep - although it has actually lost some of its *beauty* - here is what it looks like now:

----
# warning: Missing argument 1 for drupal_retrieve_form() in /www/htdocs/ltdorg/nu3/includes/form.inc on line 179.
# warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '' was given in /www/htdocs/ltdorg/nu3/includes/form.inc on line 218.
# warning: uasort() [function.uasort]: The argument should be an array in /www/htdocs/ltdorg/nu3/includes/common.inc on line 2263.
----

by the way: the only module complaining in admin/logs/updates is now HS - stating it would be 5.x-3.0-rc3 although I just uploaded it the third time with the current version:
version = "5.x-3.0-rc7"
project = "hierarchical_select"
datestamp = "1228010724"

..strangeness..

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Are you sure you haven't uploaded HS twice and that Drupal picked the wrong version? (Try removing HS for a second and see if it really does disappear.)

tille’s picture

tille commented

well - thankyouverymuch - it actually was there twice! I threw the other one overboard, now only facing 'green lights' in the updates list - BUT: the hierarchical select quit working completely.

Both modules Hierarchical Select and Hierarchical Select Taxonomy (5.x-3.0-rc7) are up and running, I do have jquery update 2.0 running, I did copy jquery (1.2.6) from the folder /modules/jquery_update/misc to /misc - I did the empty-cache -super-reload...

on the former settings page I don't get any options - only this error message:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'hierarchical_select_admin_settings' was given in /www/htdocs/ltdorg/nu3/includes/form.inc on line 218.

..maybe something wrong with some other component? ...hmm...

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Start from a vanilla Drupal install, verify that that is working and then add modules one by one. That way, you can track down the cause.

tille’s picture

tille commented

..vanilla install..?
..you mean 'fresh' / 'blank' / 'from scratch'..?
..ouch..

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Yes :)

http://www.google.com/search?q=vanilla+installation

tille’s picture

tille commented

back I am - did a vanilla install, installed all my prefered modules in latest versions - but couldn't get rid of the nerve wrecking errors. Then I finally came up with the glorious idea of downgrading HS to rc3 - and finally I had the functionalities back.

Actually the previously described error message still appears after submitting a node when adding new terms. But at least i CAN add new terms without getting the taxo-select bars greyed and frozen.

When I started the downgrading process, I came from rc7, went on with rc5 etc but only rc3 gave me back the non-frozen term-adding-functionality I need.

Well - what can I say? I am sorry, that this still seems to be the way it is - and that I can't really point out the actual error source. Please let me know if you'd like to know more about my setup or the like...

greets, till.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Assigned: Unassigned » wim leers
Status: Postponed (maintainer needs more info) » Active

I managed to reproduce this. Happens only on the D5 version.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

I was wrong.

1) It doesn't grey out.
2) It only doesn't select nor show the newly created term when the "Require associated node" setting is enabled.

Please make sure you're using the latest development snapshot!

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Closing to clean up issue queue. I'm sure that this is working in the latest development snapshot. Maybe it's not working in RC7.