Extension talk:Translate

Jump to navigation Jump to search

About this board


Translate Plugin is not loading the Suggestions on the "right side" of the translate view

7 (talkcontribs)

I just set up a frash mediawiki installation and installes all i needed for translating my wiki and the content. manual translations just working like expected but in that view i do not get any suggestions shown? Maybe there is any logfile i could check or is that due to a lack of configuration? (it is pretty much default). Im just wondering that is show forever "Loading..." and no content is shown as in some screenshots of that plugin.

Tuxxic (talkcontribs)

Did you configure TTMServer in the LocalSettings.php ? Link : Help:Extension:Translate/Configuration/fr

$wgTranslateTranslationServices = array(); $wgTranslateTranslationServices['TTMServer'] = array( 'database' => false, // Passed to wfGetDB 'cutoff' => 0.75, 'type' => 'ttmserver', 'public' => false, ); (talkcontribs)

that is configured in the Translate.php file like in the default with that 4 entries, so i guess i do not need to do that again in the LocalSettings file, or?

Tuxxic (talkcontribs)

You won't know unless you try, inmy opinion ;) (talkcontribs)

well that did not help is always stays at "loading..."... any other ideas?

Cloud668 (talkcontribs)

I am also having a similar issue on 1.31/MLEB 2018.07 (PHP 7.2.9 cgi-fcgi and on IIS if that matters for whatever reasons), but in my case, the translation aids column is loading fine for page translations but not file based message groups, which only ever showed the "Loading..." string. I've tested some of the same files along with the custom FFS/YAML group configs on an older wiki I have (1.28/MLEB 2016.10/PHP 5.6.11 fpm-fcgi on Ubuntu) and it worked fine there. Both wikis are using the default DB TTM.

On the older wiki, I noticed that the column only loaded after running createMessageIndex.php, but running that on the newer one didn't really help solve the problem.

I'm not sure what could be causing the issue on the newer wiki. Any help is appreciated.

Cloud668 (talkcontribs)

Digging a little into the access logs, it seems that in my case, the problem that the aids never loaded was that the translationaids API call for all file based messages for some reason only ever returns this:

"code":"nomessagefortitle","info":"Title does not correspond to a translatable message"
Reply to "Translate Plugin is not loading the Suggestions on the "right side" of the translate view"

Error : "Saving the translation failed: This namespace is reserved for content page translations."

2 (talkcontribs)


Please help,

I am using Mediawiki 1.30

and Language Extension Bundle MediaWikiLanguageExtensionBundle-2018.03.tar.bz2

When I try to translate this page,


I've enabled anonymous translating, so you can check ($wgGroupPermissions['*']['translate'] = true;)

I get the following errors :

on the screen :

"Saving the translation failed: This namespace is reserved for content page translations. The page you are trying to edit does not seem to correspond any page marked for translation."

In the javascript console :


Uncaught RangeError: Maximum call stack size exceeded

    at jQuery.fn.init.push (<anonymous>)

    at superMatcher (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:36)

    at Sizzle.select (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=foreground&version=0zcenri:38)



I've tried to disable all other extensions.

My LocalSettings.php :

wfLoadExtension( 'Babel' );

wfLoadExtension( 'cldr' );

wfLoadExtension( 'CleanChanges' );

$wgCCTrailerFilter = true;

$wgCCUserFilter = false;

$wgDefaultUserOptions['usenewrc'] = 1;

wfLoadExtension( 'LocalisationUpdate' );

$wgLocalisationUpdateDirectory = "$IP/cache";

require_once "$IP/extensions/Translate/Translate.php";

$wgGroupPermissions['user']['translate'] = true;

$wgGroupPermissions['user']['translate-messagereview'] = true;

$wgGroupPermissions['user']['translate-groupreview'] = true;

$wgGroupPermissions['user']['translate-import'] = true;

$wgGroupPermissions['sysop']['pagetranslation'] = true;

$wgGroupPermissions['sysop']['translate-manage'] = true;

$wgTranslateDocumentationLanguageCode = 'qqq';

$wgExtraLanguageNames['qqq'] = 'Message documentation'; # No linguistic content. Used for documenting messages

wfLoadExtension( 'UniversalLanguageSelector' );

Nikerabbit (talkcontribs)
Reply to "Error : "Saving the translation failed: This namespace is reserved for content page translations.""

A Bug in the tool associated with heading

Summary by Nikerabbit
Ranjithsiji (talkcontribs)

If I start a new translation using this tool it will not ask for the new title of the new article in new language instead it uses the title from source language resulting a lot of articles created in the foreign language in a wiki. for example, I try to translate an article from Hindi to Engish in English wiki it will start the article title as the title in Hindi. Resulting creating an article with a title in Hindi in English wiki. The UI does not look like we can edit the title. A popup box or an intermediate title asking box is helpful to solve this problem.

Nikerabbit (talkcontribs)

Are there Active steps planned for the internationalization of category names?

Summary by Nikerabbit

Some plans yes, not very active. It is a question of MediaWiki core rather than Translate.

Atef81 (talkcontribs)

I am starting a multilingual environment that will have mainly 4 languages. The problem is that the language that will have the most content is Arabic, and my aim is to get as much content translated to the other languages.

When I tried the Translate extension, it worked, but having the categories names in Arabic then "/en" and "/fr" is not practical as non Arabic speakers will find it impossible to understand.

I checked several forums and read that there are steps in the pipeline to rectify this. However, I can't find enough information about this on the Extension official page.

I am trying to start from a page like this and reach an end result like this, where page title and category names are translated to the article language.

Is this likely to be an option soon, or I need to setup a family of wikis that share the same resources like this Mediawiki manual?


Nikerabbit (talkcontribs)

Thanks for asking!

Due to possible naming conflicts, it's not a good idea to translate the actual page titles, unless you disambiguate them with a language code anyway.

But what you can do is to use the feature to translate the (category) page title. This does not affect the URL of the page, nor any links to that page. However, there are feature requests for MediaWiki core to use this translated title in links, including the category list at the bottom of the pages. It is not clear, though, when these will happen. I believe the features are not controversial, but some performance concerns must be taken into account while implementing them.

Some links:

Error using ElasticSearch in 1.27

Summary by Nikerabbit

ElasticSearch backend is not working on MediaWiki 1.27 and MLEB. Recommending to upgrade MediaWiki to use ElasticSearch backend.

Lsilverman (talkcontribs)

I'm running MW 1.27 with CirrusSearch+Elastica, which requires ElasticSearch 1.X. Cirrus and Elastica are pinned to the REL1_27 branches.

My wiki emailed me the following error upon attempting to translate my first page:

PHP Fatal error:  Call to undefined method Elastica\Query\BoolQuery::addFilter() in /var/www/devmediawiki-1.27/w/extensions/Translate/ttmserver/ElasticSearchTTMServer.php on line 282

LocalSettings.php portion looks like this:

$wgTranslateTranslationServices['TTMServer'] = array(
        'type' => 'ttmserver',
        'class' => 'ElasticSearchTTMServer',
        'cutoff' => 0.75,
         * See http://elastica.io/getting-started/installation.html
         * See https://github.com/ruflin/Elastica/blob/master/lib/Elastica/Client.php
        'config' => This will be passed to \Elastica\Client
Lsilverman (talkcontribs)

Tracing the problem further, I see that REL1_27 of Elastica includes via composer ruflin/elastica 2.3.1.

elastica 2.3.1's version of Elastica/Query/BoolQuery.php does not contain the function addFilter().

Nikerabbit (talkcontribs)

Unfortunately this incompatibility has not been caught in our testing. Given 1.29 is soon going to be released, which means we are going to drop support for 1.27 from MLEB and Translate, I would encourage you to start planning for an upgrade and use the database backend for translation memory for the time being.

Lsilverman (talkcontribs)

We use Active Directory and LDAP. The LDAP auth plugins have not been updated in some time, and as a result we are stuck on 1.27.

Translation in the source language, English!

Summary by Nikerabbit

Manual:$wgPageLanguageUseDB can be used to change page source language.

Donxello (talkcontribs)

Hi, we have an English Wiki but a German article to be translated. By default the extension marks the article as English and consequently we get

Translations to this language in this group have been disabled. Reason:

English is the source language of this page.

Any ideas how to mark this article as German and how to allow translations in the source language?



Nikerabbit (talkcontribs)

Hopefully you have recent enough MediaWiki to enable Manual:$wgPageLanguageUseDB in LocalSettings.php. Then you can use this feature to change the page content language to German. But you should do that before marking the page for translation.

Summary by Nikerabbit

An issue with older versions of MediaWiki, no longer present in newer versions as far as I know. (talkcontribs)

(Moved from support desk and modified) I have translate installed on my wiki, but when I try to add a translation for a page I get the following error. Saving the translation failed: Unknown error: "tpt-unknown-page" FuzzyBot also isn't running when I mark a page for translation. Running runJobs.php did nothing. Running showJobs.php gave the result 0. Any help would be great. Thanks.

Tuxxic (talkcontribs)


Did you run runJobs.php from your actual PHP CLI instead of using an extension like MaintenanceShell ?

I had the same problem but running from CLI solved it.

In fact, in my case I'd like to runJobs eachtime I mark a page for translation, since it isn't done automatically ... :)

This post was hidden by (history) (talkcontribs)

I ran it using SSH.

2002:43F4:3186:1234:35AE:218:4B7:62E5 (talkcontribs)

Please help me.

Nikerabbit (talkcontribs)

So if runJobs.php doesn't work, does running extensions/Translate/scripts/createMessageIndex.php work? (talkcontribs)

That worked (talkcontribs)

FuzzyBot still isn't creating the /en subpages though.

Nikerabbit (talkcontribs)

I don't have much info, so my best guess is that either the JobQueue is seriously broken and not running jobs, or there is some kind of error that prevents Translate from adding jobs to the queue. Enabling PHP error reporting as well as logging exceptions could help to identify the cause. For example:

error_reporting( E_ALL | E_STRICT );

$wgShowExceptionDetails = true;

$wgDebugLogGroups['exception'] = ini_get( 'error_log' ); 

$wgDebugLogGroups['error'] = ini_get( 'error_log' );

$wgDebugLogGroups['fatal'] = ini_get( 'error_log' );

Tuxxic (talkcontribs)

Edit : So here is what I get in my PHP error log after :

  • Adding a new chunk of text
  • Marking therefore the page for translation
  • then trying to translate it afterwards

I don't experience the problem if I update an already existing message group, if it can help you.

Thanks for advice on error logs :)

