Extension talk:Lingo

About this board

Addtion of new terms or making changes in existing is not reflecting

3
Boopalag (talkcontribs)

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 ?

X-Savitar (talkcontribs)

@Boopalag, can you share screen shorts of expected and actual behavior and the version of Lingo you're running including the version of MediaWiki?

Boopalag (talkcontribs)

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)

Reply to "Addtion of new terms or making changes in existing is not reflecting"

Bug: The extension don't "see" all the terms

10
Summary by Seb35

By default, the terminology page is "Terminology" for an English-language wiki, "Terminología" for a Spanish-language wiki. To change this default page, the parameter $wgexLingoPage must be defined in LocalSettings.php and set to the desired page.

ChofisDan (talkcontribs)

I instaled Lingo and added two terms the first time to my Terminology page, and all went fine. But when i tried to add more terms, they don't work, it seems as if the extension just doesn't see them. I tried deleting the content of the page and even removing and reinstalling the extension and nothing happens. What can I do?

Seb35 (talkcontribs)

Perhaps there is a syntax mistake on the Terminology page? Could you verify? and if you don’t find any error, copy here a minimal Terminology page with the issue and/or give a link if it is a public wiki.

Seb35 (talkcontribs)

Also, I see Lingo does not support difference of case (see phabricator:T123961), so for instance if you enter the definition

Bug
A default in a software

The word « bug » will not be highlighted by Lingo since the definition has a capital "B".

ChofisDan (talkcontribs)

The terms I entered are always written in lowercase in the articles, that is, exactly as they are in the Terminology page. I followed the syntax as it was on the extension's page here on the MediaWiki. Here's my terminology page.

Seb35 (talkcontribs)

I was not able to reproduce the issue on a test wiki (MW 1.37.1 + your Lingo version 74e31cc indicated in Special:Version), but given you customized the Lingo terminology page, did you change accordingly the parameter $wgexLingoPage to MediaWiki:Lingo-Terminología (NB the "ex" after "wg", it’s unusual for a MW setting) in LocalSettings.php?

ChofisDan (talkcontribs)
Seb35 (talkcontribs)

This is perhaps the issue: by default the page for terminology is Terminología; if you want to use MediaWiki:Lingo-Terminología instead, it is possible but you have to set $wgexLingoPage = "MediaWiki:Lingo-Terminología"; in the file LocalSettings.php.

ChofisDan (talkcontribs)

You're right!! I moved the content of MediaWiki:Lingo-Terminología to Terminología, and tho it's kind of annoying having that page in the main namespace, it worked! Thank you so much!

Seb35 (talkcontribs)

I’m glad it works. I close the topic.

GobleStL (talkcontribs)

This same issue has happened to me.

I am running a local private mediawiki and SOME terms are not "working". i.e. no tool tip is displayed.

Product Version
MediaWiki 1.37.0
PHP 8.1.2 (apache2handler)
MariaDB 10.4.22-MariaDB
ICU 70.1
Lingo 3.1.2

Tried with Terminology page and specifying a "Glossary" page in settings.

Any ideas?

SG

Reply to "Bug: The extension don't "see" all the terms"

HALP! Fatal exception of type "Error"

2
GobleStL (talkcontribs)

Was a big fan of "Terminology" and cannot for the life of me get this new one working with my old page. Created a new page called "Glossary" and specifying it in the settings but no matter what I get the aforementioned error.

GobleStL (talkcontribs)

Error: Class 'Revision' not found

3
Summary by Seb35

A recent version of Lingo must be installed, at least the one for the branch REL1_37 (MediaWiki 1.37), available in Special:ExtensionDistributor/Lingo (link 'Download extension' in extension page). Currently the version 3.1.1 is not recent enough for MediaWiki 1.37.

63.155.89.242 (talkcontribs)

When I install Lingo (both manually and via composer), all of my pages experience a Fatal Exception.


/index.php?title=Main_Page Error: Class 'Revision' not found

Backtrace:

from /mediawiki-1.37.1/extensions/Lingo/src/BasicBackend.php(304)

#0 /mediawiki-1.37.1/extensions/Lingo/src/BasicBackend.php(250): Lingo\BasicBackend->getLatestRevisionFromTitle(Title)

