Numerous ezi18n warnings after upgrade 3.7.6 - 3.8.7

Next topic

Author	Message
Nathan Kelly	Wednesday 28 March 2007 1:30:16 am Hi All, I wonder if anyone can tell me why I get these ezi18n warnings and how I can avoid them, the site seems to run fine but these warnings are really annoying as they go forever and it makes the debug output a pain to work with. Timing: Mar 28 2007 18:13:50 Module start 'content' Warning: ezi18n Mar 28 2007 18:13:50 No translation for file(translation.ts) in context(lib/template): 'The maximum nesting level of 40 has been reached. The execution is stopped to avoid infinite recursion.' with comment() Warning: ezi18n Mar 28 2007 18:13:50 No translation for file(translation.ts) in context(kernel/classes/datatypes): 'XML block' with comment(Datatype name) Timing: Mar 28 2007 18:13:50 Module end 'content' Warning: ezi18n Mar 28 2007 18:13:50 No translation for file(translation.ts) in context(kernel/navigationpart): 'Content structure' with comment(Navigation part) Warning: ezi18n Mar 28 2007 18:13:50 No translation for file(translation.ts) in context(kernel/navigationpart): 'Media library' with comment(Navigation part) Warning: ezi18n Mar 28 2007 18:13:50 No translation for file(translation.ts) in context(kernel/navigationpart): 'User accounts' with comment(Navigation part) And so on for about a hundred iterations... Do I need to change some settings somewhere, or is this just the norm with 3.8.x? Cheers! Pardon me while I burst into flames...
Ole Marius Smestad	Wednesday 28 March 2007 2:31:42 am Hello Nathan, Did you change the locale of the site during this upgrade? An example of the locale settings can be seen below, from site.ini: [RegionalSettings] Locale=eng-GB ContentObjectLocale=eng-GB ShowUntranslatedObjects=disabled SiteLanguageList[] SiteLanguageList[]=eng-GB TextTranslation=disabled What does your RegionalSettings look like? -- Ole Marius Smestad Lead Engineer eZ Publish Member of the Community Project Board
Nathan Kelly	Wednesday 28 March 2007 2:45:26 am Hi Ole, I didn't do the upgrade personally I had it done by someone else, basically my settings/siteaccess/[site]/site.ini.append.php looks like this: [RegionalSettings] Locale=eng-AU ContentObjectLocale=eng-AU TextTranslation=enabled SiteLanguageList[]=eng-AU ShowUntranslatedObjects=disabled I'm just about to have the site translated into french and about 3 - 4 other languages so I'm assuming these settings won't stay the same anyway. Cheers. Pardon me while I burst into flames...
Nathan Kelly	Wednesday 28 March 2007 2:47:56 am Oh, and no we always had the locale set to eng-AU. Cheers. Pardon me while I burst into flames...
Nathan Kelly	Wednesday 28 March 2007 2:56:04 am Ok I changed my ini to: [RegionalSettings] Locale=eng-AU ContentObjectLocale=eng-AU TextTranslation=disabled SiteLanguageList[] SiteLanguageList[]=eng-AU ShowUntranslatedObjects=disabled And the warnings are gone, that make the debug a lot cleaner. So if I translate for french in a new site access I need to enable TextTranslation for that site access along with french locale settings, is that right? If so I assume I'll get warnings for items that aren't translated? Cheers. Pardon me while I burst into flames...
Ole Marius Smestad	Wednesday 28 March 2007 4:00:38 am Yes, this setting: TextTranslation=disabled will solve your problem with the warnings. However, let me explain what is happening: in 3.7.6 there was no translation file for locale eng-AU included, so the system did not try to load any translations. With 3.8.7, there is a translation file included, the only problem is that this file, (I just checked it) does not contain any translations, thus giving you the warnings you describe. In my opinion, this looks like a glitch, since if there are no translations, the file is not really needed. I have made an issue for this here: http://issues.ez.no/IssueView.php?Id=10527 Regarding other siteaccesses, you are correct. You will only get warnings for items which are not translated. This warning will only be issued if you try to fetch a translation where none is found. Thanks for letting us know about this, and I hope this clears up your question. -- Ole Marius Smestad Lead Engineer eZ Publish Member of the Community Project Board
Nathan Kelly	Wednesday 28 March 2007 3:30:55 pm Thanks Ole, Yes it clears up my question. And I have to agree that it seems odd it happens, particularly on the default locale, it seems as though if the default locale it in use it shouldn't even be trying to translate, I would think this is just using resources for no reason. However TextTranslation=disabled is obviously the switch so I assume those resources aren't in use once this is disabled? Cheers. Pardon me while I burst into flames...