Extension talk:Semantic Glossary

blank Mediawiki after installing Semantic Glossary

I have installed Semantic Glossary the way it is described. I also have Lingo 0.2 and Semantic Mediawiki (1.5) But once I install Semantic Glossary, I get a blank Wiki page. That means: nothing works. Not error message, nothing. The extension page says that Semantic Mediawiki 1.6 is required, but the official latest version is 1.5 So what could be wrong? Any help is greatly appreciated. Anja 129.233.51.12 15:23, 15 June 2011 (UTC)

You really need SMW 1.6, 1.5 will not work, there were considerable changes. SMW 1.6 not being released is also the main reason why Semantic Glossary has not seen a release yet. However, SMW 1.6 is reasonably stable by now so you might give it a try. F.trott 15:39, 15 June 2011 (UTC)

Thanks for the answer. I will try SMW 1.6

Anja 129.233.51.12 11:40, 16 June 2011 (UTC)

How do I enter terms?

Sorry for the Noob question but I've installed the extension as well as Lingo on my SMW site. I've created the properties and now I'm stuck to figure out how to start creating Pages/terms for the Glossary?

I'm new to SMW and just figuring out the structure of properties, types, categories, forms, templates and all. Glossary was my go-button and I LOVE the idea of it, but where the heck do I find some step-by-step instructs on how to start using it?

Thanks, Dave L 65.122.249.196 19:13, 2 December 2011 (UTC)

Ok, lets build a simple structure of pages:

• Create a page 'Hypertext Markup Language' and insert the following text (taken from wikipedia):

HTML is the predominant markup language for web pages. HTML elements are the basic building-blocks of webpages.
Web browsers can refer to CSS to define the appearance and layout of text and other material. The W3C, maintainer
of both the HTML and the CSS standards, encourages the use of CSS over explicitly presentational HTML markup. In
1980, physicist Tim Berners-Lee, who was a contractor at CERN, proposed and prototyped ENQUIRE, a system for CERN
researchers to use and share documents. Berners-Lee considered HTML to be an application of SGML. It was formally
defined as such by the IETF with the mid-1993 publication of the first proposal for an HTML specification.

• Create a page 'Cascading Style Sheet' and insert the following text:

* Abbreviation: [[Glossary-Term::CSS]]
* Definition: [[Glossary-Definition::Cascading Style Sheet]]

• Create similar pages for 'CERN', 'ENQUIRE', 'SGML', 'IETF'
• Go back to the page 'Hypertext Markup Language'. The abbreviations should be underlined and when you hover over them the Definition should appear.
• To provide links with the tooltips, define the Glossary-Link property for the pages, e.g. go to 'Cascading Style Sheet' and modify it so it looks like this:

* Abbreviation: [[Glossary-Term::CSS]]
* Definition: [[Glossary-Definition::Cascading Style Sheet]]
* Link: [[Glossary-Link::Cascading Style Sheet]]

• Go back to the page 'Hypertext Markup Language' to see the effect
• You can also provide interwiki links, e.g. on the 'Cascading Style Sheet' try replacing the line with the link by

* Link: [[Glossary-Link::wikipedia:Cascading Style Sheet]]

• If you want, create a page 'Glossary' and put the following query in it:

{{#ask:[[Glossary-Term::+]]
|?Glossary-Term
|?Glossary-Definition
|?Glossary-Link
|mainlabel=-
|format=table
}}

• Finally, if it worked, improve these instructions, put them on Extension:Semantic Glossary/Example and link to this page from the main page of the extension. Thanks! :)

Cheers, F.trott 21:31, 2 December 2011 (UTC)

Beautiful - Thank You so much! (and I posted the example) Dave88008 01:12, 3 December 2011 (UTC)

Thanks! :) F.trott 01:13, 3 December 2011 (UTC)

I looked at your Extension:Semantic Glossary/Example and made a general overhaul. Please also note that you should use <nowiki></nowiki> for any documentation purpose where you reference to internal declarations such as [[Glossary:: ... ]] otherwise the documentation will contain red links. MWJames 07:56, 3 December 2011 (UTC)

Hi James,

thanks for that. The screenshots especially are awesome, I am always to lazy to do them. One thing though - the original example was meant for somebody completely new to SMW (and maybe not too experienced with MW, either), hence the detailed step-by-step instructions. Should we get back into that direction? I like the idea of the Semantic Glossary as a starting point for an SMW experience, because it gives useful results almost immediately.

Cheers, F.trott 10:05, 3 December 2011 (UTC)

Hi Stephan, anything works for me as long as the user can work with it. Cheers, MWJames 21:16, 7 December 2011 (UTC)

I've been using Semantic Glossary and thanks to User:F.trott's simple explanation I was able to get up-and-running with Semantic Mediawiki.

I had been completely confused about properties, datatypes, templates and forms and how they all worked together.

But Mr. User:F.trott made it all come together after I posted the original question. Thank You!!!

Sorry to say that User:MWJames' "improvement" is in fact, very confusing. It may be technically accurate but is/was NOT the simple explanation as laid out in the original response.

I referred a friend here who is just beginning to learn SMW as I was a couple years ago, but when I saw the original answer had been removed I had to tell my friend to ignore this thread and we would find other ways to break down the learning process.

As an educator, I know it is all-to easy for experts in a particular field to forget how to break down the basics of a subject and sail right over the top of the heads of novice students...so I don't want this to come across as a criticism of User:MWJames. Just a reminder for us all to pay attention to the steps involved in the learning process.

I would suggest the original post response of User:F.trott be reverted to so others can gain the benefit of his tutorial. DaveL (talk) 16:05, 28 October 2013 (UTC)

When I follow this tutorial, my glossary shows the term, but my pages do not have any mouseover/markup effect. I'm very new to MW, so please forgive my fundamental question. Kmlancaster (talk) 19:49, 1 September 2017 (UTC)

Might be as easy as purging the page. On your page actions choose "Refresh". F.trott (talk) 18:33, 2 September 2017 (UTC)

Weird Liquid Threads behavior

I have the Glossary disabled on Talk pages and am using LQ on the site. If a discussion uses a term in the Glossary, the definition is inserted in the text of the message???

Is there a way to disable the Glossary by Application/Extension in localsettings or some other way to turn off the Glossary by Extension in addition to Namespace? Thanks DaveL (talk) 23:15, 12 May 2012 (UTC)

I think LQT stores messages in the Thread namespace. Try disabling that for Semantic Glossary. Cheers, F.trott (talk) 23:24, 12 May 2012 (UTC)

