Glossary Terms NOT working on posts

First of all, it seems that two things reported here are not related to each other, so let’s treat them separately

@asolis11 – unfortunately we were not able to reproduce your issue. We copied your content to https://dev1.cminds.com/acne/ but, as you can see, all terms are highlighted correctly. They don’t contain any special characters, so the issue is really mysterious. Which editor do you use to insert your content? Is it default tinyMce or ckEditor or pure HTML editor? Do you type text in this editor or you copy/paste from somewhere?

@ryanlorem – Same question to you – which editor do you use in WordPress? We found that tinymce and ckeditor handle special characters differently and the source is different.
On your page, text: “BUYER’S AGREEMENT” and “CC&RS” is encoded as (spaces added because forum is stripping entities):
BUYER’S AGREEMENT, CC& #038;RS
On cminds.com, the same text is encoded as:
BUYER& #8217;S AGREEMENT, CC& amp;RS
And on my local machine it looks like this:
BUYER& #39;S AGREEMENT, CC& amp;RS
We need to find the common denominator

Oh boy, that sucks for me. I make my own content no C/P and yes I have installed tinyMce and when I C/P anything from the web I do it using the Text tab instead of the Visual as that brings up unwanted characters or calls like <div> <tables> etc….
What will be your suggestion for me to try if you have any CM?

thanks once again for spending your time with us.

I’m using the default text editor (html editor). I have just tested in a sandbox area using the Twenty Twelve theme in WordPress 3.5.1 with all other plugins deactivated. The link does not work yet.

The DOM source show it as: BUYER’S AGREEMENT

Is it possible that this is a server side issue?

Here are some specs. Let me know if there is a setting to look for in phpinfo().

x86_64 x86_64 x86_64 GNU/Linux
CloudLinux Server release 5.9 (Sergey Oleynikov)
PHP Version 5.3.19
default_charset: no value
CharConv: No
mbstring.substitute_character: No value
session.hash_bits_per_character: 4
HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.3
_SERVER["HTTP_ACCEPT_CHARSET"]: ISO-8859-1,utf-8;q=0.7,*;q=0.3
_ENV["HTTP_ACCEPT_CHARSET"]: ISO-8859-1,utf-8;q=0.7,*;q=0.3

We released 2.0.5, please let us know if this made the desired change.

well at least for my case on the old posts like the one I put here for sample still NOT working correctly but for every new posts I make it seen to be working perfectly which is good for me. I will try to delete the old posts and re-post back again and see if that helps.

It is now working for me.

I did have to go through and make sure any terms which include apostrophe are using a vertical typewriter apostrophe (') in both the title of the glossary item and the pages which include the term. The closing single quote (’) was still breaking it.

You can see everything working on this test page:
https://dreamloan.pro/glossary-terms-check-hover-items/

Thanks a lot CM. Let me know if you need anything else tested.

Good to hear, we will add the The closing single quote (’) to the next release but seems that most of the big issues are behind us ??