1. 

   Eric Johnson
   Member

   All Glossary Terms need to be EXACTLY the same in the article as they are in the glossary.

   If i have "Toner" in the glossary, it doesnt pick up "toner" in the articles. Is it possible to make it so that capitalisation doesnt get recognised?

   Posted 10 months ago #
2. 

   systemAdmin
   Member

   Open the file "includes\application\models\article_model.php" and at line 506 replace

   $content = preg_replace('/[\b|\s]('.$row->g_term.')[\b|^\s]/', $replacement, $content, 1);

   with
   

   $content = preg_replace('/[\b|\s]('.$row->g_term.')[\b|^\s]/i', $replacement, $content, 1);

   Basically just add the i modifier to the end of the regular expression to make it case insensitive. Not tested, but I believe that should do it.

   Posted 10 months ago #
3. 

   kenmcneill
   Member

   Are my eyes deceiving me, or are those two lines identical?

   Posted 8 months ago #
4. 

   Eric Barnes
   Moderator

   They are different. :) Have to look VERY closely.
   [\b|^\s]/i

   Posted 8 months ago #
5. 

   kenmcneill
   Member

   Now I feel like a dolt. I was going by what was visible in my browser and didn't realize there was more.

   Looking at the file now, it looks like this has been changed in the current version. I did a search for the original line and found nothing.(?)

   Is the glossary still case sensitive?

   Posted 8 months ago #
6. 

   Eric Barnes
   Moderator

   It appears it is not set to lowercase in the latest release.

   Look in that same file and find the function glossary($content)

   In that function you should see $content = preg_replace......

   That is the line to replace.

   Posted 8 months ago #
7. 

   JohnFerrell
   Member

   I noticed that if the Glossary term is the first word in the content section of an Article, it is not identified as a Glossary term. In addtion, if the glossary term is next to puctuation such as a comma, it is not picked up as a glossary term either. I assume the term must be surrounded by white space?

   Posted 8 months ago #
8. 

   Eric Barnes
   Moderator

   Yes it has to be a single word. Here is an example. Let's say your term is "cat" then in the article you have cataract it would find the cat in that term.

   Posted 8 months ago #
9. 

   JohnFerrell
   Member

   I realize "cateract" is not a match for "cat" but would think that "cat," would be. For example, "I have several pets: a cat, a dog, and a goldfish." I would think that in this example, "cat" should be highlighted or identified as a glossary term. In addition, if my term is "XYZ" and my Article starts with "XYZ is a new widget.", I would think that this, too should be highlighted as a glossary term. In both cases, it is not. There should be a distiction between alpha characters and puctuation characters with regards to identifying a glossary term. Starting an article content with a glossary term should also not be a limiting 'feature'.

   Posted 8 months ago #
10. 

    FredL
    Member

    I confirm the word has to be separated with spaces to get picked-up as a glossary term.
    In addition, when it is at the end of a line I have to add a </div><div> after it, otherwise the ending space get suppressed.

    Posted 8 months ago #
11. 

    FredL
    Member

    But I didn't understand a thing regarding the way to make it non-case sensitive.
    Could someone sumarize?
    Thanks

    Posted 8 months ago #
12. 

    Eric Barnes
    Moderator

    Basically just follow the steps "systemAdmin" posted above. This is also committed to the trunk and will be included in the next release.

    Posted 8 months ago #

RSS feed for this topic

Reply

You must log in to post.