this javascript error jumps up on every page after installing the module (and it doesn't work):

ret[ret.length - 1] has no properties

in jquery.js.

I am using jquery update module, so maybe something in l10n_client.js isn't working with jquery version 1.1.2?

Comments

gábor hojtsy’s picture

Title: javascript error after installing localization client » Javascript error with jquery_update and l10n_client
Status: Active » Postponed (maintainer needs more info)

Hm, well it was backported for the jQuery used in Drupal 5 from Drupal 6. What's you suggestion, should we ship with a "jQuery update" compatible version of the l10n_client JS file as well? Does not sound a too good idea to me.

heine’s picture

Upgrading the jquery used with jquery_update tojQuery 1.1.3 (http://docs.jquery.com/Downloading_jQuery) solved this issue without damaging collapsible fieldsets, tableselects, autocomplete and lots of custom code.

gábor hojtsy’s picture

Project: Localization client » jQuery Update
Status: Postponed (maintainer needs more info) » Active

Sounds good. That might be a good idea to include in the jquery_update module then? Moving issue to jQuery Update module.

wmostrey’s picture

It would be great if jquery_update could come with the 1.1.3 version. We were experiencing unresponsive script warnings using jquery_update with l10n_client and the 1.1.2 version of jquery.js. Switching to 1.1.3 resolved this issue and a quick look around didn't show any issues with other scripts such as swfobject or TinyMCE for instance. Since this has been tested and confirmed by Heine and myself this is RTBC as far as I can see.

sun’s picture

Project: jQuery Update » Localization client
Component: Code » User interface
Category: support » bug

jquery_update v2.x ships with jQuery 1.2.6 now and seems to be pretty stable so far.

I don't think that there will be another update to the 1.x branch. So, moving back to l10n_client queue.

gábor hojtsy’s picture

Status: Active » Postponed (maintainer needs more info)

Heine's report above suggests that the updated fixed jQuery update code fixed this issue. Right? So what else is to do on l10n_client?

yhager’s picture

also works with jquery-1.1.4.

wmostrey’s picture

Status: Postponed (maintainer needs more info) » Fixed

Indeed, there's nothing left to do.

Status: Fixed » Closed (fixed)

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