Chris Roberts

There was a quirk that caused problems with an empty header in a previous version, but I thought I had it fixed with a recent release. I’ll check it again.

Hi mal2809,

You’re right – I don’t check the forums very often, so I’m sorry that I’m just now seeing this. I try to respond to comments on my blog pretty quick, but rarely check the forums.

As to your question (if you’re still interested) – It sounds like you have everything set up right, you just need to use the shortcode. Try inserting the following into a post:
[gs jurassic_info_1]

Added an option at the bottom of the Tippy Settings page to not use the title attribute in the Tippy links.

I’ve debated with the best way to handle the title attribute. For a few reasons (SEO, accessibility, fallback, to name three), it is best to keep it. What I might do is to add an option to the Tippy settings, allowing users to turn it on or off as desired.

A glitch slipped by in 3.6.0. Try 3.6.1 and it should work for you.

Looking into some issues with Tippy and the ESV plugin. Make sure both plugins have been updated and check your Tippy settings. Also, do you have the ESV Plugin set to process references Dynamically or Statically?

Do you have this running on a site somewhere where I could check the errors myself and compare it to your page source? I’m still not sure what’s causing the error but I’ve got a couple of suspicions, just not sure why it’s doing what it’s doing.

It *looks* like your pages have links triggering the tooltip that relies on older code rather than the new link format with the more recent versions. Do you use Tippy tags, or are your links hard coded to trigger the tooltip?

I *may* have figured out a solution. Found another person using 3.3.3 with errors and came up with a fix. In their case it was due to a jQuery conflict. Will be pushing out 3.4.1 shortly. Please try it out when you see it and let me know if it helps with your issue.

I don’t think it’s conflicting with jquery slick menu; I tested the two together and they worked fine.

Would you be comfortable editing the dom_tooltip.js file? I’d like to know what happens if you do the following:

Find the domTip_setPositions function, should be line 83

Add the following inside the function, around line 85:
if (!event)
var event = window.event;

This should make the function look like this:
function domTip_setPositions(domTip_tipElement, event)
{
if (!event)
var event = window.event;

domTip_scrollPageX = jQuery(window).scrollLeft();
domTip_scrollPageY = jQuery(window).scrollTop();

domTip_viewScreenX = jQuery(window).width();
domTip_viewScreenY = jQuery(window).height();

domTip_curPageX = event.clientX + domTip_scrollPageX;
domTip_curPageY = event.clientY + domTip_scrollPageY;

domTip_viewPageX = event.clientX;
domTip_viewPageY = event.clientY;

domTip_tipLinkHeight = jQuery(“#” + domTip_tipElement).height();
domTip_tipLinkX = jQuery(“#” + domTip_tipElement).offset().left;
domTip_tipLinkY = jQuery(“#” + domTip_tipElement).offset().top;
}

As for the other error, “newsruby:213ReferenceError: Can’t find variable: domTip_clearTip” – domTip_clearTip was a function used in older versions of the tooltip to close the tooltip. It is now domTip_fadeTipOut

With 3.3.1 I hadn’t yet made the move to jQuery, so the issue must be related to the use of jQuery. Do you have any jQuery elsewhere in your site, or something changed related to jQuery? Can you look in your browser error console and let me know if it pops up any strange errors? This could help me debug an issue you and others may be having.

Just released 3.3.3 with some changes to how the css file is handled. The plugin comes with dom-tooltip.factory.css. If you want to customize the css, copy that to dom-tooltip.css (which current users will already have) and make edits to dom-tooltip.css. Any changes made to dom-tooltip.factory.css will be overwritten when the plugin is updated, but dom-tooltip.css will no longer be overwritten when updating. Users can update to 3.3.3 without worrying about losing their custom dom-tooltip.css

The plugin will check to see if dom-tooltip.css exists. If so, it uses that file. If not, it falls back on dom-tooltip.factory.css.

valuser, have you had trouble with it? Please let me know of any problems. 3.3.2 introduces some big internal changes and there may be some bugs. Just found one small glitch that will be fixed later when I push out 3.3.4.

Thanks for pointing this out, thought I had fixed this previously. Just released 3.0.5 with this fix.

3.0.4 should fix the issue. Let me know if you continue to have any trouble.

Sorry it isn’t working for you. Are you getting any sort of error? I haven’t had any trouble with the ESV plugin under 2.7. Tippy had an issue with 2.7 and comments but I’ve just resolved it (I hope).

At some point I hope to fiddle with this. Have not had time lately, but I’d like to add special character support.