Page MenuHomePhabricator

[Translate] Internal error: MediaWiki namespace cannot be edited with Extension:Translate installed
Closed, InvalidPublic

Description

Using MediaWiki 1.18.3 and Translate 2011-07-09 (the most recent available at mw.org), problem resolves by disabling Extension:Translate in LocalSettings.php:

http://www.coincompendium.com/w/index.php?title=MediaWiki:Sidebar&action=edit

Internal error

TranslationHelpers::getSuggestionBox: Unsupported type ttmserver

Backtrace:

#0 [internal function]: TranslationHelpers->getSuggestionBox()
#1 /path/to/w/extensions/Translate/utils/TranslationHelpers.php(215): call_user_func(Array)
#2 /path/to/w/extensions/Translate/TranslateEditAddons.php(262): TranslationHelpers->getBoxes()
#3 /path/to/w/extensions/Translate/TranslateEditAddons.php(141): TranslateEditAddons::editBoxes(Object(EditPage))
#4 [internal function]: TranslateEditAddons::addTools(Object(EditPage))
#5 /path/to/w/includes/Hooks.php(216): call_user_func_array('TranslateEditAd...', Array)
#6 /path/to/w/includes/GlobalFunctions.php(3660): Hooks::run('EditPage::showE...', Array)
#7 /path/to/w/includes/EditPage.php(1390): wfRunHooks('EditPage::showE...', Array)
#8 /path/to/w/includes/EditPage.php(500): EditPage->showEditForm()
#9 /path/to/w/includes/EditPage.php(353): EditPage->edit()
#10 /path/to/w/includes/Wiki.php(515): EditPage->submit()
#11 /path/to/w/includes/Wiki.php(255): MediaWiki->performAction(Object(Article))
#12 /path/to/w/includes/Wiki.php(640): MediaWiki->performRequest()
#13 /path/to/w/includes/Wiki.php(547): MediaWiki->main()
#14 /path/to/w/index.php(57): MediaWiki->run()
#15 {main}


Version: REL1_18-branch
Severity: critical

Details

Reference
bz37569

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 12:21 AM
bzimport set Reference to bz37569.

You have to get à more recent version of Translate. You can download it from git.

I'm setting the resolution back to invalid. A "FIXED" resolution would imply that a code change was needed to resolve your problem. This issue was marked INVALID, because there was no bug, but "user error", in that an incorrect version of the extension was being used at the time of reporting.