Enclosing qtip tags missing in 2.0.2-dev (66da4b0) on 1.27.1?

Just upgraded our MW from 1.23.8 to 1.27.1, and Lingo from 1.2.0 to 2.0.2-dev (66da4b0).

divs classed "qtip" seem missing surrounding "mw-lingo-tooltip-definition" tags.

Is this a quirk with my setup, or something common? Dlindenberger (talk) 21:47, 1 January 2017 (UTC)

Lingo Package did not work

Hi, I'm new to MediaWiki. I installed the Lingo Package (not via Composer). It did not work on my local MediaWiki version 1.28. Did I miss something. I followed the 'Common steps: Activation' on https://www.mediawiki.org/wiki/Extension:Lingo. Please help. Thamerish (talk) 19:45, 12 January 2017 (UTC)

Problem after installing Lingo

Hi,

after Lingo installation (not using composer) my wiki doesn't work. Here the error page

Warning: preg_match_all(): Compilation failed: two named subpatterns have the same name at offset 340 in /var/lib/mediawiki/includes/MagicWordArray.php on line 275

Warning: preg_replace(): Compilation failed: two named subpatterns have the same name at offset 340 in /var/lib/mediawiki/includes/MagicWordArray.php on line 288

Deprecated: Non-static method Lingo\LingoParser::parse() should not be called statically in /var/lib/mediawiki/extensions/SemanticGlossary/extensions/Lingo/src/Hooks.php on line 69 Exception encountered, of type "Error" [df92b57c602367bd7dc6ada5] /mediawiki/index.php/Main_page Error from line 75 of /var/lib/mediawiki/extensions/Lingo/src/LingoParser.php: Using $this when not in object context Backtrace:

1. 0 /var/lib/mediawiki/extensions/SemanticGlossary/extensions/Lingo/src/Hooks.php(69): Lingo\LingoParser::parse(Parser, string)
2. 1 /var/lib/mediawiki/includes/Hooks.php(195): Lingo\Hooks::parse(Parser, string, StripState)
3. 2 /var/lib/mediawiki/includes/parser/Parser.php(447): Hooks::run(string, array)
4. 3 /var/lib/mediawiki/includes/content/WikitextContent.php(331): Parser->parse(string, Title, ParserOptions, boolean, boolean, integer)
5. 4 /var/lib/mediawiki/includes/content/AbstractContent.php(497): WikitextContent->fillParserOutput(Title, integer, ParserOptions, boolean, ParserOutput)
6. 5 /var/lib/mediawiki/includes/poolcounter/PoolWorkArticleView.php(139): AbstractContent->getParserOutput(Title, integer, ParserOptions)
7. 6 /var/lib/mediawiki/includes/poolcounter/PoolCounterWork.php(123): PoolWorkArticleView->doWork()
8. 7 /var/lib/mediawiki/includes/page/Article.php(666): PoolCounterWork->execute()
9. 8 /var/lib/mediawiki/includes/actions/ViewAction.php(44): Article->view()
10. 9 /var/lib/mediawiki/includes/MediaWiki.php(503): ViewAction->show()
11. 10 /var/lib/mediawiki/includes/MediaWiki.php(288): MediaWiki->performAction(Article, Title)
12. 11 /var/lib/mediawiki/includes/MediaWiki.php(745): MediaWiki->performRequest()
13. 12 /var/lib/mediawiki/includes/MediaWiki.php(519): MediaWiki->main()
14. 13 /var/lib/mediawiki/index.php(43): MediaWiki->run()
15. 14 {main}

Before Lingo I had installed Semanticglossary (using composer). So in LocalSettings.php I have both

wfLoadExtension('Lingo');

wfLoadExtension( 'SemanticGlossary' );

Probably I am missing something very simple...

Now I have disabled the Lingo extension to work on the wiki.

Thanks for the help.

Lorenzo Loman87 (talk) 15:18, 3 February 2017 (UTC)

You still need to state your setup PHP, MediaWiki etc. to make this easier to assess. [[kgh]] (talk) 15:21, 3 February 2017 (UTC)

Hi,

at this link my version information Loman87 (talk) 15:25, 3 February 2017 (UTC)

The developer has updated the installation instructions after your post here. Perhaps you can give it another shot and see where we go from here. [[kgh]] (talk) 14:12, 6 February 2017 (UTC)

Colon in term

Is there way to use colon in term? Is there any method to escape? 83.169.194.12 (talk) 13:26, 18 April 2017 (UTC)

Unless you find some loophole I do not think so. F.trott (talk) 08:22, 4 May 2017 (UTC)