2017-05-03 12:01:19 SERVERNAME database-name: [3f588d59648bf5725b6fb31e] /index.php?title=Sp%C3%A9cial:PageTranslation   DBUnexpectedError from line 2866 of C:\mediawiki-path\includes\libs\rdbms\database\Database.php: MWCallableUpdate::doUpdate: Cannot flush snapshot because writes are pending (JobQueueDB::doBatchPush).

#0 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1092): Database->flushSnapshot(string)

#1 [internal function]: LoadBalancer->{closure}(DatabaseMysqli)

#2 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1390): call_user_func_array(Closure, array)

#3 C:\mediawiki-path\includes\libs\rdbms\loadbalancer\LoadBalancer.php(1100): LoadBalancer->forEachOpenMasterConnection(Closure)

#4 [internal function]: LoadBalancer->beginMasterChanges(string)

#5 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(176): call_user_func_array(array, array)

#6 [internal function]: LBFactory->{closure}(LoadBalancer, string, array)

#7 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactorySimple.php(134): call_user_func_array(Closure, array)

#8 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(179): LBFactorySimple->forEachLB(Closure, array)

#9 C:\mediawiki-path\includes\libs\rdbms\lbfactory\LBFactory.php(200): LBFactory->forEachLBCallMethod(string, array)

