Glossary operator

Author Message

Patrice DUCLAUD

Wednesday 20 September 2006 12:00:51 am

ezpublish 3.6.11 .
I've make the install of the glossary operator extention and it's seems to be ok in ezpublish. the extention is active.
I try to use it but i have no result. I look for in forum and try to implement some code in template but nothing append.
I'm sure I've missed something, but why ?

Is this extention works fine with new version of ezpublish ?
Is there any documentation, example of use ? The docs in the extention allow me to understand what it can do (i believe), but i'm not able to use it now ;-((

Is there somebody who can give me some help to understand how to use this extention.

Thanks,

Patrice

Claudia Kosny

Wednesday 20 September 2006 1:02:42 pm

Hello Patrice

we need a bit more information to be able to help you.
First I am not sure what you mean by 'new version of EZ'. The current version is 3.8.4 which is a long way from 3.6.11. So what version do you use?

Regarding the problem itself:
- Give us a bit of code where you try to use the glossary.
- Do you get any error messages in the debug output?

Greetings from Luxembourg

Claudia

Patrice DUCLAUD

Thursday 21 September 2006 8:25:28 am

Hello Claudia,

Thanks for your reply,

I use ezpublish 3.6.11 (the upgrade from 3.6.* to 3.8.* will be realised in few month).

What i've done :
Copy the "glossary extension package" in the "extension" directory of my website (test).
Add this to site.ini.append(.php) in the override directory (settings/override)
[ExtensionSettings]
ActiveExtensions[]=glossary

The extension is active in admin of my website.

I've created an ovveride of
design/MySite/override/templates/content/datatype/view/ezxmltags/paragraph.tpl
with the following code :

<p>
{$content|glossary(false,109,replace,normal)}
</p>

109 is the node_id of a folder named TheGlossary in my website tree.

and now ... what must i do ?

No error messages in the debug output.

Sorry not to be able to give you more good information.
In What TheGlossary folder consist of ? a folder where glossary function put keywords and links to articles or something like that ? I'm not sure to understand how this extension works and therefor it's difficult to speak about .

I walk in the dark .... and no ligth to know where i must go ...

Patrice

Marco Zinn

Thursday 21 September 2006 2:01:35 pm

Hi there,
i had tried the glossary operator some months ago and it worked fine. I'm referring to Hans' "Updated Glossary Operator" (http://ez.no/community/contribs/template_plugins/updated_glossary_operator ) and i had tried this with ez 3.4
You will need a place (folder), where you have to store the words and descriptions of your glossary terms. You can use any class for this, for example, an article.
So, you'll have a folder with 50 articles, each of which defines one term of your glossary. The name of each article must be the word, that you describe.

Now, you have your glossary. In order to use it, run the operator on some text/XML; your example lookes fine to me.
Now, the operator has at least 2 Modes: One "Search and Replace", where each (or only the first) occurance of any word, that exists in your glossary (see above) will be linked to the glossary term. You would just output the result of that operation on the screen/in the template.
The second mode will not return some printable HTML, but an array with information (an array) about those glossary words, that were found in the input text. You can then use some template code ("section loop") to loop over the returned array and print the words (with links to each glossary term) below the article, for example.

I hope, this will help you a bit.

Marco
http://www.hyperroad-design.com

Patrice DUCLAUD

Friday 22 September 2006 1:01:17 am

Thanks for your reply Marco,

Today is a good day, Now I understand how glossary operator works and everythings is good for me. It was just a problem of understanding.

Thanks.

Patrice

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.