Can't install Lingo

 Problem 1
   - mediawiki/lingo 2.0.1 requires justinrainbow/json-schema ~1.0 -> satisfiable by justinrainbow/json-schema[1.1.0, 1.2.1, 1.2.3                   , 1.2.4, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.5.0, 1.6.1, v1.6.0] but these                    conflict with your requirements or minimum-stability.
   - mediawiki/lingo 2.0.0 requires justinrainbow/json-schema ~1.0 -> satisfiable by justinrainbow/json-schema[1.1.0, 1.2.1, 1.2.3                   , 1.2.4, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.5.0, 1.6.1, v1.6.0] but these                    conflict with your requirements or minimum-stability.
   - Installation request for mediawiki/lingo ~2.0 -> satisfiable by mediawiki/lingo[2.0.0, 2.0.1].

Fatal error: Call to undefined function Lingo\string()

Fatal error: Call to undefined function Lingo\string() in /.../w/extensions/Lingo/src/Element.php on line 166

Lingo breaking formatting when citations at end of line

We've found an odd formatting issue that pops up when Lingo is enabled. The following code should generate four headings with indented text below them, some with references before the full stop, and some after:

'''Heading 1'''
:Indented text with reference followed by a line break with clear which should clear previous formatting.<ref>Reference1</ref>

'''Heading 2'''
:Indented text with reference followed by blank line only, reference after punctuation.<ref>Reference 2</ref>

'''Heading 3'''
:Indented text with reference followed by blank line only, reference before punctuation<ref>Reference 3</ref>.

'''Heading 4'''
:And so on. All these display as expected in preview mode, including an extra line between 1 and 2. 

<references />

The expected formatting is shown in this image. However, when Lingo is enabled, the formatting is not correctly cleared at the end of any line where a citation comes after the punctuation - see this image. Inspection of the HTML source shows that various formatting tags are not being closed.

This occurs with Mediawiki 1.28.2 with Lingo 2.0.3, but also occurred on 1.24 with an older version of Lingo. --Danny252 (talk) 20:12, 20 June 2017 (UTC)

Terminology page does not display markup

I just started using the extension. For a bit my Terminology page showed the correct mouseover. Then, I added __NOGLOSSARY__ to my Terminology page and now mouseover doesn't work anywhere on the wiki. I have refreshed pages and I have also tried removing __NOGLOSSARY__ from the Terminology page and mouseover has not returned. Kmlancaster (talk) 18:27, 15 September 2017 (UTC)

That's a new one. I don't think I ever heard of somebody trying __NOGLOSSARY__ on the Glossary page itself.

In any case, with __NOGLOSSARY__ taken off, what happens if you take one of the pages where a tooltip should apear and do a null edit, i.e. go to the edit page and save without a change? F.trott (talk) 20:15, 15 September 2017 (UTC)

FWIW, Lingo looks at the raw wikitext of the Glossary page to build it's dictionary, so adding something unexpected will probably derail it. Would be nice of course if it gave at least a warning, but for that I'd need to have a look at the exact failure mode. No time right now, I'm afraid. F.trott (talk) 20:23, 15 September 2017 (UTC)

A null edit doesn't cause mouseover to return.

I used __NOGLOSSARY__ on the Terminology page because I figured you didn't need something defined by mouseover on the same page as you're giving the definitions. Kmlancaster (talk) 17:44, 18 September 2017 (UTC)

Any further thoughts on this?A Kmlancaster (talk) 20:26, 26 September 2017 (UTC)

Unfortunately not. I would have expected the tooltips to reappear once the NOGLOSSARY was out. I will have to try this myself to see what is going on. F.trott (talk) 23:06, 26 September 2017 (UTC)

Getting ERR_EMPTY_RESPONSE with Lingo 2.0.3 and MW 1.27.4

Thanks for fixing the issue with Preferences not saving. Using Git, I updated to the master branch and confirmed that the fix is working. However, on save, I am getting ERR_EMPTY_RESPONSE in Chrome and Page Cannot be Displayed in IE. There are no other errors, the debug log shows that the Post is succeeding, but the page is not reloading.

I also got this error when viewing my terms page and attempting to view historical revisions (I am using Approved Revisions, but not sure if this is relevant).

When I check out the specific commit where the preferences fix was done (d03c2d0a00b0b0ad5890eb646fec6567b24edb3f), everything works great. But any commit after that produces the errors.

Edit: After further testing, the error started happening with the above commit, as well. I checked out the commit before it (2cd9912db7d2f782558cbb0918a6c8f47a370068) and now everything appears to be working correctly again - and preferences are saving. I hope you are able to reproduce the issue. It's an odd one.

Thanks! Jlemley (talk) 19:22, 28 December 2017 (UTC)