Closed (fixed)
Project:
Localization client
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Nov 2008 at 10:18 UTC
Updated:
15 Feb 2013 at 20:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
gábor hojtsyLooks like user error. You've upgraded the module but did not run update.php so your JavaScript cache was not emptied for regeneration. You site caches an outdated version of the JS of this module.
Comment #2
hass commentedJust a second... if the module does not provide a new update hook I don't need to refresh anything. My status page does not tell me anything I need to regenerate. Only for a test I cleared all my caches now and the problem is gone.
As l10n_client don't have a .install file I expect there is no upgrade path yet. Additonal there is no uninstall code, but variables like "l10n_client_use_server".
Comment #3
gábor hojtsyDon't blame this module if you don't read the docs. Even Drupal core release notes includes to run update.php even when there are no update functions to run at all to clear caches, so all new changes take effect. update.php does that when you run it, you just need to follow the docs. There is nothing we should do about that here. No module is adding empty update functions just to trick you into running update.php. You should run it when you update any of your modules.
As for the uninstall code, looking forward to a patch.
Comment #4
hass commentedUps... never done this within the last years... good to know, but not very user friendly.
Comment #5
gábor hojtsyIt is quite user friendly: always run update.php. It is much less user friendly if you need to look into the .install file code to identify whether there was an update function or not, or even worse, if Drupal needs to inform you after the fact that you missed running update.php.
Comment #6
hass commentedI remember that I've read it that I should run update.php very very long time ago, but never seen any difference until today...
However this is OT here - if Drupal knows that there is a newer version installed - it could simply themself clear the caches automatically on the next page request... this would be user friendly solution.
Comment #7
hass commentedAside some people added menu_rebuild() functions in .install files. This seems also be executed by update.php. I could simply remove googleanalytics_update_6003() and ignore all complains in #262468: Can't configure GA without running update.php... I've stolen this in past from dww's update_status.install
Comment #8
gábor hojtsy#345918: how do you uninstall Localization client? is now marked as duplicate of this issue.
Comment #9
gábor hojtsyThe the moment, the following two settings are available:
- l10n_client_server
- l10n_client_use_server
These two would need to be removed on uninstall. Anybody interested in doing a quick .install file with code to remove these on uninstall? :)
Comment #10
dawehnerhere is one.
Comment #11
dawehnerrerole. Forgot something in the file.
Comment #12
gábor hojtsyAdded a little whitespace (two spaces on the comment line in @file) and committed as-is. To be ported to D7.
Comment #13
gábor hojtsyCommitted as http://drupalcode.org/viewvc/drupal/contributions/modules/l10n_client/l1...
Comment #14
dawehnerI'm confused, i used this syntax for a while, but then people said, its wrong, here is recent example which might be right ;)
http://drupalcode.org/viewvc/drupal/drupal/index.php?revision=1.98&view=...
The patch uses my old code style.
Comment #15
gábor hojtsy@dereine: your patch seems to apply to the D6 version and changes how it works?!
Comment #16
andypostSuppose you need
cache_clear_all('variables', 'cache');after this query, not sure that uninstall process cleans variables cacheComment #17
gábor hojtsy@dereine?
Comment #18
SebCorbin commentedFixed in D7
Comment #19
andypostThis needs backport, D6 still used wide
Comment #20
SebCorbin commentedAs stated in #12, code is already in D6, see http://drupalcode.org/project/l10n_client.git/blob/refs/heads/6.x-2.x:/l...