#1 /mediawiki-1.37.1/extensions/Lingo/src/BasicBackend.php(202): Lingo\BasicBackend->getRevisionFromTitle(Title)

#2 /mediawiki-1.37.1/extensions/Lingo/src/BasicBackend.php(164): Lingo\BasicBackend->getRawDictionaryContent(Title)

#3 /mediawiki-1.37.1/extensions/Lingo/src/BasicBackend.php(78): Lingo\BasicBackend->collectDictionaryLines()

#4 /mediawiki-1.37.1/extensions/Lingo/src/LingoParser.php(186): Lingo\BasicBackend->next()

#5 /mediawiki-1.37.1/extensions/Lingo/src/LingoParser.php(159): Lingo\LingoParser->buildLingo()

#6 /mediawiki-1.37.1/extensions/Lingo/src/LingoParser.php(217): Lingo\LingoParser->getLingoTree()

#7 /mediawiki-1.37.1/extensions/Lingo/src/LingoParser.php(83): Lingo\LingoParser->realParse(DeprecatedGlobal)

#8 /mediawiki-1.37.1/extensions/Lingo/src/Lingo.php(53): Lingo\LingoParser->parse(DeprecatedGlobal)

#9 /mediawiki-1.37.1/includes/HookContainer/HookContainer.php(338): Lingo\Lingo::Lingo\{closure}(WikitextContent, Title, ParserOutput)

#10 /mediawiki-1.37.1/includes/HookContainer/HookContainer.php(137): MediaWiki\HookContainer\HookContainer->callLegacyHook(string, array, array, array)

#11 /mediawiki-1.37.1/includes/HookContainer/HookRunner.php(1212): MediaWiki\HookContainer\HookContainer->run(string, array)

#12 /mediawiki-1.37.1/includes/content/AbstractContent.php(552): MediaWiki\HookContainer\HookRunner->onContentAlterParserOutput(WikitextContent, Title, ParserOutput)

#13 /mediawiki-1.37.1/includes/Revision/RenderedRevision.php(263): AbstractContent->getParserOutput(Title, integer, ParserOptions, boolean)

#14 /mediawiki-1.37.1/includes/Revision/RenderedRevision.php(235): MediaWiki\Revision\RenderedRevision->getSlotParserOutputUncached(WikitextContent, boolean)

#15 /mediawiki-1.37.1/includes/Revision/RevisionRenderer.php(217): MediaWiki\Revision\RenderedRevision->getSlotParserOutput(string, array)

#16 /mediawiki-1.37.1/includes/Revision/RevisionRenderer.php(154): MediaWiki\Revision\RevisionRenderer->combineSlotOutput(MediaWiki\Revision\RenderedRevision, array)

#17 [internal function]: MediaWiki\Revision\RevisionRenderer->MediaWiki\Revision\{closure}(MediaWiki\Revision\RenderedRevision, array)

#18 /mediawiki-1.37.1/includes/Revision/RenderedRevision.php(197): call_user_func(Closure, MediaWiki\Revision\RenderedRevision, array)

#19 /mediawiki-1.37.1/includes/poolcounter/PoolWorkArticleView.php(137): MediaWiki\Revision\RenderedRevision->getRevisionParserOutput()

#20 /mediawiki-1.37.1/includes/poolcounter/PoolCounterWork.php(162): PoolWorkArticleView->doWork()

#21 /mediawiki-1.37.1/includes/page/ParserOutputAccess.php(281): PoolCounterWork->execute()

#22 /mediawiki-1.37.1/includes/page/Article.php(691): MediaWiki\Page\ParserOutputAccess->getParserOutput(WikiPage, ParserOptions, MediaWiki\Revision\RevisionStoreRecord, integer)

#23 /mediawiki-1.37.1/includes/page/Article.php(506): Article->generateContentOutput(User, ParserOptions, integer, OutputPage, array)

#24 /mediawiki-1.37.1/includes/actions/ViewAction.php(80): Article->view()

#25 /mediawiki-1.37.1/includes/MediaWiki.php(543): ViewAction->show()

#26 /mediawiki-1.37.1/includes/MediaWiki.php(320): MediaWiki->performAction(Article, Title)

#27 /mediawiki-1.37.1/includes/MediaWiki.php(930): MediaWiki->performRequest()

