Help talk:Extension:Translate/Configuration

You can request assistance for configuration issues at #mediawiki-i18n on FreeNode; after your install is successfully completed, it's appreciated if you write down here what would have helped you so that the documentation can be improved (what's missing, what's unclear etc.), even if you don't have time to do it yourself.

Cache

The most frequent questions about configuration seem related to caching, perhaps the page should be checked with this regard. It currently seems contradictory, as it says "$wgCacheDirectory must be configured correctly" but below it assumes it isn't and says "FileCachedMessageIndex needs $wgCacheDirectory to be functional": most people won't understand they actually should use it to fix their problems, as it often seems to. I don't understand anything about this so I can't correct/improve the instructions. Nemo 09:47, 29 February 2012 (UTC)

Is this page really useful?

Yesterday I went through the installation of the MediaWiki Language Extension Bundle for a personal pet project: http://espiral.org

The installation went well without major issues. The only point where I ot stuck was this Help:Extension:Translate/Configuration page. It's really confusing for a newcomer. But then... it turns out that Help:Extension:Translate/Installation leaves already a working environment? I guess I will find the need to fine tune details along the way. Still, the impression the documentation gives is that nothing will really work before you go through this "configuration". The reality seems to be that your installation instructions provide a default configuration that Just Works.--Qgil (talk) 07:55, 17 July 2013 (UTC)

Thanks for the useful feedback. Sometimes yes, it's useful and should actually be more prominent, see action above. However you're right, maybe the page could be renamed to /Advanced configuration or /All configuration. Help:Extension:Translate/Installation (quite useless itself now) already implies this page is usually not required; I'll clarify it in the lead. --Nemo 08:34, 17 July 2013 (UTC)

$wgTranslateLanguageFallbacks

I have a Greek wiki ($wgLanguageCode = "el";) and I want to have English (en) as the default aid. If I add "en" in my user preferences it works just fine. But if I put $wgTranslateLanguageFallbacks['el'] = 'en'; in LocalSettings.php nothing happens. Am I missing something? And a second question: Is it possible to have "en" as a global aid, i.e. for all languages? I tried $wgTranslateLanguageFallbacks['*'] = 'en'; as well as $wgTranslateLanguageFallbacks = 'en'; but none of them works. --Ioannis Protonotarios 00:30, 9 September 2013 (UTC)

This reply is obviously way too late for you, but for anyone else wondering: $wgTranslateLanguageFallbacks works as it should, but only if the assistant languages ("Assistant languages:") in a user's preferences (under "Editing") is set to default (as in, literally the string "default"). As for the second question (global translation aid), I don't know unfortunately. Jon Harald Søby (talk) 08:50, 1 February 2021 (UTC)

Machine translation

I've tried multiple way to set $wgTranslateTranslationServices but I've never managed to get something to happen (on a labs-vagrant wiki). No requests can be seen and nothing is logged, though eval.php shows the configuration is applied, so I have no idea where the problem could be, let alone investigate it. --Nemo 10:03, 3 July 2014 (UTC)

Same here ProfaneServitor (talk) 02:10, 22 December 2022 (UTC)

big page doesnt load

i saved a site with ~1500 translation units and it reaches time out on load is there a way to set variables so it still loads?

What do you mean with "load"? Do you have a link? Nemo 09:01, 20 March 2016 (UTC)

Page translation

Parts copied from Translate.php can not be translated. Because of this, vast majority of the page can not be translated and the rest does not worth the effort (at least to me and BenyElbis). How to solve this? --Dvorapa (talk) 16:06, 16 April 2020 (UTC)