Problem/Motivation

Module does not see translations. Neither local nor external. The result of check is always "missing translations" for all modules. I found it out when started new project. The same problem on previous projects.

Downgrade to 2.0 version fixed problem and works fine. Checked on a local and external web server.

The Drupal cache backend is overridden by the DrupalFakeCache. When this override was removed, the translation updates got working again.

Proposed resolution

1. Document this behavior.
2. Make translation state independent from disabling cache.

Comments

ruslan.murzin created an issue. See original summary.

sutharsan’s picture

Status: Active » Postponed (maintainer needs more info)

I can not reproduce this situation on a clean install.
Can you describe the steps to reproduce on a new drupal installation.

ruslan.murzin’s picture

Clean install really works fine. I just checked. Maybe conflict with other module. I'll try to reproduce error later.

ruslan.murzin’s picture

Today I spent few hours trying to reproduce an error but I couldn't. I added all modules (the problem site has), one by one but nothing. From other side I still have the site where "Localization update" module does not see updates. I don't know what to do :)

I can backup the site and give you a link in private, if you want.

sutharsan’s picture

I can backup the site and give you a link in private, if you want.

That is ok.

sutharsan’s picture

@ruslan.murzin, I'm still interested if you can share a backup.

ruslan.murzin’s picture

I sent you a link via personal contact form the same day you answered. I thought you have no time to check backup ))

Could you send me something and I'll reply from email client.

Link to my contact form https://www.drupal.org/user/2319166/contact

sutharsan’s picture

Title: Module does not see translations » Translation not found when DrupalFakeCache is used.
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active

I have installed the website I got provided by @ruslan.murzin and investigated the problem.
It is caused by a combination of two things. The latest release of l10n_update stores the translation in the cache bin. The provided site uses code to fully disable the cache using the DrupalFakeCache cache backend. Once the a normally caching backend is restored, the translations get recognized again.

The use of DrupalFakeCache was similar to https://pastebin.com/Pe6EdvBt

ricovandevin’s picture

Confirmed this issue with Localization update 7.x-2.2.