Closed (works as designed)
Project:
Localization server
Version:
6.x-1.0-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Apr 2009 at 22:22 UTC
Updated:
18 Jan 2010 at 13:02 UTC
After I've upgraded D6 version from alpha2 to alpha3 I've got these errors (red message box):
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
* An existing project under the URI is already handled by the module. Not possible to add it with l10n_localpacks.
Sorry I'm in a migration process and do not have the time to take a look into the code now... but I'd don't like to loose it, so post it here.
Comments
Comment #1
gábor hojtsyWell, looks like you've had messages which was not handled with the localpacks module.
Comment #2
hass commentedI have upgraded OG 1.1 -> 1.3, Views 2.1 -> 2.5 and l10n_server alpha2 -> alpha3 in one update.php run... this site does not have more modules installed except google analytics and potx if I haven't missed one.
Comment #3
gábor hojtsyStill looks like you've used l10n_drupalorg to set up these projects up or you had both connectors enabled on update so the module picked the drupalorg one. If you had more then one connector enabled on the update when it set up the connector relations, it could not tell which module used which connector, so it might have decided wrong. Fix by updating your connector values in the project table, there is not much we can do in an automated way.