Extension talk:Semantic Glossary/Flow

Previous page history was archived for backup purposes at Extension talk:Semantic Glossary/LQT Archive 1 on 2015-07-10.

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?

I believe you have been hit by issue 62 :(

Thanks for this, I have downgraded MediaWiki and sure enough it seems to work fine.

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.

__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

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.

I can confirm that this is not working with MW 1.35

filed a bug report here: https://github.com/SemanticMediaWiki/SemanticGlossary/issues/57

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.

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

Thanks,

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?

See Extension:Lingo. Semantic Glossary is built on top of that.

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

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

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

Have some solution to use synonymous in Semantic Glossary?

Tracked with GitHub issue 47

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)

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.

> 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.

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.

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?

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.

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.

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.

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}}

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.

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

Many thanks,

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. :)

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.

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

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('

If you can, please use master for the moment.

See https://github.com/SemanticMediaWiki/SemanticGlossary/issues/41

Why Thank you, that seems to work fine. 
Will I be able to use composer for this version?

Composer should work. You just have to force it to use the master version.