#10 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(262): LBFactory->beginMasterChanges(string)

#11 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(225): DeferredUpdates::runUpdate(MWCallableUpdate, LBFactorySimple, integer)

#12 C:\mediawiki-path\includes\deferred\DeferredUpdates.php(133): DeferredUpdates::execute(array, string, integer)

#13 C:\mediawiki-path\includes\MediaWiki.php(891): DeferredUpdates::doUpdates(string)

#14 C:\mediawiki-path\includes\MediaWiki.php(720): MediaWiki->restInPeace(string)

#15 C:\mediawiki-path\includes\MediaWiki.php(739): MediaWiki->{closure}()

#16 C:\mediawiki-path\includes\MediaWiki.php(543): MediaWiki->doPostOutputShutdown(string)

#17 C:\mediawiki-path\index.php(43): MediaWiki->run()

#18 {main}

Nikerabbit (talkcontribs)
Tuxxic (talkcontribs)

In my case, 1.28.2, but I experienced it also on 1.28.0. (talkcontribs)

Hi Nikerabbit,

I got same problem Saving the translation failed: Unknown error: "tpt-unknown-page"

Wiki version 1.28.1

Use extensions/Translate/scripts/createMessageIndex.php is OK, but translate new page doesn't work

Nikerabbit (talkcontribs)

I don't know if this is specific to 1.28, but I just tried with MediaWiki vagrant on a clean install, using default MLEB configuration, and I did not have this problem.

