Disable Localization client on certain pages.
zmove - November 5, 2008 - 08:02
| Project: | Localization client |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi,
It would be cool to be able to disable the localization client on some pages, cause It brings lots of problem with some others modules that use javascript.
It would allow to not beeing obliged to go to the module page and manually disable it each time we have a javascript problem.
It could work a little like the block visibility setting, I think a major part of the code can be copied from it.
#1
Wouldn't it be best to try and solve the JavaScript issues? :)
#2
I'm not experienced in javascript debugging for that. When I have to debug a code I wrote, it's ok, when I have to find why some javascript function are not triggered, it's not the same....
In addition, l10n client is enabled when you are in developping mode, you often disable it when your website become in production, that's why I can't spend several days in javascript debugging for a thing that will not be in production mode.
It just could be a nice feature, instead of going to the module page (which take soooo much time to load in drupal 6) to be able to disable the l10n feature on some page, or maybe, like devel module propose, a block with a link to disable the module quickly.
It's not a major issue, just an idea for a little but usefull addition.
zmove
#3
i also think this feature would be nice.
no because javascript problems but when administraiting while building the place.
i am upgrading a site and i am maybe two hours debuging a problem, organizing contents, trying a new plugin and then i have some time and i transllate the main menus for the people that will create contents.
it would be nice, no to have to desactivate the plugin and then activate again or have to create a new user and rol.
thanks for your great plugin: transllating now in drupal is much much easyier :)
#4
@candelas: why not disable the module then?
#5
Gábor Hojtsy: it is a time question. you are working on the site, you see a mistake, you make it able, change the mistake and turn it off.
if you have to go to the moduls page, make it able, go back to the mistake page and reload it is a more time.
and if it happen several times, then it becames not practical.
only because of that :)
but maybe you have more things to do ?¿?
#6
If you'd need to go to the settings page to enable it, then fix the mistake and go to the settings page to disable it, then what is the difference between that and replacing "settings page" with "modules page". Having an on/off setting for a module is generally frowned upon, since that is what enabling/disabling the module is for. Also, this issue seems to be like disabling the module on certain page indefinitely, not as a one time on/off setting, so that sounds like a different issue altogether.