That worked, Thanks!!! DaveL (talk) 14:05, 13 May 2012 (UTC)

Glossary-Term as a text in a Forme

First of all: great extension! :-)

I have "hopefully a short" challenge:

For example, I define the properties Glossary-Term::CSS and Glossary-Definition::Cascading Style Sheet in a Glossary-page. And I'm using "CSS" as an fixtext in a Forme. Somthing like: "CSS: NameCSS". Now I open a Page with this Forms and get "CSSCascading Style Sheet" (term and definition concatenated) with no question mark. I expected only the term CSS. May you can help? Thanks! Gregor sander (talk) 11:23, 8 August 2012 (UTC)

The cause may either be that the CSS or JS was not loaded or that the JS fails at some point. I seem to remember that problem, but I thought I fixed it. Maybe could you try getting the latest versions of Lingo and SemanticForms? If that does not help, do you have a link to the problematic Form? F.trott (talk) 10:52, 30 August 2012 (UTC)

Semantic Glossary conflicts with Semantic Forms

First of all, thank you for this extension!

I've tried this extension, but it seems it conflicts with Semantic Forms extension. My observation is the following: When the property name (eg.CSS property name) contains a term (eg. CSS) from a glossary, the "Edit with form" option will not work anymore. Is there any workaround for this problem?

Thank you,

Ndrew 78.92.15.81 10:30, 5 September 2012 (UTC)

Hi Andrew,

I was not aware of this problem until now, so alas I do not know a workaround. Maybe you could try to exclude the form from markup by including the magic word __NOGLOSSARY__ anywhere in that form's text. F.trott (talk) 11:32, 5 September 2012 (UTC)

Dear F.trott,

Unfortunately all of my pages based on forms... :-(

Best regards,

Ndrew 78.92.15.81 12:42, 5 September 2012 (UTC)

Hi Stephan, I don't really remember but I thought I had the same problem and fixed this excluding formedit from text parsing

class LingoParser 
protected function realParse( &$parser, &$text ) {
...
if ( $text == null ||
...
$action == 'formedit' ||			
...

MWJames (talk) 13:26, 5 September 2012 (UTC)

Thank you very much, it's Perfect! :-)

Best regards, ndrew 78.92.15.81 14:56, 5 September 2012 (UTC)

I now fixed this by using an earlier hook. The problem was, that Lingo also annotated stuff between nowiki tags. This should not happen anymore now.

Cheers, F.trott (talk) 22:22, 27 October 2012 (UTC)

Plans of development

I love this extension! How are you planning to further improve it? What about supporting the word forms like "fox - foxes". Katkov Yury (talk) 16:36, 6 November 2012 (UTC)

handling synonymous terms in Semantic Glossary

How do I handle synonyms in Semantic Glossary?

In Lingo you can specify synonyms in the following way:

TERM ACRONYM

term

Term definition

Thanks!

Anna 128.183.170.184 18:12, 27 February 2013 (UTC)

Hi Anna, good question. I thought it would be as easy as specifying a second Glossary-Terms for one definition. But I just tried it and it does not work. So right now the only way to do this is to actually define the two synonyms separately. I will fix the extension so this should be easier in future versions.

Cheers F.trott (talk) 08:43, 28 February 2013 (UTC)

Hi all,

it is possible, but elaborate to create synonyms for a page. I succeded to do so by creating a Semantic Internal Object for every synonym on the page. This can e.g. be simplified by using functions like {{lc:term}} and {{uc:term}} in templates to simulate case-insensitivity. Just don't look on the complexity...

thx 195.226.179.252 13:28, 6 September 2013 (UTC)

Have some solution to use synonymous in Semantic Glossary? 187.4.43.18 (talk) 18:34, 26 June 2017 (UTC)

Glossary items in links and properties

first off, really good idea to use SMW for glossary items, makes them very reusable.

If I define a glossary term A1, and have these:

[[A1 testing]], [[Property::A1 testing]]

I end up with this:

[[A1 testing]] where the brackets are visible, A1 is a glossary item but there's no link, and [[:A1 testing|A1 testing]], same condition with no assignment.

Any way to fix this?

thanks! David Mason (talk) 15:43, 31 March 2013 (UTC)

Fixed in 0.4.2. Alas, if you have an MW pre1.20 installation now the annotation of terms between nowiki-tags is back. No way to fix this, i'm afraid. F.trott (talk) 09:04, 7 April 2013 (UTC)

sorry, but where do I get 0.4.2? I've just found 0.1. David Mason (talk) 18:25, 8 April 2013 (UTC)

Sorry, I meant Extension:Lingo 0.4.2. Here is a direct link: http://code.google.com/p/lingo-extension/downloads/list

There is a small bug left, Lingo 0.4.2 will still report being 0.4.1 on Special:Version. Will fix that soonish. F.trott (talk) 19:09, 8 April 2013 (UTC)

Do I disable the Lingo Extension

I implemented the Lingo extension before finding this. Am I supposed to disable the Lingo Extension in the localsettings.php?

Also, any recommendation for the Property Types for "Glossary-Term", "Glossary-Definition" and "Glossary-Link"? Shizzire (talk) 14:13, 25 June 2013 (UTC)

"Semantic Glossary depends on the Lingo extension. You need to install Lingo first." Answers the first question. Shizzire (talk) 14:14, 25 June 2013 (UTC)

Hi Shizzire,

no need to take care of the Property Types. In fact, you do not need to define those properties yourself. Semantic Glossary does that internally. They are available and recognized as soon as you installed Semantic Glossary.

Cheers F.trott (talk) 14:20, 25 June 2013 (UTC)

Ok thanks. Should I be concerned that these properties appear "redlinked" in the Properties pages? Lingo was working, but with the addition of SemanticGlossary, it has stopped. I have two pages with "Glossary-Term" properties, but the inline query below has no data:

{{#ask: [[Glossary-Term::+]]
|?Glossary-Term
|?Glossary-Definition
|?Glossary-Link
|mainlabel=-
|format=table
}}

Relevant versions:
*Semantic Glossary (Version 0.1)
*Semantic MediaWiki (Version 1.8.0.1)
*MediaWiki	1.19.2
*PHP	5.3.8 (cgi-fcgi)
*MySQL	5.5.16-log
*Lingo (Version 0.4.2)

Shizzire (talk) 14:56, 25 June 2013 (UTC)

The red links are normal. There really is no wiki page for these properties, after all. Also Lingo stopping to work is as expected, since Semantic Glossary has taken over as a storage for the terms.

I have no clue, why those terms don't show up in the query. You could try to edit and save the pages with the term definitions and then purge the page with the query. F.trott (talk) 19:14, 25 June 2013 (UTC)

A friend suggested "The property page indicates that "Glossary-Term" is a "special" property in the wiki, meaning probably that it was set up by your Lingo Extension. Special properties cannot be queried using #ask." However this page[1] contradicts the statement:

Since SMW 1.4.0, special properties can be used in browsing interfaces and inline queries just like all other properties.

I've noticed other problems with semantic data and #ask, so I think the root cause is beyond SemanticGlossary. Thanks for the help. Shizzire (talk) 20:22, 25 June 2013 (UTC)

How to insert URL / WEB links?

Hi, Thank you very much for the extension. At the page glossary I have added the :

{{#ask:Glossary-Term::+

|?Glossary-Term

|?Glossary-Definition

|?Glossary-Link

|mainlabel=-

|format=table

}}

and then I have created an item:

{{#subobject:epi

|Glossary-Term=epipen

|Glossary-Definition=epipen is an allergy tool

|Glossary-Link=epipen details}}

My question is at the field: Glossary-Link=epipen details what shall I right in order to have an external link like www.epipen.co.uk and not an internal one.

Many thanks,

Achilles 134.83.1.244 10:55, 10 July 2013 (UTC)

Sorry for the late answer, I completely missed this.

External links are not supported, I am afraid. F.trott (talk) 14:22, 20 November 2013 (UTC)

SemanticGlossary and Geshi

Hi,

thanks for the wonderful extension! I would like to use SG to show function and parameters of API-Calls in code I formatted using Extension:SyntaxHighlight_GeSHi. I consider Geshi to use some kind of nowiki to prevent the highlighting, anyway, it does not work.

Does anybody have a hint where to enable this?

thx 195.226.179.252 10:02, 5 September 2013 (UTC)

Hi,

I found a solution for myself. In Lingo.php line 79 I replaced

$wgHooks['ParserAfterParse'][] = 'LingoHooks::parse';

with

$wgHooks['ParserBeforeTidy'][] = 'LingoHooks::parse';

Thus I re-implemented the nowiki-Bug, which to me is a feature. Could this be made configurable? Are there any further flaws with it?

thx 195.226.179.252 13:13, 6 September 2013 (UTC)

Conflict with HeaderTabs

Just now I've installed SG 0.1 and Lingo 0.4.3 alpha (both development versions), but notice some odd behaviour in combination with the Header Tabs extension. For some reason, either Lingo or SG forces a table of contents to appear on top of the page. Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 11:54, 30 September 2013 (UTC)

Can you please tell me where to download Lingo 0.4.3 alpha? Wikimanz (talk) 08:34, 16 October 2013 (UTC)

Here: https://git.wikimedia.org/zip/?r=mediawiki/extensions/Lingo&format=zip F.trott (talk) 08:40, 16 October 2013 (UTC)

Has anybody worked on this topic in the meantime?

I have installed

• Lingo 1.1.0
• Semantic Glossary 1.0.0
• HeaderTabs 0.10.0
• MW 1.21.0
• SMW 1.8.0.5

and realize a conflict between Semantic Glossary and HeaderTabs.

My definition of a term is:

{{#set_internal:Glossary
|Glossary-Term=HTML
|Glossary-Definition=HyperText Markup Language
|Glossary-Link=wp:HTML}}

My HeaderTab example is

= 1 =
HTML
= 2 =
aaaaaaaaaaaa
<headertabs/>

Obviously the tool tip generated by Semantic Glossary / Lingo for the term "HTML" interferes with the tab generation of Headertabs.

Has anybody found a solution for this problem? Kappa (talk) 15:33, 8 August 2014 (UTC)

Markup such as bold and italic

I may be missing something, but I can't find how to enable standard character markup such as bold and italic in the tooltips. Is that what the CSS style definition is intended for? If so, can anyone give a concrete example how such a definition in a stylesheet would look like? Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 11:47, 11 October 2013 (UTC)

Parsing definitions as wikitext is not implemented yet. F.trott (talk) 12:10, 11 October 2013 (UTC)

Thanks, that explains things : ) Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 18:14, 11 October 2013 (UTC)

Next release

Heiya, quite some time has passed since the 0.1 release and some changes were made to the code to improve this extension. Will there be a new release, probably with the 1.9 release of SMW? Cheers [[kgh]] (talk) 19:40, 29 November 2013 (UTC)

Good point. But Lingo has to be released first. So much to do, so little time. :) F.trott (talk) 20:06, 29 November 2013 (UTC)

Yeah, on step at a time. However, keep on fighting at will! :) [[kgh]] (talk) 21:03, 29 November 2013 (UTC)

