I don't think so. Translations in question have nothing to do with Translatable extension, nor with queries at all. So, IF this is an issue, is a symfony2 one.
On Sep 27, 9:24 am, Gediminas Morkevicius <[email protected]> wrote: > It maybe doctrine cache > related:https://github.com/l3pp4rd/DoctrineExtensions/issues/158 > > if that does not help, maybe there was some issue introduced with 2.0.3 > release > > > > > > > > On Tue, Sep 27, 2011 at 5:49 AM, ryan weaver <[email protected]> wrote: > > Hi there! > > > I don't know anything about this issue, but I do know that you're the > > second person that's posted on the board today about it. > > > There is a ticket open describing your issue - > >https://github.com/symfony/symfony/issues/2250. I'd recommend commenting > > on that ticket and adding any other information you have. > > > Thanks! > > > Ryan Weaver > > US Office Head & Trainer - KnpLabs - Nashville, TN > >http://www.knplabs.com<http://www.knplabs.com/en> > >http://www.thatsquality.com > > Twitter: @weaverryan > > > 2011/9/26 Nicolò Pignatelli <[email protected]> > > >> Hello everybody. > > >> I'm using Symfony 2.0.3 and I noticed the following problem. > > >> This is my scenario: > >> - Cache cleared, environment dev (but the same happens with prod). > >> - First request to my page, a service set the session locale to 'it' > >> - Some identifiers need to be translated; the it catalogue does not > >> exists, so the en catalogue is used to translate those identifiers. > >> - Identifiers are correctly translated with the en fallback. > > >> - The page is reloaded (cache is already warmed up): now the fallback > >> is NOT working and I can see my identifiers instead of translation > >> strings from the catalogue. > >> - If I clear cache and reload my page again, the scenario reset to the > >> first point. > > >> Any ideas? > >> Thank you! > > >> -- > >> If you want to report a vulnerability issue on symfony, please send it to > >> security at symfony-project.com > > >> You received this message because you are subscribed to the Google > >> Groups "symfony developers" group. > >> To post to this group, send email to [email protected] > >> To unsubscribe from this group, send email to > >> [email protected] > >> For more options, visit this group at > >>http://groups.google.com/group/symfony-devs?hl=en > > > -- > > If you want to report a vulnerability issue on symfony, please send it to > > security at symfony-project.com > > > You received this message because you are subscribed to the Google > > Groups "symfony developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/symfony-devs?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
