[2.6.x] Translation Component not properly functioning

[craigh]

It appears that the Translation Component is present, but failing to operate properly. For example if I intentionally throw an exception, I get hundreds of rows saying WARNING - Translation not found.

this was not true before the upgrade to 2.6.x

this is in use in the Zikula project and in complete dev mode at the moment. We are also have composer issues since the changeover to 2.6.x

any help is appreciated.

ping @Guite @cmfcmf

[craigh]

I forgot to mention that if I add symfony/translation to the composer file it removes all the errors above but then I have a duplicate install of the lib.

[MAXakaWIZARD]

@craigh I also have hundreds of rows saying WARNING - Translation not found in WebProfiles's LOG panel even without throwing any exceptions. But translations do work anyway.

[wouterj]

It seems like this is an issue with the LoggingTranslator, which was added in Symfony 2.6: https://github.com/symfony/Translation/blob/master/LoggingTranslator.php#L102-123

@aitboudad can you please take a look at this, as you created this translator?

[aitboudad]

@wouterj Ok :)
@craigh can you provide me an example reproduce your issue ??

[craigh]

@aitboudad - our zikula package is quite large (compared to symfony) and the example I was using is an additional module to intentionally throw an exception (for testing). If you like I can talk you through setting that up?

zikula: https://github.com/zikula/core
breakit: https://github.com/craigh/BreakIt

[aitboudad]

@craigh of course, just I found an exception here :p http://zikula.org/library/

[craigh]

hmmm. that doesn't demonstrate the problem because that install is still on Symfony 2.5.x 😉

you'll have to install the full product

[aitboudad]

ops I don't see what's going wrong here, "WARNING - Translation not found" it's related to jms/i18n-routing-bundle (missing translate routes)

translation.WARNING: Translation not found. {"id":"zikulaadminmodule_admin_index","domain":"routes","locale":"en"} []

You can ignore logging "routes" channel if you want avoid hundreds of rows or disable logging translation.

[craigh]

@cmfcmf can you comment here? (your implementation of routes, etc)

[cmfcmf]

The warnings are caused by the I18n-Routing bundle indeed. Here it checks whether or not a translation for a given route pattern exists:

if ($routeName === $i18nPattern = $this->translator->trans($routeName, array(), $this->translationDomain, $locale)) {
    $i18nPattern = $route->getPattern();
}

Example:

• Route pattern: /foo/bar
• Translation check: Is a translation for /foo/bar to %LOCALE% available?
• YES: Okay, generate the route using the translated pattern.
• NO: Okay, generate the route using the orginal pattern.

Because our Route patterns already are in English (and therefore need no translation to English), the NO branch is executed all the times. This then causes the warnings in the logging translator.

Maybe the I18n-Routing bundle should not try to translate the Route pattern and then check if it differs from the original pattern, but rather do something like this:

// Check if route is translated.
if (!$this->translator->getCatalogue($locale)->has($routeName, $this->translationDomain)) {
    // No translation found.
    $i18nPattern = $route->getPattern();
} else {
    // Get translation.
    $i18nPattern = $this->translator->trans($routeName, array(), $this->translationDomain, $locale)
}

Conclusion: The warnings are produced by the I18n-Routing bundle, which might need to be fixed.

[craigh]

I can confirm that setting logging: false removes the errors, but is obviously only a workaround.

[craigh]

@aitboudad - closing this ticket as it appears to be a problem with schmittjoh/JMSI18nRoutingBundle, I'm hoping they will find a fix! thank you for your attention 😄

[Cedoriku]

Sorry to interrupt,
I am (we are) having this problem also, yet not using JMSI18nRoutingBundle, but Doctrine Translatable Plugin. The log file shows that the translator is trying to translate all the options in all the selects (choiceList) in all the forms! Having big Forms with lot of choiceList and Entity selects inputs, some pages are just crashing...

Help!

[aitboudad]

@Cedoriku Would you mind preparing a simple example reproducing the problem ?

[Cedoriku]

Yes I will do that tomorrow morning ASAP.
These are just simple formTypes with choiceLists (select), and the log file shows that the Translator tries to translate every option label in the select, even for entities choiceLists that are already handled by the Translatable Plugin. So I'm not sure it has something to do with the plugin.

For each option, we get a line of that kind (don't have it in front of me right now):

Translation.WARNING.Translation not found [...] {id:"The option label", domaine:message, locale:fr}

[Cedoriku]

After reflexion, we're actually not sure if the crash comes from that problem, as we just encountered it. It may come from other bugs in our code, but searching about it, we found that log problem.

[Cedoriku]

the proper log message is:
[2015-02-04 18:40:59] translation.WARNING: Translation not found. {"id":"ROUMANIE","domain":"messages","locale":"fr"} []

[aitboudad]

@Cedoriku So to be sure, can you disable logging to check if the problem persist or not ?

# app/config/config.yml
framework:
    translator: { logging:  false }

[Cedoriku]

Ok.
When Translator logging set to false, the warnings disappear.

[damijanc]

Hi I have a similar issue:

Here is my twig snippet to reproduce the behavior:

{{ form_widget(form.address, { 'attr': {
                                    'class': 'form-control phone',
                                    'placeholder':'street.and.number'|trans,
                                    'data-toggle':'tooltip',
                                    'title':'street.and.number.tooltip'|trans
                                } }) }}

This code will produce false missing translation warnings.

[xabbuh]

@damijanc Can you check if #15048 solves your issue?