Making it installable with SMW 2.x

Heiya, currently even master of this extension is not installable via Composer when trying to update to SMW 2.x since it requires SMW 1.9.x as Composer prompts:

mediawiki/semantic-glossary dev-master requires mediawiki/semantic-media-wiki ~1.9

Cheers [[kgh]] (talk) 07:16, 23 July 2014 (UTC)

Should work now.

Cheers F.trott (talk) 07:33, 23 July 2014 (UTC)

Thanks for trying to fix this, however it still does not work. :(

When having "mediawiki/semantic-glossary": "@dev", I get this:

Problem 1
 - mediawiki/semantic-glossary dev-master requires mediawiki/semantic-media-wiki ~1.9, ~2.0 -> no matching package found.
 - mediawiki/semantic-glossary dev-REL1_23 requires mediawiki/semantic-media-wiki ~1.9 -> no matching package found.
 - mediawiki/semantic-glossary 1.0.0 requires mediawiki/semantic-media-wiki ~1.9 -> no matching package found.
 - Installation request for mediawiki/semantic-glossary @dev -> satisfiable by mediawiki/semantic-glossary[1.0.0, dev-REL1_23, dev-master].

When adding "mediawiki/semantic-glossary": "dev-master", it looks a bit better:

Problem 1
 - Installation request for mediawiki/semantic-glossary dev-master -> satisfiable by mediawiki/semantic-glossary[dev-master].
 - mediawiki/semantic-glossary dev-master requires mediawiki/semantic-media-wiki ~1.9, ~2.0 -> no matching package found.

So it seems that commaseparating different branches does not work. Minimum stability is at "dev" in the "composer.json". [[kgh]] (talk) 07:51, 23 July 2014 (UTC)

Perhaps it does not work since SMW 2.x is still a RC and not officially released with a 2.0? [[kgh]] (talk) 07:54, 23 July 2014 (UTC)

Sorry, my fault. Comma means AND. Inserted a pipe now, which should mean OR. F.trott (talk) 07:58, 23 July 2014 (UTC)

Talk about finding the solution at the same time. Yeah, as a MediaWikian I would say: Do the pipe trick, but here it is not a trick. ;) Thanks, this worked with "@dev" as well as with "dev-master"! [[kgh]] (talk) 08:02, 23 July 2014 (UTC)

