The patch is included starting from Lingo 3.2.4.
Using the configuration option $wgexLingoUseNamespaces[NS_FILE] = false; does not disable Lingo in file descriptions.
The config does work for other namespaces, and adding __NOGLOSSARY__ to the file description successfully disables Lingo. Is there some other setting that I need to use to disable Lingo across all file descriptions?
MW 1.42.1
Lingo 3.2.1 (cc4a274)
Thank you for reporting this issue. My initial testing confirmed the unexpected behavior in the File namespace. However, the extension code handles all namespaces uniformly, so the cause might be external. We'll investigate the issue further and keep you updated.
Thanks for the report. This was fixed in 04070ded4, and included in version 3.2.4.
Prior to this, $wgexLingoUseNamespaces was unreliable (and would most likely only work properly for NS_MAIN), please upgrade if you plan on using this variable.
Proven functionality in the supported environment (Lingo REL1_39 (3.2.0) on MW REL1_39 with a compatible version of PHP).
Extension only guarantees compatibility for LTS MediaWiki versions.
Hello everyone! I've encountered a bug using VisualEditor with Lingo installed. What happened is it wouldn't let me edit using VisualEditor throwing a following exception:
[exception] [f31f5d51fffaa701908e43c3] /mediawiki/api.php?action=visualeditor&format=json&paction=parse&page=%D0%97%D0%B0%D0%B3%D0%BB%D0%B0%D0%B2%D0%BD%D0%B0%D1%8F_%D1%81%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0&uselang=en&editintro=&preload=&preloadparams=&formatversion=2 Error: Typed property Parser::$mOutput must not be accessed before initialization
#0 /var/lib/mediawiki/extensions/Lingo/src/LingoParser.php(393): Parser->getOutput()
#1 /var/lib/mediawiki/extensions/Lingo/src/LingoParser.php(77): Lingo\LingoParser->shouldParse()
#2 /var/lib/mediawiki/extensions/Lingo/src/Lingo.php(72): Lingo\LingoParser->parse()
#3 /var/lib/mediawiki/includes/HookContainer/HookContainer.php(161): Lingo\Lingo::Lingo\{closure}()
#4 /var/lib/mediawiki/includes/HookContainer/HookRunner.php(1179): MediaWiki\HookContainer\HookContainer->run()
#5 /var/lib/mediawiki/includes/content/ContentHandler.php(1774): MediaWiki\HookContainer\HookRunner->onContentAlterParserOutput()
#6 /var/lib/mediawiki/includes/content/Renderer/ContentRenderer.php(47): ContentHandler->getParserOutput()
#7 /var/lib/mediawiki/includes/Revision/RenderedRevision.php(259): MediaWiki\Content\Renderer\ContentRenderer->getParserOutput()
#8 /var/lib/mediawiki/includes/Revision/RenderedRevision.php(232): MediaWiki\Revision\RenderedRevision->getSlotParserOutputUncached()
#9 /var/lib/mediawiki/includes/Revision/RevisionRenderer.php(223): MediaWiki\Revision\RenderedRevision->getSlotParserOutput()
#10 /var/lib/mediawiki/includes/Revision/RevisionRenderer.php(164): MediaWiki\Revision\RevisionRenderer->combineSlotOutput()
#11 [internal function]: MediaWiki\Revision\RevisionRenderer->MediaWiki\Revision\{closure}()
#12 /var/lib/mediawiki/includes/Revision/RenderedRevision.php(199): call_user_func()
#13 /var/lib/mediawiki/includes/poolcounter/PoolWorkArticleView.php(84): MediaWiki\Revision\RenderedRevision->getRevisionParserOutput()
#14 /var/lib/mediawiki/includes/poolcounter/PoolWorkArticleViewCurrent.php(104): PoolWorkArticleView->renderRevision()
#15 /var/lib/mediawiki/includes/poolcounter/PoolCounterWork.php(167): PoolWorkArticleViewCurrent->doWork()
#16 /var/lib/mediawiki/includes/page/ParserOutputAccess.php(304): PoolCounterWork->execute()
#17 /var/lib/mediawiki/includes/parser/Parsoid/ParsoidOutputAccess.php(226): MediaWiki\Page\ParserOutputAccess->getParserOutput()
#18 /var/lib/mediawiki/includes/Rest/Handler/Helper/HtmlOutputRendererHelper.php(764): MediaWiki\Parser\Parsoid\ParsoidOutputAccess->getParserOutput()
#19 /var/lib/mediawiki/includes/Rest/Handler/Helper/HtmlOutputRendererHelper.php(577): MediaWiki\Rest\Handler\Helper\HtmlOutputRendererHelper->getParserOutputInternal()
#20 /var/lib/mediawiki/includes/Rest/Handler/Helper/HtmlOutputRendererHelper.php(438): MediaWiki\Rest\Handler\Helper\HtmlOutputRendererHelper->getParserOutput()
#21 /var/lib/mediawiki/extensions/VisualEditor/includes/DirectParsoidClient.php(157): MediaWiki\Rest\Handler\Helper\HtmlOutputRendererHelper->getHtml()
#22 /var/lib/mediawiki/extensions/VisualEditor/includes/ApiParsoidTrait.php(110): MediaWiki\Extension\VisualEditor\DirectParsoidClient->getPageHtml()
#23 /var/lib/mediawiki/extensions/VisualEditor/includes/ApiVisualEditor.php(231): MediaWiki\Extension\VisualEditor\ApiVisualEditor->requestRestbasePageHtml()
#24 /var/lib/mediawiki/includes/api/ApiMain.php(1935): MediaWiki\Extension\VisualEditor\ApiVisualEditor->execute()
#25 /var/lib/mediawiki/includes/api/ApiMain.php(912): ApiMain->executeAction()
#26 /var/lib/mediawiki/includes/api/ApiMain.php(883): ApiMain->executeActionWithErrorHandling()
#27 /var/lib/mediawiki/api.php(95): ApiMain->execute()
#28 /var/lib/mediawiki/api.php(48): wfApiMain()
#29 {main}
I'm running MediaWiki 1.41.1 and Lingo 3.1.1. As a temporal dirty workaround I added some lines in Lingo/src/LingoParser.php that check whether Parser::$mOutput was initialized and it seems to be working:
/**
* @param Parser $parser
* @return bool
*/
private function shouldParse( $parser ) {
global $wgexLingoUseNamespaces;
if ( !( $parser instanceof Parser || $parser instanceof StubObject ) ) {
return false;
}
$reflectionClass = new \ReflectionClass(Parser::class);
if ( !$reflectionClass->getProperty( 'mOutput' )->isInitialized( $parser ) ) {
return false;
}
Is there any solution to this? Thanks in advance!
Can confirm that this fix works for my instance (Topic:Y539l5u5ccztb2oe) also.
SG
Correction - this does not actually fix the issue. It DOES allow VisualEditor to open and work but the the site becomes unstable.
Further investigation revealed that (without the changes) VisualEditor opens up when you are CREATING a new page but pops an error when attempting to edit an existing page.
As a work-around, I simply open a new page and create my changes if needed then switch to Edit Source and copy pasta!
I am unsure why do you use Lingo 3.1.1 (this tag was released in 2019).
If you use composer as required https://github.com/wikimedia/mediawiki-extensions-Lingo, it should end up with installing Lingo 3.2.
If you can't use composer for some reason, we suggest installing branch REL1_39 via git. It is targeted at work with MW 1.39 but can work with 1.41, please test.
I updated the direct download link on the extension page so that now it points to the version 3.2.0.
I confirm the described behavior in my test environment:
Perhaps it is due to the recent changes in the MediaWiki core.
In the recommended environment:
everything works correctly.
This has not been fixed in MW 1.41 and Lingo 3.2.1. This is still an open issue for REL1_41, which I am able to unfortunately replicate.
Thank you for testing. I confirmed the failure for MW 1.41 in the above comment.
As long as the extension compatibility policy is LTS (key: ltsrel), we expect it to work with MW 1.39 and 1.43. Tasks can be added to Phabricator issue tracker about the issues in the non-LTS versions.
Actually, the task is there already and I see you in the thread, @Joe Beaudoin Jr. Redux
User confirmed that the fix now works.
Turning on error reporting show the below.
| Product | Version |
|---|---|
| MediaWiki | 1.39.0 |
| PHP | 8.1.13 (apache2handler) |
| Lingo | 3.1.1 |
PHP Caching
| APCu Support | Enabled |
| Version | 5.1.21 |
| APCu Debugging | Disabled |
| MMAP Support | Enabled |
| MMAP File Mask | no value |
| Serialization Support | php |
| Build Date | Jun 25 2022 07:29:23 |
MediaViewer also has issues and has been disabled so direct viewing of images is fine. But with Lingo I get this:
[d2bd7de25bc67f629e3a1d49] /mediawiki/index.php?title=Glossary&action=submit Error: Call to undefined function Lingo\wfGetMainCache()
Backtrace:
from /var/www/html/mediawiki/extensions/Lingo/src/LingoParser.php(387)
#0 /var/www/html/mediawiki/extensions/Lingo/src/BasicBackend.php(262): Lingo\LingoParser->purgeGlossaryFromCache()
#1 /var/www/html/mediawiki/includes/HookContainer/HookContainer.php(338): Lingo\BasicBackend->purgeCache()
#2 /var/www/html/mediawiki/includes/HookContainer/HookContainer.php(137): MediaWiki\HookContainer\HookContainer->callLegacyHook()
#3 /var/www/html/mediawiki/includes/HookContainer/HookRunner.php(2732): MediaWiki\HookContainer\HookContainer->run()
#4 /var/www/html/mediawiki/includes/Storage/PageUpdater.php(913): MediaWiki\HookContainer\HookRunner->onPageContentSave()
#5 /var/www/html/mediawiki/includes/EditPage.php(2596): MediaWiki\Storage\PageUpdater->saveRevision()
#6 /var/www/html/mediawiki/includes/EditPage.php(1904): EditPage->internalAttemptSave()
#7 /var/www/html/mediawiki/includes/EditPage.php(721): EditPage->attemptSave()
#8 /var/www/html/mediawiki/includes/actions/EditAction.php(73): EditPage->edit()
#9 /var/www/html/mediawiki/includes/actions/SubmitAction.php(38): EditAction->show()
#10 /var/www/html/mediawiki/includes/MediaWiki.php(542): SubmitAction->show()
#11 /var/www/html/mediawiki/includes/MediaWiki.php(322): MediaWiki->performAction()
#12 /var/www/html/mediawiki/includes/MediaWiki.php(904): MediaWiki->performRequest()
#13 /var/www/html/mediawiki/includes/MediaWiki.php(562): MediaWiki->main()
#14 /var/www/html/mediawiki/index.php(50): MediaWiki->run()
#15 /var/www/html/mediawiki/index.php(46): wfIndexMain()
#16 {main}
¯\_(ツ)_/¯
Everything else seems good.
This is a fresh build with the aforementioned versions.
Any ideas?
SG
Thank you for your report, we're working on 1.39 compatibility and the issue should have an update soon.
The lastest patch has been merged, can you test it with the patch merged (master) and let me know if you still face this issue?
Proven functionality in the supported environment (Lingo REL1_39 (3.2.0) on MW REL1_39 with a compatible version of PHP).
I have a definition for AB and a definition for AB-CD but AB-CD only shows the definition for AB. How can I fix this??
SG
_Lingo_talk.png)
Can't confirm. Lingo 3.2.0 installed as explained in the Composer section of the extension page, produces tooltips correctly with the default settings.
Please note that the next official release of Lingo will be for the next MediaWiki LTS version in accordance with Lingo compatibility policy (LTSrel).
Due to the latest changes in the core, I changed the requirements on the extension page.
Proven functionality in the supported environment (Lingo REL1_39 (3.2.0) on MW REL1_39 with a compatible version of PHP).
I have been searching and cannot figure this one out. Lingo is operational but when I run update.php I get this:
PHP Deprecated: Use of Hooks::register was deprecated in MediaWiki 1.35. [Called from Lingo\BasicBackend::registerHooks in /var/www/mediawiki/extensions/Lingo/src/BasicBackend.php at line 58] in /var/www/mediawiki/includes/debug/MWDebug.php on line 386
Any idea?
SG
It is just a PHP warning that gets thrown if your current version of MediaWiki is v1.35 or over but your version of Lingo lingers behind. Your best bet is to upgrade Lingo.
To judge by https://github.com/wikimedia/mediawiki-extensions-Lingo/blob/master/src/BasicBackend.php, the extension uses hooks correctly. The change hasn't been backported to the 1.36-1.38 branches though, maybe because it is only a deprecation warning, not an error. Or maybe it was just an oversight.
It is fixed in REL1_39 (LTS) according to the extension compatibility policy (ltsrel): https://github.com/wikimedia/mediawiki-extensions-Lingo/blob/c88549b25caa48012b915c150115c7100ded82be/src/BasicBackend.php#L56C1-L60C3
If you are on MW 1.39, please checkout REL1_39 branch, rather than a tag.
If you are running MW < 1.39, just ignore the message, as mentioned by @Cavila, it is just a deprecation warning and will go away with the upgrade to 1.39.
As for MW 1.35, it went end-of-life on December 21, 2023.
It actually only pops this error when I use VisualEditor. I disable Lingo when I need to use that extension and then have no issues.
@GobleStL Please, make sure that you have PHP error reporting off in your LocalSettings.php and repeat testing. In case of failure, please share your current MW version number + PHP version, so that we could try to reproduce the error. A link to your LocalSettings.php will also be very helpful (just wipe the sensitive info out).
With error reporting on: "[58a6c0d657e09eaaaf0dc77c] Exception caught: Typed property Parser::$mOutput must not be accessed before initialization"
With error reporting off: "[addf778021d79e091496ce38] Caught exception of type Error"
This only pops up when I attempt to use VisualEditor. Lingo works just fine.
If I disable Lingo extension, VisualEditor opens without an error. I believe it is related to https://phabricator.wikimedia.org/T357686
In troubleshooting this I upgraded everything. I even started using dev branches. (The error started when on stable branch). Currently I am:
| Product | Version |
|---|---|
| MediaWiki | 1.41.1 |
| PHP | 8.3.7 (fpm-fcgi) |
| ICU | 66.1 |
| MariaDB | 10.5.23-MariaDB-0+deb11u1 |
| Lua | 5.1.5 |
| Pygments | 2.16.1 |
| VisualEditor | 0.1.2 (6f30783) 16:34, 10 May 2024 |
| Lingo | 3.2.1 |
<?php
#To suppress error messages uncomment the next two lines
error_reporting( 0 );
ini_set( 'display_errors', 0);
#To turn on error reporting uncomment the next four lines
#error_reporting( -1 );
#ini_set( 'display_errors', 1 );
#$wgShowExceptionDetails = true;
#$wgShowDBErrorBacktrace = true;
# This file was automatically generated by the MediaWiki 1.41.1
# installer. If you make manual changes, please keep track in case you
# need to recreate them later.
#
# See includes/MainConfigSchema.php for all configurable settings
# and their default values, but don't forget to make changes in _this_
# file, not there.
#
# Further documentation for configuration settings may be found at:
# https://www.mediawiki.org/wiki/Manual:Configuration_settings
# Protect against web entry
if ( !defined( 'MEDIAWIKI' ) ) {
exit;
}
## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;
$wgSitename = "This_Wiki";
## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs
## (like /w/index.php/Page_title to /wiki/Page_title) please see:
## https://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath = "/mediawiki";
## The protocol and server name to use in fully-qualified URLs
$wgServer = "https://wiki.com";
## The URL path to static resources (images, scripts, etc.)
$wgResourceBasePath = $wgScriptPath;
## The URL paths to the logo. Make sure you change this from the default,
## or else you'll overwrite your logo when you upgrade!
$wgLogos = [
'1x' => "$wgResourceBasePath/resources/assets/wiki.svg",
'icon' => "$wgResourceBasePath/resources/assets/wiki.svg",
];
$wgFavicon = "$wgResourceBasePath/resources/assets/wiki_icon.svg";
## UPO means: this is also a user preference option
$wgEnableEmail = true;
$wgEnableUserEmail = true; # UPO
$wgEmergencyContact = "an.email@abc.com";
$wgPasswordSender = "an.email@abc.com";
$wgSMTP = [
'host' => 'ssl://smtp.email.com', // could also be an IP address. Where the SMTP server is located. If using SSL or TLS, add the prefix "ssl://" or "tls://".
'IDHost' => 'wiki.com', // Generally this will be the domain name of your website (aka mywiki.org)
'localhost' => 'wiki.com,
'port' => 465, // Port to use when connecting to the SMTP server
'auth' => true, // Should we use SMTP authentication (true or false)
'username' => 'an.email@abc.com', // Username to use for SMTP authentication (if being used)
'password' => 'somethinghere' // Password to use for SMTP authentication (if being used)
];
$wgEnotifUserTalk = true; # UPO
$wgEnotifWatchlist = true; # UPO
$wgEmailAuthentication = true;
## Database settings
$wgDBtype = "mysql";
$wgDBserver = "localhost";
$wgDBname = "this_wiki";
$wgDBuser = "wiki_dude";
$wgDBpassword = "apassword";
# MySQL specific settings
$wgDBprefix = "";
$wgDBssl = false;
# MySQL table options to use during installation or update
$wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary";
# Shared database table
# This has no effect unless $wgSharedDB is also set.
$wgSharedTables[] = "actor";
## Shared memory settings
$wgMainCacheType = CACHE_ACCEL;
$wgMemCachedServers = [];
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";
$wgGenerateThumbnailOnParse = true;
$wgSVGConverter = 'ImageMagick';
# InstantCommons allows wiki to use images from https://commons.wikimedia.org
$wgUseInstantCommons = false;
# Periodically send a pingback to https://www.mediawiki.org/ with basic data
# about this MediaWiki instance. The Wikimedia Foundation shares this data
# with MediaWiki developers to help guide future development efforts.
$wgPingback = false;
# Site language code, should be one of the list in ./includes/languages/data/Names.php
$wgLanguageCode = "en";
# Time zone
#$wgLocaltimezone = "UTC";
$wgLocaltimezone = "America/Chicago";
## Set $wgCacheDirectory to a writable directory on the web server
## to make your wiki go slightly faster. The directory should not
## be publicly accessible from the web.
#$wgCacheDirectory = "$IP/cache";
$wgTmpDirectory = "/var/www/mediawiki/temp";
$wgSecretKey = "abc123";
# Changing this will log out all existing sessions.
$wgAuthenticationTokenVersion = "1";
# Site upgrade key. Must be set to a string (default provided) to turn on the
# web installer while LocalSettings.php is in place
$wgUpgradeKey = "1234567890";
## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsUrl = "";
$wgRightsText = "";
$wgRightsIcon = "";
# Path to the GNU diff3 utility. Used for conflict resolution.
$wgDiff3 = "/usr/bin/diff3";
# The following permissions were set based on your choice in the installer
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['read'] = false;
## Default skin: you can change the default skin. Use the internal symbolic
## names, e.g. 'vector' or 'monobook':
$wgDefaultSkin = "monobook";
# Enabled skins.
# The following skins were automatically enabled:
wfLoadSkin( 'MinervaNeue' );
wfLoadSkin( 'MonoBook' );
wfLoadSkin( 'Timeless' );
wfLoadSkin( 'Vector' );
# Enabled extensions. Most of the extensions are enabled by adding
# wfLoadExtension( 'ExtensionName' );
# to LocalSettings.php. Check specific extension documentation for more details.
# The following extensions were automatically enabled:
wfLoadExtension( 'AccessControl' );
wfLoadExtension( 'AutoCreateCategoryPages' );
wfLoadExtension( 'CategoryTree' );
wfLoadExtension( 'Cite' );
wfLoadExtension( 'CiteThisPage' );
wfLoadExtension( 'CodeEditor' );
wfLoadExtension( 'ConfirmEdit' );
wfLoadExtension( 'DataDump' );
wfLoadExtension( 'DiscussionTools' );
wfLoadExtension( 'DumpsOnDemand' );
wfLoadExtension( 'Echo' );
wfLoadExtension( 'Gadgets' );
wfLoadExtension( 'ImageMap' );
wfLoadExtension( 'InputBox' );
wfLoadExtension( 'Interwiki' );
#wfLoadExtension( 'LinkTitles' );
wfLoadExtension( 'Linter' );
wfLoadExtension( 'LoginNotify' );
wfLoadExtension( 'Maintenance' );
wfLoadExtension( 'Math' );
wfLoadExtension( 'MultimediaViewer' );
wfLoadExtension( 'Nuke' );
wfLoadExtension( 'OATHAuth' );
wfLoadExtension( 'PageForms' );
wfLoadExtension( 'PageImages' );
wfLoadExtension( 'ParserFunctions' );
wfLoadExtension( 'PdfHandler' );
wfLoadExtension( 'Poem' );
wfLoadExtension( 'Renameuser' );
wfLoadExtension( 'ReplaceText' );
wfLoadExtension( 'Scribunto' );
wfLoadExtension( 'SecureLinkFixer' );
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
wfLoadExtension( 'TemplateData' );
wfLoadExtension( 'TextExtracts' );
wfLoadExtension( 'Thanks' );
wfLoadExtension( 'TitleBlacklist' );
wfLoadExtension( 'VisualEditor' );
wfLoadExtension( 'WikiEditor' );
# End of automatically generated settings.
# Add more configuration options below.
//DataDump Configuration
$wgDataDumpDirectory = "<path>${wgDBname}/";
$wgDataDump = [
'xml' => [
'file_ending' => '.xml.gz',
'generate' => [
'type' => 'mwscript',
'script' => "$IP/maintenance/dumpBackup.php",
'options' => [
'--full',
'--output',
"gzip:${wgDataDumpDirectory}" . '${filename}',
],
],
'limit' => 1,
'permissions' => [
'view' => 'view-dump',
'generate' => 'generate-dump',
'delete' => 'delete-dump',
],
],
'image' => [
'file_ending' => '.zip',
'generate' => [
'type' => 'script',
'script' => '/usr/bin/zip',
'options' => [
'-r',
'<path>${filename}',
"<path>${wgDBname}/"
],
],
'limit' => 1,
'permissions' => [
'view' => 'view-dump',
'generate' => 'view-image-dump',
'delete' => 'delete-dump',
],
],
];
// create DataDump right
$wgAvailableRights[] = 'view-dump';
$wgAvailableRights[] = 'view-image-dump';
$wgAvailableRights[] = 'generate-dump';
$wgAvailableRights[] = 'delete-dump';
// add DataDump to the user group
$wgGroupPermissions['user']['view-image-dump'] = true;
$wgGroupPermissions['sysop']['view-image-dump'] = true;
$wgGroupPermissions['user']['generate-dump'] = true;
$wgGroupPermissions['sysop']['generate-dump'] = true;
$wgGroupPermissions['sysop']['delete-dump'] = true;
// add DataDump to the 'basic' grant so we can use our DataDump over an API request
$wgGrantPermissions['basic']['view-image-dump'] = true;
$wgGrantPermissions['basic']['generate-dump'] = true;
$wgGrantPermissions['basic']['delete-dump'] = true;
//For mobile adding extension and settings
$wgUrlProtocols[] = "file://";
$wgFileExtensions[] = 'iso';
$wgFileExtensions[] = 'pdf';
$wgFileExtensions[] = 'doc';
$wgFileExtensions[] = 'xls';
$wgMaxShellMemory = 8000000;
$wgMaxShellFileSize = 1000000;
$wgMaxShellTime = 300;
$wgAllowTitlesInSVG = true;
$wgLinkTitlesParseOnEdit = true;
$wgLinkTitlesBlackList[] = 'B6200';
// Add Lingo
wfLoadExtension( 'Lingo' );
#The following hook is needed for Lingo to function
$wgHooks['SetupAfterCache'][] = function() {
// specify a different name for the terminology page (Default: 'Terminology' (or localised ve>
$GLOBALS['wgexLingoPage'] = 'Glossary';
// specify that each term should be annotated only once per page (Default: false)
//$GLOBALS['wgexLingoDisplayOnce'] = false;
// specify what namespaces should or should not be used (Default: Empty, i.e. use all namespa>
//$GLOBALS['wgexLingoUseNamespaces'][NS_SPECIAL] = false;
// set default cache type (Default: null, i.e. use main cache)
//$GLOBALS['wgexLingoCacheType'] = CACHE_NONE;
// use ApprovedRevs extension on the Terminology page (Default: false)
//$GLOBALS['wgexLingoEnableApprovedRevs'] = true;
};
We only support LTS branches of MediaWiki. You can try the REL1_39 branch's code and it might work with 1.41. Probably unrelated, running MediaWiki with version 8.3 might cause issues.
Thank you. I realize this. This is why I just disable the extension when I want to use VisualEditor.
Lingo REL1_39 is free of this bug. The issue was SemanticGlossary pulling an outdated Lingo version.
MW 1.39, php 8.1, Lingo extension REL1_39 and I'm getting:
Warning: Undefined global variable $wgParser in/var/www/html/extensions/Lingo/src/Lingo.php on line53
Hi @Allanext2, please let me know what installation method did you use (cloning Git repo, composer or something else)?
Hi @Elcapitan68,
I have it installed with a git submodule from the github repo, below the entry in .gitmodules:
[submodule "data/extensions/Lingo"]
path = data/extensions/Lingo
url = https://github.com/wikimedia/mediawiki-extensions-Lingo.git
branch = REL1_39
I then do:
git submodule init
git submodule update
git submodule foreach -q 'branch="$(git config -f $toplevel/.gitmodules submodule.$name.branch)"; echo "Extension $name:"; git switch $branch'
Thank you !
Please check paths, REL1_39 of Lingo seems to be free of wgParser:
w/extensions/Lingo$ php -v
PHP 8.1.27 (cli) (built: Dec 21 2023 20:19:54) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.27, Copyright (c) Zend Technologies
with Zend OPcache v8.1.27, Copyright (c), by Zend Technologies
w/extensions/Lingo$ git status
On branch REL1_39
Your branch is up to date with 'origin/REL1_39'.
nothing to commit, working tree clean
w/extensions/Lingo$ grep -R wgParser ./
w/extensions/Lingo$
See here.
Is there a chance that you mount an outdated branch some way?
What happens if you checkout the tag?
cd extensions/Lingo git checkout 3.2.0
@Elcapitan68 You're right the REL1_39 branch in clean of wgParser.
The issue is that when Semantic Glossary is installed (dev-master branch) with `composer update --no-dev` it requires the dependency Lingo 3.1.1 which overrides files
@Allanext2 Got it. As Lingo REL1_39 is just fine, and provided that there is the PR waiting for a merge, I suggest closing this.
In the meantime, feel free to try the fork from WikiTeq https://github.com/WikiTeq/SemanticGlossary that includes the patch.
@Elcapitan68 yes, makes sense, thank you !!
Sorry for the late reply! Indeed, setting $wgexLingoPage = 'Project:Terminology'; does the trick :)
I'm trying to use Project:Terminology as the terminology page for the extension across an entire wiki, but the extension doesn't seem to recognize that page when I set it in MediaWiki:Lingo-terminologypagename, using either "Project:Terminology" or "Wiki Name:Terminology".
Thank you for asking, @SlyCooperFan1
You are supposed to use a configuration variable in order to change the default page. Please try to add to your LocalSettings.php:
$wgexLingoPage = 'Project:Terminology';
The page you mention (MediaWiki:Lingo-terminologypagename) is used to create localized names for the Lingo page, eg. MediaWiki:Lingo-terminologypagename/fr, see: https://github.com/wikimedia/mediawiki-extensions-Lingo/blob/362618929b946588935d2bd15a94d9d966079481/src/BasicBackend.php#L175
@SlyCooperFan1, did you have a chance to try setting $wgexLingoPage? Did it help?
The bug report is created on Phabricator https://phabricator.wikimedia.org/T348465. In the meanwhile, a CSS workaround is suggested.
I am using the vector 2022 skin and recently installed the Lingo extension, love it but I have this very strange problem, when I have Lingo enabled, I found that the TOC is displayed at the beginning of only some pages.. if I switch to the old vector (2010) skin, the TOC displays at the beginning of all pages (which is expected). Has anyone seen this issue or any idea where could be the problem? Below are the versions:
| Product | Version |
|---|---|
| MediaWiki | 1.39.2 |
| PHP | 8.1.13 (fpm-fcgi) |
| MariaDB | 10.6.11-MariaDB |
| ICU | 67.1 |
| Lua | 5.1.5 |
| Pygments | 2.11.2 |
Hi, @Paulxu20 Please, provide a link to a live page with the described TOC behavior or to a screenshot. Also, make sure your expectations about all pages are correct: by design, a table of contents is automatically generated on a page when more than three section headings are used (Manual:Table of contents)
Hi @Elcapitan68, thanks for the reply! Here is an example: https://papals.org/index.php?title=Test3, you can see on this page the TOC is appearing both at beginning of the page, as well as on the sidebar. And you are right, but I am under the impression that if the skin is vector 2010, the toc only appears at the beginning of the page, but if the skin is vector 2020, the toc only appears on the sidebar, no?
What is happening now is that the toc appears on both the beginning of the page and the sidebar when the skin is vector 2020, I am actually OK with this, but the problem is that it is not consistent, on some page it appears on both places, on some page it only appears on sidebar.
Pretty sure it has something to do with Lingo, because if you look at this test page https://papals.org/index.php?title=Test4, notice that it does not have the word "GU" (which is in the glossary list) on the page, and the toc only appears in sidebar. But on https://papals.org/index.php?title=Test3, it does have "GU" at beginning of the page, which triggered Lingo to render the tooltip, and the toc appears on both places.
@Paulxu20, we should probably call it "vector-2022"? Indeed, it looks strange. The page Reading/Web/Desktop Improvements/Features/Table of contents describes the concept of the new TOC, saying that "We intentionally do not add the old table of contents to the article in addition to the new sidebar location". Please, let me know if you use caching (varnish / redis / cloudflare / file cache / etc.).
Hi @Elcapitan68, for caching APCu is used. In the LocalSettings.php it is set like this: $wgMainCacheType = CACHE_ACCEL;
I am not sure if this is the best caching option performance wise, but it has been working ok to me.
@Paulxu20 I see. It looks like a side effect of the way src/LingoParser.php works. It re-renders the page injecting its elements and is not aware about the latest Vector specifics. I will create a ticket for investigating and fixing this.
In the meanwhile I suggest hiding the in-page TOC with CSS on MediaWiki:Vector-2022.css, like this:
#mw-content-text #toc {
display: none;
}
Possibly a caching issue
Whenever i tried to add new terms or making changes in existing lingo terms, those changes are not reflecting on my media wiki pages but i could see the terms i added is reflecting on my terminology page. Can anyone help on this issue ?
@Boopalag, can you share screen shorts of expected and actual behavior and the version of Lingo you're running including the version of MediaWiki?
Hi X-Savitar, Thanks a lot for response, Now the issue is little different.
Actually we are able to see the tooltip but there is a delay for the tooltip to be visible after a new Glossary term is added (approx 4-7 days delay). Sometimes its reflecting within a day and sometimes after a week (there is no uniform pattern).
Any suggestions to make the tooltip visible immediately after a new term is added?
Mediawiki - 1.35.3 with the Lingo version - 3.1.1 (8ae42ff)
We're guessing that this was caused by the old tooltip being stuck in your parser cache. To avoid this, check Manual:$wgInvalidateCacheOnLocalSettingsChange and Manual:$wgCacheEpoch then touch (save) your LocalSettings.php file. Please let us know if that solves your issue.
Fix was merged
Just wanted to point out that there is an open change regarding an issue with Parser::getOutput being null.
See https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Lingo/+/745880
There is a discussion. It would be great if a maintainer could join in.