I clicked on "admin/l10n_server/l10n_localpacks/scan" and get this errors. Always reproducible.

    * 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.
    * 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.

No (new) local packages found to scan in sites/default/files/project.

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Postponed (maintainer needs more info)

Inbetween "the" and "module", you should have a modulename. Looks like you did not run update.php when updating l10n_server and skipped where it set up the connector module relationships in the database?

hass’s picture

hass commented

No, I ran the update :-). Checked again now and there are no outstanding updates and I still have this error...

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

You seem to have project records which lack a connector module set then. Not sure why would the update skip those though. Can you look that up in your database?

hass’s picture

hass commented
Status: Postponed (maintainer needs more info) » Active

Yes, "l10n_community_project.connector_module" is empty for all projects...

if ($existing_project->connector_module == 'l10n_localpacks') {

is than FALSE and result in the messages I get... for the reason that there is no 'l10n_localpacks' in the "l10n_community_project.connector_module" field. This may happen... and $existing_project->connector_module is empty for the reason that there is also no other connector inside.

Looks not correct what happens here. l10n_community_update_6000 sets the connector_module and if this update hook has already been executed there is no chance to get the connector_module value into the db field. I'm not sure about the history of the update hook_6000...

I've executed it by hand now... and the errors are gone. Cannot remember how I've upgraded in past, but it should be from official to an official release only. Last update was Alpha3 to Alpha5.

No good idea how this could have failed... maybe I haven't had any connectors enabled while updating...

    $connector_module = module_exists('l10n_localpacks') ? 'l10n_localpacks' : 'l10n_drupalorg';
    $ret[] = update_sql("UPDATE {l10n_community_project} SET connector_module = '". $connector_module ."'");

AHHHH - YES this IS the reason... *damn* - when updating D5 to D6 you are able to execute update hooks with modules disabled! This must be the reason... I ran into this issue so often in different modules with the last weeks... developers are not aware about this or do not have this in mind... have not read the upgrade docs... I don't know...

1. I have disabled all modules when I've updated to D6.
2. Than ran all updates
3. Copied the modules in
4. Ran update again (but modules are nevertheless disabled)

In such a case the below becomes TRUE and the connector info is not added to the connector_module column.

  if (!module_exists('l10n_drupalorg') && !module_exists('l10n_localpacks')) {

I believe this function need to go into the enable or install hook of the l10n_localpacks module... hopefully this is not tooo confusing now...

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (works as designed)

Every newly added project gets their connector set properly, so those who did not fail that update are fine. Did not receive any other reports of this update failing, and that release was a pretty long time ago.