Hi,

I know this seems like an age-long question. I have googled on this, and looked through drupal.org as well.

I just downloaded the latest 6.x-3.x-dev, and installed in Drupal Core 6.14. I tried to edit a vocabulary, and the preview section there gives me the above mentioned error, and of course I'm sure I have javascript enabled. I visited your HS homepage, and the demo works. Did I miss any step?

Thank you in advance.

Comments

wim leers’s picture

Status: Active » Postponed (maintainer needs more info)

jQuery UI installed? If yes, that's likely the culprit.

Start with a vanilla Drupal install and add things until they stop working. That's the culprit.

ThePiano.SG’s picture

Hi,

You are right. After disabling jQuery UI, it works.

But does that mean we are not able to use jQuery UI? Or is there any workaround?

wim leers’s picture

Status: Postponed (maintainer needs more info) » Fixed

Overwrite jQuery UI files with the ones included in HS. I've modified them to no longer cause JS errors. jQuery UI is an incredibly buggy piece of software.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

zoo’s picture

Overwrote "effects.core.js" and "effects.drop.js" files in jQuery UI module folder with those provided by HS, run a cache cleaning, no luck.

FF 3.5.6 keeps to return:

Error: too much recursion
Source File: ***/sites/all/modules/jquery_ui/jquery.ui/ui/minified/effects.core.min.js?Z
Line: 10

Anyone has found any solutions? thanks

zoo

zoo’s picture

I've tried to disable all modules but HS, just to see if the javascript problem relates with some of them, but it seems it is not the culprit in my case since the javascript alert remains. Further if I click the update button the page redirects to the main taxonomy page.

I wonder what could be... I really would like to use HS.

Bye

zoo

zoo’s picture

Hello,

Forgive me, HS works very well now... Sorry for having posted twice.

The js error was due to the fact that 2 instances of jquery UI were loaded at the page load, the second one after the HS call.

This was causing the error. I'm sorry, but glad to have finally found the reason of this issue.

Thank You for your work and hope this could be of some help for others

Bye

zoo