Tuxxic (talkcontribs)

Thanks for testing.

Would you be interested in the list of my extensions installed, in order to see which one might be the culprit then ?

Nikerabbit (talkcontribs)

There is some info at https://phabricator.wikimedia.org/T100085 about different but possible related error message. It says it would be about exceptions.

I also can reproduce "Cannot flush snapshot" errors on my wiki now, so let's see if I can debug further. (talkcontribs)

Thanks for debug Nikerabbit

ShInKurO (talkcontribs)

Hi all,

I've installed Translate extension (2017.07) on my wiki (mediawiki 1.27). When I try to translate a translable article the translation progressbar of the GUI doesn't go on when I press "Save translation" and I don't obtain any translation of my page after I've finished to translate at all. I've configured $wgJobRunRate to 0 and setted from console configuration of my hosting the cron job php script as written on mediawiki documentation (I cannot access to console).

Any idea about how solve this problem?

Thanks in advance!

Nikerabbit (talkcontribs)

Please open a new thread and check why the saving of the translations is failing, for example using PHP logs or your browser's developer tool and network tab.

ShInKurO (talkcontribs)

new thread opened! :)

Save button doesn't work

Summary by Nikerabbit

Incompatibility with 1.27.3 resolvable by updating MediaWiki.

ShInKurO (talkcontribs)

Hi all,

I've installed Translate extension (2017.07) on my wiki (mediawiki 1.27). When I try to translate a translable article the translation progressbar of the GUI doesn't go on when I press "Save translation" and I don't obtain any translation of my page after I've finished to translate at all. I've configured $wgJobRunRate to 0 and setted from console configuration of my hosting the cron job php script as written on mediawiki documentation (I cannot access to console).

On Firefox console I've these log:

when I write transation:

When I press save button:


error    Object

code    nomessagefortitle

info    Title does not correspond to a translatable message

error    Object

code    unknownerror

info    Unknown error: "tpt-unknown-page"

Any idea about how solve this problem?

Thanks in advance!

Nikerabbit (talkcontribs)
ShInKurO (talkcontribs)

Ok after some test my hosting doesn't support the launch of a script in its cron-mode tool, in fact the launch of runJob.php from that cron tool reply: "This script must be run from the command line cron". At this point shall I configure $wgJobRunRate to 1 again? will the translate extension work in these conditions?

Nikerabbit (talkcontribs)

If your wiki has enough traffic, it might just work okay.

ShInKurO (talkcontribs)

Also setting $wgJobRunRate to 1 my errors on click on save button remain:

code    nomessagefortitle

info    Title does not correspond to a translatable message

code unknownerror

info Unknown error: "tpt-unknown-page"

Nikerabbit (talkcontribs)

Yeah, either there hasn't been enough traffic (requests) to process that job (likely), or the job failed to process for some reason (less likely).

ShInKurO (talkcontribs)

Is there a way to log runJob script from browser (modifing some php source file script I suppose, but what php script? Mantainance.php?)?I

Nikerabbit (talkcontribs)

You don't need any specific page, just making requests to the main page URL should start draining the queue.

ShInKurO (talkcontribs)

Sure but what should read from an http request (with firebug I suppose) from runJob.php to give me help to fix this issue?

Nikerabbit (talkcontribs)

There is no output in the requests about the jobs. For that you have to resort to server side logging, which you may have to configure separately to log at the right verbosity.

ShInKurO (talkcontribs)

The problem is I have no access to server side, I can only upload file or execute in a gui kind a periodical job (a call to an url). For this reason I ask if there is a way to have a log written in a file or similar setting a variable or modifyng a script...

Nikerabbit (talkcontribs)

There are many configuration options for logging, and you can also configure the logs to be written in a file. Have look at DefaultSettings.php.

ShInKurO (talkcontribs)

Ok I've enabled some debug mode from LocalSettings.php and I've these errors when I load my homepage:

Notice: Use of undefined constant DB_REPLICA - assumed 'DB_REPLICA' in ../extensions/Translate/tag/TranslatablePage.php on line 874

And when I try to translate a debug row is written in this way:

[error] [221f291bb92735e24646966f] /index.php?title=Speciale:Traduci&group=page-I+5+Numeri&language=en&action=page&filter= ErrorException from line 874 of ../extensions/Translate/tag/TranslatablePage.php: PHP Notice: Use of undefined constant DB_REPLICA - assumed 'DB_REPLICA'