I have just seen how Jeroen has done this for SESP. See here on GitHub

"require": {
	"php": ">=5.3.0",
	"composer/installers": "1.*,>=1.0.1",
	"mediawiki/semantic-media-wiki": "1.9.*|~2.0"
},

[[kgh]] (talk) 07:58, 23 July 2014 (UTC)

Another way I have seen is "mediawiki/semantic-media-wiki": ">=1.9" That's probably the solution if one does not like to revisit the dependency stuff every time a new branch is available. [[kgh]] (talk) 08:08, 23 July 2014 (UTC)

I think it is a rather hacky solution. It includes all versions above 1.9 not taking care of any possible API changes in higher versions of SMW. The whole point of dependency management is to make sure only compatible versions are combined, which this rule will disable. See [2]. F.trott (talk) 08:21, 23 July 2014 (UTC)

Indeed this reinstates the situation ante (without Composer). [[kgh]] (talk) 13:45, 23 July 2014 (UTC)

Creating Form inputs for glossary terms

On the Semantic_Glossary overview it mentions that "You can easily build a user interface to edit the glossary, e.g. using Semantic Forms.".

Does anyone have any more information than this regarding how to set the required objects up? I have tried different combinations of creating templates, forms and categories but can't find anyway of populating the 'Glossary-Term', 'Glossary-Definition' etc values via an input form?

Thanks in advance for any suggestions and apologies if I am missing a glaringly obvious solution somewhere. Nprobinson (talk) 13:23, 27 November 2014 (UTC)

Just a quick answer with an example, presuming you have installed SMW, SF and SG properly:

Say you have something like the following in a template called "Template:Glossary term" (subobjects are used here as recommended by the docs):

=={{{Term|}}}==
{{{Definition|}}} (link: {{{Link|}}})
{{#subobject:
|Glossary-Term={{{Term|}}}
|Glossary-Definition={{{Definition|}}}
|Glossary-Link={{{Link|}}}
}}

Then in the form you may want to use multiple-instance templates:

{{{for template|Glossary term|multiple}}}
===Term===
{{{field|Term|input type=text}}}
===Definition===
{{{field|Definition|input type=textarea}}}
===Link===
{{{field|Link|input type=textarea}}}
{{{end template}}}

Does that help you in any way? Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7) 15:20, 27 November 2014 (UTC)

Create a page Category:Glossary Term:

[[Has default form::Glossary Term]]

Create a page Template:Glossary Term:

{{#set:
|Glossary-Term={{{Glossary Term|}}}
|Glossary-Definition={{{Glossary Definition|}}}
}}

Create a page Form:Glossary Term:

