Eugenio Petulla'

You are welcome,
If you are happy with the plugin please consider to leave a vote on the plugin’s page.

??

what @mte90 said is valid!

We don’t support RTL langauages yet, but we are working on it. I’m sorry but when I started writing the plugin I completely forgot the RTL language support, it’s my fault! T.T

• This reply was modified 8 years, 1 month ago by Eugenio Petulla'.

Hi @hilash ,

the plugin is pretty simple and self-explanatory so you don’t need a documentation for use it. Just activate it, go to the setting page and choose where to activate the auto-link engine, choose if you want tooltips or not and the template you want for them.

Start creating your glossary terms like you create a normal post or page and choose if you want link them also to different terms from the title (related). It’s pretty simple and straight forward and you can see a demo here: https://codeat.co/glossary/glossary/

We are plannig to write a little documentation in some weeks but at moment you can ask to us everything specific you need opening another support ticket here or on github.

There is a way, simply put the term between a span tag using the text editor functionality of WordPress. Follow this example:

Bank = Parsed, so you have the tooltip

<span>Bank</span> = No parse

No shortcodes or other stuff required. ??

It’s a tweak and it will work also in your specific case:

<span>Bank</span>er

Otherwise I’m trying to resolve the issue at the bottom level of the problem, unicode chars, so keep following this thread. ??

Thank you for the link, it was very helpful. I’m working on the solution today. Keep following this thread and I will notify you when everything is ready! ??

Actually is very difficoult to me understand the problem because of the language (is it Hebrew, right?) but I’m working on a tweak that could help avoid situation like this. If you can do some test for me I will appreciate it a lot! ??

Try to edit line 191 of the public/includes/Glossary_Tooltip_Engine.php file. Delete this part \:\;\*\"\)\!\?\/\%\$\￡\|\^\<\> and save, than tell me if something change. ??

If it will resolve your issue we can add a special option into the settings panel. ??

No responses, I think we can mark this as resolved!

Hi @vebmayster, thank you for the support! ??

I resolved this issue some release ago. Did you upgraded your plugin to the last version?

We’ve got the term “code” in our glossary and it doesn’t shows up into words like “coders” or “decode”.

Take a look at our demo site here: https://codeat.co/glossary/hello-world/

and the term here: https://codeat.co/glossary/glossary/code/

If your plugin is at the last version maybe is better than you post us a link of the issue on your blog because in the regular expression we use there is a rule that looks for a space or a special char before the term and if there aren’t the match doesn’t occur. ??

Just wite your terms and choose where they have to match from the Glossary Setting Page. Automatically they will be linked for every occourrence of the term.

This plugin doesn’t need so much configuration. Take a look at this page in your Dashboard: https://s31.postimg.org/4pcpepbaj/Schermata_da_2016_06_26_12_06_19.png

??

This is totally insane! XD

Something is altering the standard wordpress loop, our plugin’s archive is totally standard… do you have a Genesis child theme maybe? Did you tried to switch your theme with a twenty-something? This could be a theme issue maybe. Give it a try! ??

I’m following this thread as Glossary Plugin’s author. I tryed to debug on my side but it’doesn’t seems to be our fault so I’m curious about this now! ??

Sorry for the delay in my reply.

I did a lot of tests of this situation, now I added the term code and coding into the Demo site and it works as expected. I really don’t understand how it could happen in your website.

Are the map pins a separate custom post type?

If you want investigate more maybe is better to move this discussion on GitHub, here: https://github.com/CodeAtCode/Glossary

Actually I can’t reproduce the issue, in our Regex there is a check for this (keywords in links) and it’s working in our demo site. I’m not able to figure out why it is not working for your map system!

Search for the TEST word in the following page, there is a link that is using the keyword “blog” inside itself and it’s working without issues: https://codeat.co/glossary/hello-world/

Maybe your problem is not related to our plugin, I’m looking at the way you are rendering the pins on the map and it’s a little weird to me, because this map puts html tags into a html data attribute. It’s completely out of any coding standards so it’s very hard to debug for us. Sorry but I have to say: this is a wontfix for me T.T

Dear someonehere15 we appreciated every kind of feedback if it’s a good starting point for a productive discussion, so don’t apologize to us ??

We are working for a new major realease, starting from other users’ feedbacks. I want to ask something to you because I’m thinking about it since a lot of feature request started to arrive from github and this support forum.

I want to give a small customizer to user in order to personalize every aspect of tooltips but it will became a nightmare for us to give support to it for free (I’m thinking about every theme is out there, also outdated and not responsive at all. T.T ). If we built a paid addon (something like 9 USD/Year) for direct support (also for feature request) plus a complete customizer, are you willing to pay the “pro” version?

However, we are working on the issue you reported and we will introduce them in the next major release (1.1.0), so keep tracking our plugin. ??

I’m working on this feature like a shortcode (as Daniele said) but it will be included into the next major release (1.1.0) that will be released as soon as possible.:)