#28 /mediawiki-1.37.1/includes/MediaWiki.php(564): MediaWiki->main()

#29 /mediawiki-1.37.1/index.php(53): MediaWiki->run()

#30 /mediawiki-1.37.1/index.php(46): wfIndexMain()

#31 {main}

Izno (talkcontribs)
Seb35 (talkcontribs)
TimoKausK (talkcontribs)

I installed MW 1.35.1 and Lingo is active.

In the Special:Version page no Terminology Page - Link was shown. So I created the Terminology Page with some definitions in the main Space.

But. Nothing happens. I googled that behavior and found nothing that matches my problem.


Can anyone help me out?

F.trott (talkcontribs)

It seems that the link disappeared from the Description column together with the rest of the extension description in one of the last MW versions.

On a non-english wiki the page will be called differently. You can go to the page MediaWiki:Lingo-terminologypagename on your wiki to find the actual name.


Edit: Last version showing the description correctly was apparently 1.34, so something must have changed in 1.35

TimoKausK (talkcontribs)

This is it!

So so many thanks from Germany where Terminology - Page is named 'Glossar' !

63.224.99.246 (talkcontribs)

Mediawiki 1.36.2

php 7.4.3

Lingo 3.1.1

Fatal exception of type "ArgumentCountError"

I get this error on any actual page, not on Special pages.

I have a page named Terminology created before enabling the extension.

When I disable Lingo in the LocalSetttings, everything works fine.

178.251.90.66 (talkcontribs)

I confirm the "ArgumentCountError" problem. Same software versions.

Reply to "Can not make it run"

Definition popup box display problem

2
Issiegainsley (talkcontribs)

My hoover over DOES work but it is displaying at the full length of the main window and at the very bottom of the browser. (chrome).

ProductVersionMediaWiki1.32.3 (aadd77b)PHP7.3.10 (cgi-fcgi)MySQL8.0.17


Have you seen this before? If not I can include more information.

Seb35 (talkcontribs)

This was reported as a bug on Phabricator. There is a fix proposed on Phabricator and I submitted a perennial fix yesterday, so it will be fixed in a future version.

Reply to "Definition popup box display problem"

Feature request: Exclude headings from lookup

2
Amousey (talkcontribs)

Feature request - any common terms including acronyms that are used in part of a heading, especially a subheading, cause a messy and unhelpful layout - these are especially common as the last or first word in a heading. Excluding these, or excluding certain tags from lookup would be helpful.

Eg h1 - h5

Amousey (talkcontribs)
Reply to "Feature request: Exclude headings from lookup"

Feature request: Ability to exclude a term from lookup, depending on surrounding words

2
Amousey (talkcontribs)

If you have "Enterprise" in the glossary, but some pages contain the phrase "The Starship Enterprise" then it would be helpful to not have the glossary term highlighted in that phrase. Other examples would be words with meanings that depend on context, eg lookup American (definition: USA) but not North American (which includes Canada).

Secondly, have some definitions appear in the glossary but that don't automatically get looked up (no dotted border) / which would make the glossary very helpful for browsing.

This comes up a great deal on medical terms, where syndrome, disease, illness and disorder are all helpful to have in the glossary for those browsing it - but almost every diagnosis seems to include one of those words as part of the name. So they would be looked up on most pages.

Amousey (talkcontribs)
Reply to "Feature request: Ability to exclude a term from lookup, depending on surrounding words"
Krabina (talkcontribs)
SLauser (talkcontribs)

For what it's worth, I would love to see a working Lingo extension again as well. I'm 0% familiar with how extensions are built, but could potentially assist with maintenance if someone more experienced steps up to take the reins.

Planetenxin (talkcontribs)
Reply to "Next release?"

Bug: Lingo not running on custom namespaces

3
000Tom0000 (talkcontribs)

I've created a custom namespace but noticed that Lingo isn't loaded on this namespace. The documentation says that by default Lingo will run on all namespaces but this seems to be only for the default namespaces?

Is this by intention? Enabling it on your custom namespaces can be done as the documentation says.

F.trott (talkcontribs)
000Tom0000 (talkcontribs)

Running a mediawiki without any caching at the moment, it started working as soon as I explicitely added the custom namespace to the LocalSettings.

Reply to "Bug: Lingo not running on custom namespaces"
Return to "Lingo" page.