<noinclude>
{{#formlink:form=Glossary Term|link text=New Glossary Term}}
</noinclude><includeonly>
{{{info|create title=Create new Glossary Term|edit title=Edit Glossary Term|page name=<Glossary Term[Glossary Term]>}}}
{{{for template|Glossary Term}}}
{| class="formtable"
! Term:
| {{{field|Glossary Term|input type=text}}}
|-
! Definition:
| {{{field|Glossary Definition|input type=textarea}}}
|}
{{{end template}}}
{{{standard input|save}}} {{{standard input|cancel}}}
</includeonly>

Follow the link on the Form page and create some terms.

It may be necessary to purge the pages containing text with terms. F.trott (talk) 15:21, 27 November 2014 (UTC)

Heh, mid-air collision. :)

Both should work. Cavila's for one page containing several terms (up to the whole glossary), mine for one page per term. F.trott (talk) 15:24, 27 November 2014 (UTC)

Thanks for the responses.

I ended up implementing the one page per term as it fitted my requirements better but thank you both for the guidance.

Solution worked perfectly. Nprobinson (talk) 09:33, 10 December 2014 (UTC)

When I follow your example, I get the following as the only visible content on my Form:Glossary Term page. Any help?

{{#formlink:form=Glossary Term|link text=New Glossary Term}} Kmlancaster (talk) 19:58, 1 September 2017 (UTC)

Usually when a function call appears verbatim on the page it means, that the respective function is unknown. Make sure that PageForms is installed properly. F.trott (talk) 18:35, 2 September 2017 (UTC)

Do both examples above use PageForms? One mentions SF. BTW, could this all be configured in the extension itself?

Many thanks, Dan Bolser (talk) 09:46, 27 March 2020 (UTC)

They should work with PageForms. This is a question from 5y ago, SF was probably not yet renamed back then.

The whole idea of Semantic Glossary (over e.g. Lingo) is to leverage SMW's capabilities. So while there may be a reduction in setup effort for wiki admins, I am not sure if it would make sense to hard-code a special page or something instead of utilizing the available capabilities in the SMW ecosystem. Maybe it would be useful to have the above solutions as a cookbook recipe somewhere in the documentation.

Or maybe I am just not getting the point. :) F.trott (talk) 10:27, 27 March 2020 (UTC)

Terms lost their pop (up) after upgrade

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I recently upgraded my site from MW 1.18 to 1.24 - SMW 1.8 to 1.9 via Semantic Bundle and upgraded Semantic Glossary from 0.1 to 1.1 (Lingo too)
The Glossary category page used to store the glossary works and all terms display on their individual pages but they stopped popping up on mouse-over within documents on the site.
Template:

<includeonly>{| class="wikitable"
! Term
| [[Glossary-Term::{{{Term|}}}]]
|-
! Definition
| [[Glossary-Definition::{{{Definition|}}}]]
|-
! Link
| [[Glossary-Link::{{{Link|}}}]]
|}

[[Category:Glossary]]
</includeonly>

Form:

{| class="formtable"
! Term:
| {{{field|Term|mandatory}}}
|-
! Definition:
| {{{field|Definition|mandatory}}}
|-
! Link:
| {{{field|Link|mandatory}}}
|}
{{{end template}}}

Is there a version problem or is my code bad?
Thanks in advance! DaveL 00:39, 13 February 2015 (UTC)

Neither I'd say. There must be something else. You can try the following:

• run .../maintenance/update.php
• run .../extensions/SemanticMediawiki/maintenance/rebuildData.php
• run .../extensions/SemanticGlossary/maintenance/rebuildGlossaryCache.php

I am not sure, if any of this will help, but without any more clues it is the best I can tell you.

That wiki is not public by any chance, is it? F.trott (talk) 06:37, 13 February 2015 (UTC)

Thanks, yes it's public - the template is here and the form here. DaveL 14:18, 13 February 2015 (UTC)

Ran update.php ...no problem

Ran .../extensions/SemanticMediawiki/maintenance/rebuildData.php

-bash: syntax error near unexpected token `(' dl88008@scientolipedia.org [~/public_html/w/extensions/SemanticMediaWiki/maintenance]# Fatal error: Call to a member function isSpecialPage() on a non-object in /home/dl88008/public_html/w/extensions/SemanticResultFormats/formats/gallery/Gallery.php on line 70

Line 70 - SemanticResultFormats/formats/gallery/Gallery.php

if ( !$this->getContext()->getTitle()->isSpecialPage() ) {

Ran .../extensions/SemanticGlossary/maintenance/rebuildGlossaryCache.php ...no problem DaveL 17:55, 13 February 2015 (UTC)

Please try to add the following line at the end of your LocalSettings.php:

$wgIncludejQueryMigrate = true;

F.trott (talk) 18:13, 13 February 2015 (UTC)

You're a mensch sir - works great! Thank You

BTW - I like the smaller script popping below the line now - nice improvement - looking forward to using the other enhancements. DaveL^{MW 1.24.1, PHP 5.4.37, MySQL5.1.73-cll SMW 1.9.2} 18:22, 13 February 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Accessing definitions through API

I'm trying to access Dave8808's Glossary below with the Semantic Search function. Using the Glossary-Definition property isn't getting what shows up on the "Definition" page. Does anyone know how to access that? 131.191.49.211 (talk) 03:37, 1 August 2015 (UTC)

Mobilefrontend inserts definitions in freetext areas

I installed MobileFrontend extension but noticed that semantic glossary definitions were getting inserted into the text on pages immediately after a term in the glossary was used so I've had to disable MF.

I can't imagine the NS declarations would be a solution but is there something similar available or being looked at? (will have to accelerate plans to implement either Foreground or Chameleon skin otherwise)

MW 1.25.1, SMW 2.2, SG 1.1, Lingo 1.2 DaveL^{MW 1.25.1, PHP 5.4.37, MySQL5.1.73-cll SMW 2.2} 22:15, 8 August 2015 (UTC)

Blank page after installing Semantic Glossary

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi, i installed the lingo extension and the semantic glossary. After that i only get a blank page in our wiki. Has anyone an idea?

Versions:

MediaWiki	1.22.13
PHP	5.4.41-0+deb7u1 (apache2handler)
MySQL	5.5.44-0+deb7u1

Semantic_MediaWiki: 1.8.0.5

Lingo: 1.2.0

Semantic Glossary: 1.1.0

Thanks in advance! LNAG-IT (talk) 13:04, 12 August 2015 (UTC)

> Semantic_MediaWiki: 1.8.0.5

This is not going to work with an outdated SMW release such as 1.8*, it requires at least 1.9 (and soon 2.2).

For details, please have a look at https://github.com/SemanticMediaWiki/SemanticGlossary MWJames (talk) 17:35, 26 September 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Using Cargo instead of SMW

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hello, are there plans to make Semantic Glossary working with Cargo extension ? 85.168.193.149 (talk) 08:12, 13 March 2016 (UTC)

No.

But it should not be to complicated to create a Cargo-specific extension. Lingo (the underlying extension responsible for the markup of terms) was created with extensibility in mind. You just need to create and register a Cargo-specific backend and that should be it. F.trott (talk) 11:45, 13 March 2016 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Extension Registration

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have installed Lingo and Semantic Glossary using composer under MediaWiki 1.26:

composer require mediawiki/lingo "~2.0"
composer require mediawiki/semantic-glossary "~2.0"

If I follow the installation instructions and add the two extension registration statements

wfLoadExtension( "Lingo" );
wfLoadExtension( "SemanticGlossary" );

an exception is raised in mediawiki/includes/MagicWords.php:

[error] [fd810cd6] /mywiki/index.php/Main_Page   ErrorException from line 951 of .../includes/MagicWord.php: PHP Warning: preg_match_all(): Compilation failed: two named subpatterns have the same name at offset 340

I added some debugging statements and determined that the subpattern name that is duplicated is <a_noglossary>:

regex = /(?P<a_notoc>__NOTOC__)|(?P<a_nogallery>__NOGALLERY__)|(?P<a_forcetoc>__FORCETOC__)|(?P<a_toc>__TOC__)|(?P<a_noeditsection>__NOEDITSECTION__)|(?P<a_notitleconvert>__NOTITLECONVERT__)|(?P<b_notitleconvert>__NOTC__)|(?P<a_nocontentconvert>__NOCONTENTCONVERT__)|(?P<b_nocontentconvert>__NOCC__)|(?P<a_noglossary>__NOGLOSSARY__)|(?P<a_noglossary>__NOGLOSSARY__)/iuS

If I remove the extension registration statement for Lingo, Lingo is still autoloaded, and the exception does not get thrown.

Is the fact that Lingo should not be explicitly loaded an omission in the SemanticGlossary documentation? Or is the duplicate definition of the __NOGLOSSARY__ magic word if Lingo and SemanticGlossary are both explicitly loaded a bug? Cindy.cicalese (talk) 01:26, 5 April 2016 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Semantic Glossary & Lingo Browse Problem

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I install Semantic Glossary as my last extension. I modify LocalSettings.php as follows;

wfLoadExtension('SemanticGlossary');

I run the following in a Composer session; composer require mediawiki/semantic-glossary "2.*"

The errors when I browse the wiki are like the following;

Warning: preg_match_all(): Compilation failed: two named subpatterns have the same name at offset 340 in C:\xampp\htdocs\test01\includes\MagicWordArray.php on line 275

Warning: preg_replace(): Compilation failed: two named subpatterns have the same name at offset 340 in C:\xampp\htdocs\test01\includes\MagicWordArray.php on line 288

As a solution, I comment out the LocalSettings.php string facilitating Lingo;

wfLoadExtension('Lingo');

After this the wiki works normally and I have use of Semantic Glossary.

* OS: Windows 8

* XAMPP: xampp-win32-7.0.9-1-VC14-installer.exe

* MediaWiki: 1.27.1

* Semantic Mediawiki: 2.4.1

* Lingo: 2.0.1

* Semantic Glossary: 2.0.1

* PHP: 7.0.9

* MariaDB: 10.1.16

* Semantic Result Formats: 2.4

* Replace Text: a2a8fbf

* SimpleTooltip: f8bfbf3 AKSHA (talk) 17:18, 16 October 2016 (UTC)

What's the problem?

From the instalation instructions on Extension:Semantic Glossary: "You do not have to take care of any dependencies, those are solved by Composer. It is in particular NOT necessary to install the Lingo extension separately. Doing so will result in errors." F.trott (talk) 17:31, 16 October 2016 (UTC)

Thank you F.trott. All is well for me. Just sharing. I will take note of your better information. AKSHA (talk) 20:42, 16 October 2016 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Semantic Query for Glossary Terms

Would it be possible to create a Semantic query or a variant of a query that provides a list of terms that are defined by Semantic Glossary?

For example, I have a group of pages that are either members of a category, or who all have a relationship back to a parent page. On the parent page, I would like to place a query to list all the terms and acronyms that appear on the child pages. However, since the glossary terms do not have hard links on those pages, but just have the Semantic Glossary term underlined with the popup definition, I don't know how to query for those "soft links" that appear on the child pages. Is this possible?

Thanks! Ray Jorgensen Rwjorgensen (talk) 14:12, 7 December 2016 (UTC)

You can of course use Glossary-Term, Glossary-Definition and Glossary-Link in queries, just like any other property. I did not actually test this, but a query to list defined terms and definitions on the wiki should be something like:

{{#ask: [[Glossary-Term::+]]
|?Glossary-Term
|?Glossary-Definition
|mainlabel=-
|format=table
}}

However, if you are looking for a list of all terms that are used on a particular page (or pages), you are out of luck, I'm afraid. F.trott (talk) 15:30, 7 December 2016 (UTC)

Install Semantic Glossary with Composer

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

MediaWiki 1.28.0 I install "mediawiki/semantic-glossary": "~2.0" with composer and add wfLoadExtension('SemanticGlossary'); to local settings, it changes the layout of Special:Versions page removing versions and names. Legaulph (talk) 12:45, 14 December 2016 (UTC)

Got removed lingo and added wfLoadExtension('SemanticGlossary'); Legaulph (talk) 13:36, 14 December 2016 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Link icon not loaded

Hi everybody,

a minor issue occurs when I use the property Glossary-Link: in the pop-up the link icon is not loaded properly and I don't understand the reason.

You can check the issue here.

Many thanks for the help!

Lorenzo Loman87 (talk) 14:27, 17 January 2017 (UTC)

When trying to load the icon the server responds with a 404, i.e. File not found. Make sure http://mediawikiarchivio.unigre.it/mediawiki/extensions/Lingo/styles/linkicon.png exists and is accessible. F.trott (talk) 14:32, 17 January 2017 (UTC)

thanks for the answer. If I don't have the Lingo extension installed, can I change the default icon with something else? Loman87 (talk) 15:33, 17 January 2017 (UTC)

You should have Lingo. It is a dependency of Semantic Glossary and automatically installed by Composer. F.trott (talk) 16:37, 17 January 2017 (UTC)

I believe that this is not stated clearly enough in the installation instructions. It should state explicitly that Semantic Glossary requires the Lingo extension:

- Lingo is installed automatically when installing Semantic Glossary with Composer

- When Semantic Glossary is installed manually using the tar ball or zip from GitHub, Lingo must also be upload manually into the extensions folder

When Lingo is not installed, the link image does not appear, but - more severely - the Special:Preference page is broken. Any changes there are not saved to the db. 82.143.124.122 (talk) 09:52, 23 May 2017 (UTC)

No, this is wrong.

Installing Lingo on top of SemanticGlossary is one of the most common mistakes people make. It leads to strange problems that are hard to debug especially when people do not mention that they used some "custom" installation process.

The zip file already contains all dependencies, including Lingo. It should work out of the box. If it does not, please raise an issue clearly mentioning that you are using the tar ball/zip file. F.trott (talk) 10:56, 23 May 2017 (UTC)

Tracked at https://github.com/SemanticMediaWiki/SemanticGlossary/issues/24. I hope to fix this in the next few days. F.trott (talk) 11:15, 23 May 2017 (UTC)

It's fixed now in SG 2.0.3. F.trott (talk) 23:39, 23 May 2017 (UTC)

Error trying to get Semantic Glossary working

I have been trying unsuccessfully to get Semantic Glossary to work and I've been having issues. Whenever I enable it in LocalSettings.php I get the following error in the php log:

PHP Fatal error:  Call to a member function getValueFormatter() on null in C:\inetpub\wwwroot\w\extensions\SemanticMediaWiki\includes\datavalues\SMW_DV_String.php on line 74

I was wondering if anyone had come across this and/or had a fix for it?

Version info:

Component	Version
MediaWiki	1.28.1
SMW	2.5.2
Semantic Result Formats	2.5.0
Semantic Cite	1.3.0
Semantic Breadcrumb Links	1.3.1
DisplayTitle	1.2
Semantic Glossary	2.0

Plus various other extensions that I am not sure whether or not they are causing problems. Kriegfrj (talk) 07:08, 7 July 2017 (UTC)

Try upgrading to latest version, please. F.trott (talk) 09:11, 7 July 2017 (UTC)

Well, whaddaya know. I thought I was already at the latest version (I normally check that before posting for help), but it turns out I had a typo in my composer.local.json, specifying version 2.0 of SG rather than ~2.0. When I fixed it and ran composer it upgraded to 2.2.0 - and the problem seems to have resolved itself.

Thank you for your help, F.trott - to be honest, I'm a bit embarrassed that the solution turned out to be so trivial. At least it wasn't as simple as rebooting the web server. :) Kriegfrj (talk) 13:21, 9 July 2017 (UTC)

:D F.trott (talk) 14:46, 9 July 2017 (UTC)

popup width

Dear all,

I'm running MediaWiki 1.29.0 with Semantic Glossary 2.2.0. Everything is working as expected, apart from the popup width for the glossary terms, which seems to default to a rather small width (see here: https://www.dropbox.com/s/3mo9vhfwfm0ia8l/popup_issue.jpg?dl=0)

I've tried to find a way to change the default width of the popups. Can anybody shed some light on this please? Is this all governed by the Lingo style sheets?

Many thanks -

Martin Mri ice (talk) 10:17, 17 November 2017 (UTC)

It works for me. The Qtip library sets the min width to 50px and the max width to 280px for the class .qtip and for me this is exactly what's applied: The tip grows as much as allowed in width until it reaches max width and then breaks to the next line. It appears that for some reason on your page the tip tries to become as narrow as possible, but I have no idea why. Lingo does not change the dimensions of the tip.

I could have a look at the applied styles on your wiki if it is public. F.trott (talk) 12:25, 17 November 2017 (UTC)

Thank you very much for taking the time to reply and sorry it's taken me a while to come back to you. Well, it's a school day every day. I'm using the Approved Revision Extension. When there is a new revision, and you approve that, it shows the page you've approved, with "This revision of the page has been set as the approved version." at the top of the page. While on this view, the behaviour of the popups is exactly as above. Once I reload the page, everything is fine :) So, luckily, a non-problem!

I do have another question that I'm hoping someone might know the answer to:

When defining the Glossary-Terms, how do I account for different spelling / capitalization? So let's say I want a popup for MASH and different spellings are Mash, M*A*S*H and MASH.

I have found that it seems to work if I define multiple Glossary-Terms as below

[[Glossary-Term:MASH]]
[[Glossary-Term:M*A*S*H]]
[[Glossary-Term:Mash]]

That works reasonably well, but when I build the "auto-glossary" through

{{#ask:[[Glossary-Term::+]]
|?Glossary-Term
|?Glossary-Definition
|?Glossary-Link
|mainlabel=-
|format=table
}}

it will obviously list all variants for the Glossary-Term.

So my question is whether a) I'm using the right way of defining multiple Glossary-Terms or whether there is a better way of doing this? and b) if the answer to a) is yes - does #ask have an possibility to limit to the first result for multiple definitions (a bit like select top 1 * in SQL).

Hope this makes sense?

Thanks - Martin Mri ice (talk) 09:30, 22 November 2017 (UTC)

The answer to the first question is yes, this is exactly how it should be done.

The answer to the second question in principle is also yes, but it is not as simple as it seems at first glance. One problem is that just because you define properties in a certain order does not mean that they appear in that same order when queried. So defining MASH, then M*A*S*H, then Mash may well lead to them appearing as M*A*S*H, MASH, Mash. The next problem is that SMW does not natively support this kind of grouping, so you would have to use the template format and in the template work with string functions (or use #array_map from the PageForms extension) to create the table row by hand.

An altogether simpler approach would be to just define a new property Main Term that you set in addition to the Glossary-Term properties on each page and then query for that:

{{#ask:[[Main Term::+]]
|?Main Term
|?Glossary-Definition
|?Glossary-Link
|mainlabel=-
|format=table
}}

F.trott (talk) 10:02, 22 November 2017 (UTC)

Perfect, thank you very much. Mri ice (talk) 11:15, 22 November 2017 (UTC)

Not all instances found

I'm really sorry about yet another question. I've tried to troubleshoot to no avail and am now hoping I'm missing something really obvious.

So I've started building up a glossary and have added ca. 150 definitions so far. Everything has been working well up until now. I've added a new glossary term definition using the same template as I've used for everything else:

[[Glossary-Term::MOSAIQ]]

This is a term that occurs fairly frequently.

What I don't understand is that it does not seem to find all occurrences of the term, but some. I have uploaded a screenshot: https://www.dropbox.com/s/vrlmldqmi65gu0e/mosaiq_semantic_glossary.jpg?dl=0

Its correctly identified 3 instances, but it hasn't identified 4 others.

Is there a limit on how many it will find per page? How can I troubleshoot this?

As before, very grateful for any help.

Thanks

Martin Mri ice (talk) 16:12, 22 November 2017 (UTC)

For the moment I have no idea at all. Looks like a bug. I'll get back to you. F.trott (talk) 17:18, 22 November 2017 (UTC)

Thank you and I must apologize, I have caused this all by myself :(

It appears that I had two Glossary-Terms defined. The first one:

[[Glossary-Term::MOSAIQ]]

and the second one:

[[Glossary-Term::MOSAIQ Server]]

All instances of MOSAIQ Server got tagged appropriately. Some instances of MOSAIQ on its own did and others didn't. Having removed the second term, all instances of MOSAIQ are now tagged.

I guess that what I tried to do was simply not possible.

Sorry to have wasted your time.

Thank you - Martin Mri ice (talk) 18:56, 22 November 2017 (UTC)

Ah yes, that might be problematic, although I still think it'd be nice if it worked. Thanks for the clarification. F.trott (talk) 19:11, 22 November 2017 (UTC)

Its someone alive here?!

A database query error has occurred. This may indicate a bug in the software.

[a833f4b26fe85a741b68abc6] 2018-03-21 12:30:08: Fatal exception of type "Wikimedia\Rdbms\DBQueryError" Raulcpop (talk) 12:30, 21 March 2018 (UTC)

https://www.chiark.greenend.org.uk/~sgtatham/bugs.html F.trott (talk) 12:56, 21 March 2018 (UTC)

Glossary is generating a fatal error in MediaWiki 1.31.0

MediaWiki 1.31.0

PHP	7.1.8 (apache2handler)
MySQL	5.6.34-log

Fatal error: Uncaught Error: Call to undefined function SG\wfProfileIn() in /app/mediawiki/extensions/SemanticGlossary/src/LingoBackendAdapter.php:58 Stack trace: #0 /app/mediawiki/extensions/Lingo/src/LingoParser.php(191): SG\LingoBackendAdapter->next() #1 /app/mediawiki/extensions/Lingo/src/LingoParser.php(163): Lingo\LingoParser->buildLingo() #2 /app/mediawiki/extensions/Lingo/src/LingoParser.php(223): Lingo\LingoParser->getLingoTree() #3 /app/mediawiki/extensions/Lingo/src/LingoParser.php(80): Lingo\LingoParser->realParse(Object(Parser), '

parse(Object(Parser), '

parse('<div class="ale...', Object(Title), Object(ParserOptions), true, true, 26246) #8 /app in /app/mediawiki/extensions/SemanticGlossary/src/LingoBackendAdapter.php on line 58 Legaulph (talk) 12:05, 26 July 2018 (UTC)

If you can, please use master for the moment.

See https://github.com/SemanticMediaWiki/SemanticGlossary/issues/41 F.trott (talk) 14:01, 26 July 2018 (UTC)

Why Thank you, that seems to work fine.

Will I be able to use composer for this version? Legaulph (talk) 14:20, 26 July 2018 (UTC)

Composer should work. You just have to force it to use the master version. F.trott (talk) 14:22, 26 July 2018 (UTC)

MediaWiki 1.32.2 and Composer

First of all, thank you for all the hard work on the extension

Second, without going into any technical detail, I could not get the extension to work and had issues with the instructions for installing the extension, both manually and with Composer. I also don't want to burden you in any fashion by asking for help on solving the issue. I'll get it eventually. Instead I'd like to contribute some updates to the instructions for the manual installation of the extension, not Composer*. But it would be easier if you could help a bit.

Here's the short version of what I did: Semantic Glossary Extension downloaded, loaded in the LocalSettings.php file, permissions, ownership of everything set (no specific instructions given on that).  In the instructions for a manual installation I noticed that Lingo was the only dependency listed, along with the instructions to not load it in the LocalSettings.php file.  Downloaded, installed, not configured in LocalSettings.php, done.  Result: "Fatal exception of type "Error" displayed in the browser afterwards.  I haven't looked into the PHP error log yet, but this error doesn't seem to be at that lower level.  I then tried Composer* per your instructions.  It downloaded and installed 83 dependencys.  That seemed a bit much.  The result was more or less the same as it hosed our entire MediaWiki site.  Thankfully I don't test new extensions or Composer updates on a live site, so no big deal.

Anyway, and again, I don't want to waste your time or have you fix my install, but here are my questions:  Are there issues with MediaWiki 1.32.2?  What are all the dependencies for your Extension?  And do they need to be loaded or not loaded in the LocalSettings.php file?

Thanks...

* I've not had much luck with Composer helping more than it damages.  Maybe someone else can help with expanding the instructions for that for various Composer configurations and other OS installs. Terrawide (talk) 01:07, 28 June 2019 (UTC)

There seems to be an issue with some versions of MediaWiki 1.31 and 1.32 when using Composer. See https://phabricator.wikimedia.org/T226766 .

You could try to use the --no-dev switch with composer or wait for the release of 1.32.3 F.trott (talk) 08:47, 1 July 2019 (UTC)

Please mention SMW is a req on Extension page

It would be nice if you mention that SMW is a requirement on the extension page.

Further, it would be ideal if the extension.json also specifically mentions SWW is a requirement. 138.232.9.101 (talk) 14:37, 14 May 2020 (UTC)

> It would be nice ...

Done

> Further, it would be ideal ...

Once the extension to manifest 2 this will be indeed a thing to. Currently the added requirement for MediaWiki is nothing but dead code. [[kgh]] (talk) 14:51, 14 May 2020 (UTC)

Broken

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Under MW 1.34, SemanticGlossary is broken: PHP Fatal error: Uncaught Error: Call to undefined method ExtensionRegistry::load() in /var/www/wiki/w/extensions/SemanticGlossary/SemanticGlossary.php:29

git pull seems to download an obsolete version of master branch.

The up-to-date version doesn't build (https://travis-ci.org/github/SemanticMediaWiki/SemanticGlossary/builds/690632839).

Alex Mashin (talk) 09:57, 21 June 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Is there a way to turn off the glossary pop-up for a specific term on a page?

I have a button on a page that uses a term from the glossary, but the glossary pop-up is a bit of a nuisance. Is there some magic word/controls that I can place around that word to suppress the popup from appearing? Rwjorgen (talk) 13:46, 9 October 2020 (UTC)

See Extension:Lingo. Semantic Glossary is built on top of that. F.trott (talk) 15:31, 9 October 2020 (UTC)

Magic word "__NOGLOSSARY__" not working on Lingo 3.1.1

__NOGLOSSARY__ tag doesn't work if we use Lingo : 3.1.1 with Semantic Glossary: 3.0.0. Could anyone let me know how can the __NOGLOSSARY__ tag start working with Lingo 3.1.1 165.156.40.27 (talk) 11:36, 18 November 2020 (UTC)

I know this works with MW 1.31.x and does not work with 1.35.x I have only few experience with non LTS versions of MW. [[kgh]] (talk) 14:36, 18 November 2020 (UTC)

I can confirm that this is not working with MW 1.35 Krabina (talk) 11:06, 19 May 2021 (UTC)

filed a bug report here: https://github.com/SemanticMediaWiki/SemanticGlossary/issues/57 Krabina (talk) 11:11, 19 May 2021 (UTC)

popup box does not display correctly

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. Issiegainsley (talk) 14:37, 26 January 2021 (UTC)

I see the lingo extension is no longer maintained. Is this extension still maintained?

Thanks, Issiegainsley (talk) 16:56, 3 February 2021 (UTC)

Everything appears to be configured but no glossary terms are showing

I have installed Semantic Glossary and Lingo and they both show up on my "Version" page as being installed ( MediaWiki 1.36.2, Semantic Glossary 4.0.0, Lingo 3.1.1) and there are no errors showing up in my logs.

I have created a GlossaryTerm template based on the example in the conversation a few posts back:

 
=={{{Term|}}}== 
{{{Definition|}}} 
(link: {{{Link|}}})
<includeonly>
[[Category:Glossary]]
</includeonly>
{{#subobject:
|Glossary-Term={{{Term|}}}
|Glossary-Definition={{{Definition|}}}
|Glossary-Link={{{Link|}}}
}}

Then I have terms that look like this:

 {{GlossaryTerm
 |Term=Project
 |Definition=The organisation of people to deliver something something
 }}

These are pulled into a page for the Glossary category that works correctly.

The problem is that if I have "Project" somewhere in my page, it doesn't get highlighted at all. My best guess is that there is something missing from my LocalSettings.php to tell it that it should be using the Glossary category as a source for glossary terms, but I can't see what I need to be configuring there- all the Lingo configuration seems to be based on quite different assumptions from the Semantic Glossary tooling and the documentation and example page seem to expect this to work correctly first time. Where am I going wrong? Glenatron (talk) 12:05, 13 October 2021 (UTC)

I believe you have been hit by issue 62 :( [[kgh]] (talk) 16:10, 13 October 2021 (UTC)

Thanks for this, I have downgraded MediaWiki and sure enough it seems to work fine. Glenatron (talk) 13:59, 14 October 2021 (UTC)

Interesting that it works for you on 1.35.x I am not lucky enough to get this working on my 1.35. Anyhow, good to know. [[kgh]] (talk) 15:41, 14 October 2021 (UTC)