I use hierarchical select on a taxonomy vocabulary width terms and subterms.
Since few days, when I load subterms (hierarchical_select_json), there seems to be a conflict width fbconnect that prevent me to load subterms.
I've javascript error width https://s-static.ak.facebook.com/connect/xd_arbiter.php?version=11

I don't know if I'm the only one to experience this problem, it may be a fbconnect related problem, sinse the drupal 6 version of their module is no really up to date.

Comments

it-cru’s picture

it-cru
Primary language English
Location Munich
commented

You are not alone ;)

After every term item selecting I have to hit the update button (the nojs one which is normaly hidden) for more deeper term selecting or adding the hs selected terms via the add button.

Same problem here with hs 7.x-3.0-alpha5 and the FB for Drupal module. When I deactivate all FB relevant modules in my development environment hs works again like a charm.

Perhaps somebody with more ajax/js debugging knowhow can take a look, check and possible fix this.

it-cru’s picture

it-cru
Primary language English
Location Munich
commented

After update from FB for Drupal from 7.x-3.3-beta3 to 3.3-beta4 my taxonomy hierachical select works again like a charm.

Perhaps this helps with D6 too.

kcannick’s picture

kcannick commented

Same issue here... I have a D6 site and use HS for required fields in user profile.... Once users select the top level in HS field sub levels appear but remain grayed and curser stays active as if still loading options... However when I disbale fbconnect modules everything works as usual... This issue just started in the past month or so.

brazorf’s picture

brazorf commented

Subscribe
Anyway i think this has to be more related to fbconnect itself, rather than HS.
This is the javascript error i get, after selecting one item from the first level html-select:
Uncaught Error: Invalid DOM node passed to FB.XFBML.parse()

It seems like he's trying to parse the json response from HS... thing it should not be doing. Should we issue this to fb_connect queue?

edit:
i opened a new issue because as i said i think this is mostly related to fbconnect itself: http://drupal.org/node/1810014

gold’s picture

gold
they/them
Location 20 minutes in the future
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Tidying up the issue queue. The 6.x version is no longer supported. Only reopen this if it also applies to the 7.x.