Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I install the "localization client" module and it disables simplemenu and maybe other javascript stuff
Uninstalling brings the simplemenu back.
Firebug complains about the following error:
ret[ret.length - 1] has no properties
e("#edit-copy", Document modules)jquery.js (line 2)
e(Document modules)jquery.js (line 2)
e([Document modules], function())jquery.js (line 2)
e("#l10n-client-form #edit-copy")jquery.js (line 2)
e("#l10n-client-form #edit-copy", undefined)jquery.js (line 2)
e("#l10n-client-form #edit-copy", undefined)jquery.js (line 2)
l10nEditorAttach()l10n_client.js (line 82)
e()jquery.js (line 2)
e()jquery.js (line 2)
e([function(), function(), function(), 4 more...], function(), undefined)
I am using the legacy "jquery update" module (jquery 1.1.2)
Comments
Comment #1
michalczernik CreditAttribution: michalczernik commentedIs this really one year old bug? Still unfixed?
This module is breaking all Javascripts.. Regardless you use 'jQuery update' or not.
:-(
Comment #2
Gábor HojtsyWe've recently added code to not re-attach behavior, which should help. It would be great to get actual examples. The 5.x example that the issue was submitted for is indeed ages old. And while a bug standing around for ages might look strange, it also means others did not reproduce it or did not think it was important to fix. If this would be critical, others would be around to confirm.
I've just tried the current version of l10n_client with the current version of simplemenu, and they both work just fine. Please specify if actual modules have interaction issues.
Comment #3
shwx CreditAttribution: shwx commentedI've the same problem...
Comment #4
Gábor HojtsyHave you tried the latest development snapshot? (I intend to do a release soon, so more testing would be awesome :).
Comment #5
shwx CreditAttribution: shwx commentedYes, I tried the last, but without succes :(
Comment #6
Gábor HojtsyOk, we need more information from your Javascript error logs then.
Comment #7
EugenMayer CreditAttribution: EugenMayer commentedAlso issues with wysiwyg image upload http://drupal.org/node/857546#comment-3217076 (confirmed on several clients ). Seems like JSON or headers are broken by the client.
I suggest headers
Comment #8
Gábor HojtsyYou suggest, or you have some proof? The issues above suggest problems with how elements are not found by l10n_client and the latest dev versions use classes to identify elements rather then IDs. Are you using the latest dev version?
Comment #9
EugenMayer CreditAttribution: EugenMayer commentedGabor no, i have no proof of the suggestion - i had not time for further investigation. The only thing i had proof is that the localisation client is the cause and its breaking other modules too.
AFAIK those people used the stable. You expect the dev to work out here?
Comment #10
Gábor HojtsyYes, the initial issue above can be solved by (a) not using ID selectors (b) not running the behavior multiple times. We now do both in the dev version. I hoped to get some 3rd party testing before I push a new version, and since you experience the issue, you'd be best to test. I can always release a new stable version, but would not planned to annoy anybody to release without fixing critical issues :)
Comment #11
EugenMayer CreditAttribution: EugenMayer commentedSounds reasonable. I will report back Gabor, thanks for the work!
Comment #12
EugenMayer CreditAttribution: EugenMayer commentedGabor its veryfied, working with dev!
Comment #13
Gábor HojtsyNothing to commit here, this was committed already.
Comment #15
geaseThe issue still persists in l10n_client 6.x-2.0 and current dev. It kills wysiwyg_imageupload module.
Comment #16
unegro CreditAttribution: unegro commentedThis bug still happening in Drupal 7.2
There is a mismissed configuration?
Comment #17
unegro CreditAttribution: unegro commentedIt happens too in Drupal 7.2
Comment #18
Gábor HojtsyCan you try if the improvements from #862590: Cleanup and optimization on l10n_client.js help? Thanks.
Comment #19
unegro CreditAttribution: unegro commentedI tried the suggested patches
The patch l10n_client-global.patch didn't work
The patch l10n_client-complete2.patch din't work
The patch D7-patch-combined.patch didn't work
The patch l10n_client-cache-client.patch didn't work
Firebug Gives me This error:
$.cookie is not a function
switch($.cookie('Drupal_l10n_client')) {
Do you have another suggestion?
Comment #20
Gábor Hojtsy@unegro: Yes, that should be a duplicate of #522646: jquery.cookie.js incompatible with Apache mod_security by default, see info there.
Comment #21
SebCorbin CreditAttribution: SebCorbin commentedIs this issue still happening since #862590: Cleanup and optimization on l10n_client.js has been committed?
Comment #22
joel_osc CreditAttribution: joel_osc commentedJust an FYI, I experienced this issue when using the TOC module - found a workaround to disable hot-keys on the l10 and the toc started working again. My workaround involved commenting out the following lines:
Comment #23
Mark_L6n CreditAttribution: Mark_L6n commentedAnother FYI, I just found that Colorbox was not working properly on views pages with language prefixes in the path, see here. The code/link being generated was proper, just for some reason the javascript would not kick in and load the lightbox. (Localization client 7.x-1.3, Drupal 7.30).
Comment #24
Mark_L6n CreditAttribution: Mark_L6n commentedAdditionally, Bootstrap theme users are reporting conflicts: #1887224: Drupal localization client support
Comment #25
veroniqueg CreditAttribution: veroniqueg commentedHello,
I have the same problem than #24 with Bootstrap that requires jQuery => 1.9.1.
and localization client doens't work with jQuery 1.9
I get the error TypeError: $.browser is undefined
and it is said here
that $.browser has been removed from jQuery 1.9
I use as a workaround the ThemeKey module to switch theme for the Translator role and jQuery Update to select jQuery 1.8 for the translator's theme, but I would rather like using Bootstrap for everyone.
Comment #26
portulacaIt also affects me, Bootstrap jquery update breaks Localization client.
Comment #27
portulacaInstalling the devel version of Localization client solved it for me.