Closed (fixed)
Project:
Localizer
Version:
5.x-1.10
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Sep 2007 at 17:55 UTC
Updated:
12 Nov 2007 at 13:44 UTC
When a drupal site use 'update status' and 'localizer' modules together, the update status module shows drupal 5.2 outdated, because the localizered drupal core modules (block, menu, taxonomy) have "5.1" drupal version declaration in their .info files.
The problem also founded here: http://drupal.org/node/163646#comment-285211
Comments
Comment #1
edinjapan commentedThe patches that were designed for Drupal 5.2 and Localizer 1.10 (filename=localizer-sites-all-5.2-1.10.tgz) which can be found at http://speedtech.it/drupal-content-localization do not have this issue. If you overwrite with the new patch files the issue should go away. (My site is working fine.)
Note though that for each release of Drupal, this same issue can occur if the Localizer patch files are not updated--and there will always be a bit of a lag there. For example, Drupal just barely did a release to 5.3, but Localizer patch files have not yet been released.
Comment #2
Roberto Gerola commented