Nikerabbit (talkcontribs)
ShInKurO (talkcontribs)

I've actually mediawiki 1.27.1, so to have all work properly shall I upgrade mediawiki to 1.27.3 (latest avaible) or upgrade to 1.28+ mantaining actual version of Translate or downgrade Translate (what version?) ?

Nikerabbit (talkcontribs)

1.28+ should work. 1.27.3 won't. Do note that in next MLEB release we are likely going to drop support for 1.27.

ShInKurO (talkcontribs)

Ok I've update mediawiki to 1.29 and Translate to the latest version and now it works, thanks :)

Last question: if I want to remove a translation shall I remove all translations? I've tried to remove a translation (I've selected french instead of english and I've put english translation into french page) without result until I've not removed my page from Translate control.

Nikerabbit (talkcontribs)

Use the Delete action on page "Page/fr", that should remove the translations properly.

Adapting content based on user language preference

MarcoSwart (talkcontribs)

Is there a way to find out what the the preferred language of a user is and have a template present some information based on this preference? On Dutch Wiktionary we have many non-Dutch editors making valuable contributions and probably also readers who are learning our language. Because our content is structured by nature, we have a large set of templates presenting readers and editors with interface-type information (language, part of speech, grammatical types, context labels). If we knew the preferred language of the reader, we could present a translation of this type of information e.g. in a tooltip.

Nikerabbit (talkcontribs)

The regular assumption is that the currently selected interface language is the user's preferred language, and use {{int:messagename}} to display text in that language. With JavaScript you could ask ULS for guesses for preferred language.

PHP 7.1 - can't access translated pages: [] operator not supported for strings

Summary last edited by 24pm 12:35, 30 May 2018 5 months ago

Use the latest MLEB release where this is fixed.

-- It is not fixed for release 2017.07 as for 2018.05.30. Solution is to add array initialization in line 634:

$result = array(); 
$result[] = 'tpt-patrolling-blocked';


Lanthanis (talkcontribs)

Using MW 1.27.4 with LDAP Authentication and PHP7.1.

You get this error when attempting to use the short array push syntax on a string.

Exception encountered, of type "Error"
[2f682d8f66d60d00c36c9d4b] /wiki/Entypo/en Error from line 634 of C:\inetpub\wwwroot\mywiki\extensions\Translate\tag\PageTranslationHooks.php: [] operator not supported for strings
#0 C:\inetpub\wwwroot\mywiki\includes\Hooks.php(195): PageTranslationHooks::preventPatrolling(Title, User, string, string)
#1 C:\inetpub\wwwroot\mywiki\includes\Title.php(2094): Hooks::run(string, array)
#2 C:\inetpub\wwwroot\mywiki\includes\Title.php(2543): Title->checkPermissionHooks(string, User, array, string, boolean)
#3 C:\inetpub\wwwroot\mywiki\includes\Title.php(1933): Title->getUserPermissionsErrorsInternal(string, User, string, boolean)
#4 C:\inetpub\wwwroot\mywiki\includes\Title.php(1915): Title->userCan(string, User, boolean)
#5 C:\inetpub\wwwroot\mywiki\includes\page\Article.php(1081): Title->quickUserCan(string, User)
#6 C:\inetpub\wwwroot\mywiki\includes\page\Article.php(1059): Article->showPatrolFooter()
#7 C:\inetpub\wwwroot\mywiki\includes\page\Article.php(736): Article->showViewFooter()
#8 C:\inetpub\wwwroot\mywiki\includes\actions\ViewAction.php(44): Article->view()
#9 C:\inetpub\wwwroot\mywiki\includes\MediaWiki.php(493): ViewAction->show()
#10 C:\inetpub\wwwroot\mywiki\includes\MediaWiki.php(288): MediaWiki->performAction(Article, Title)
#11 C:\inetpub\wwwroot\mywiki\includes\MediaWiki.php(735): MediaWiki->performRequest()
#12 C:\inetpub\wwwroot\mywiki\includes\MediaWiki.php(509): MediaWiki->main()
#13 C:\inetpub\wwwroot\mywiki\index.php(43): MediaWiki->run()
#14 {main}

In my case I need to edit PageTranslationHooks.php at line 634 to change:

$result[] = 'tpt-patrolling-blocked' to $result = 'tpt-patrolling-blocked'

Source: PHP Manual / StackOverflow

Nikerabbit (talkcontribs)

I believe this is fixed already in a newer version of Translate.