Categories
Package/plugin/module WordPress

Text Hover v2.0

I’d like to announce the official release of the updated Text Hover plugin (v2.0) for WordPress.

Add hover text to regular text in posts. Handy for providing explanations of names, terms, phrases, and acronyms mentioned in your blog.

This release encapsulates all of the plugin code in its own class, which includes the addition of updated internal plugin management code. This release is fully compatible with WordPress through v2.8+, but support has been dropped for versions of WordPress older than v2.6.

The plugin’s official homepage is located at :
coffee2code.com/wp-plugins/text-hover.

Comments welcome on this post for this version of the plugin. Comments will be closed once this release has been superseded by another.

Read more for a detailed ChangeLog of the release.

Detailed ChangeLog

These are the detailed changes, which may or may not make sense to you depending on your familiarity with the previous features and internals of the plugin.

  • Encapsulated all functionality into its own class
  • Added ‘Settings’ link for plugin on admin Plugins page
  • Updated copyright date
  • Noted compatibility through 2.8+
  • Dropped compatibility with versions of WP older than 2.6
  • Updated screenshots

16 replies on “Text Hover v2.0”

Thanks for this very nice plugin.
Sorry to disturb with one question: in French we have a lot of ” ‘ ” in front of the words (l’ or d’ replacing “the” or “of” if first letter is a vowel). I tried to add the equivalent of “'” in the special characters, but can’t make it work properly.
for example “L’AFD” should hover “Agence française de développement”
Can you help by providing the code lines to change?
Best regards,
Myrtille

Actually, what you want already works. The problem most likely has to do with the nature of the “‘” character. The character has a non-curly version and a curly-version. They are essentially different characters. Go back into the the plugin’s settings page and paste over the “‘” with the curly version (in your comment above, that’s the curly version) and save the settings. Then reload a page containing “L’AFD” and see if it works. (If the settings actually had the curly quote version, then delete it and type the character in, which should then be the non-curly version.)

Thanks for the quick answer. But maybe I wasn’t clear enought (sorry for my English). If I write in the settings:
L’AFD=>L’Agence française de développement
it works perfectly.
My problem is that I want to enter in the settings only:
AFD=>Agence française de développement
which doesn’t work, supposedly because of the “l'” in front of it (not considered as a space or equivalent), so AFD is not considered as a word. Am I right? Is it possible somewhere in the code to add “L'”, “l'” and “d'” as space-equivalents, so that I don’t have to type 4 versions for every word in the settings? (right now I have to type hovers for “AFD”, “l’AFD”, “L’AFD” and “d’AFD”)

Good news: beta version works perfectly.
Bad news (for me): doesn’t solve my problem. Maybe if you see the site it can help? (Sorry it’s still in progress… due in september)
www.marches-tropicaux.com/blog/
In the first post (“Le Bénin se voit en exportateur de riz”), “FAO” txt hover is ok, but in “l’ONU” (“the UN” in French), it doesn’t display.
My settings:
ONU => Organisation des Nations unies
Onu => Organisation des Nations unies

Myrtille: Please re-obtain the plugin file from the repository link I mentioned in my last comment. I have updated it to version 2.1-beta2. I modified the character matching code to make it more versatile in recognizing single and double quotes, which I think is the issue you are encountering. Let me know how it goes!

Hy,
thanks for this wonderful plugin; I’ve searched for a glossary plugin and found this for the best solution.
Unfortunately, I need my tooltips to be formatted. Is there any way to show the tooltips as css objects or something like this so html use is possible?
Thank you!

I’ve discovered an interesting “feature”. The Text Hover inserted the <acronym> into a url link in my post and broke the post half way through. I have had to turn off the plugin, which otherwise seemed very nice.

Here’s what the part that broke the page looked like. If you can get it to not do this sort of thing, I’d really love to use the plugin. I hate having to explain what a dietary vegan is or a pescetarian is what IgAN is all the time…or words I’ve actually made up.


I am ready <a title="The Eat <acronym title='A person whose diet excludes animal flesh, animal products, and possibly honey; his or her lifestyle also excludes the wearing and use of animal products.'>Vegan</acronym> Experiment” href=”http://alternative-me.com/the-eat-vegan-experiment/”>to commit to 365 days of eating vegan</a> — no dairy, no eggs, nothing made with animal by-products.  The fun for you will be in reading about my adventures in adjusting — shopping for ingredients I’ve never heard of, eating out in restraunts and trying to order something other than salad,  finding soymilk chocolate, vegan cooking without butter spray, etc.

And much more…

Very weird stuff going on….

I’ve been using Text Hover for a few months now with no problems. I have the most recent version on the most recent version of WordPress.

Today, I added a definition as follows:
R22 => a 2-place helicopter manufactured by Robinson Helicopter Company in Torrance, CA

A post using “R22” broke before the use of R22 in the post and resumed near the end. I’ve since removed the entry to restore the post as it was. Any idea why this might be happening? The same post uses the definied acronym CFI and works fine.

The post in question can be found here: www.marialanger.com/2009/08/09/lazy-shopping-for-a-helicopter/

Wait a sec…just realized that “r22” was used in a link in the same post, near the beginning. Maybe it’s the same problem J.Lynne was reporting? If so, I’ll just wait for v2.1. Thanks.

Maria: You’re probably right about that; most likely the “r22” in the link was being replaced by Text Hover when it shouldn’t have been, breaking the post. I just released v2.2 of the plugin, which should fix that.

J. Lynne: As I just mentioned, your probably should now be fixed as well with the v2.2 release of the plugin.