Chris Roberts

Copy the file itself to your theme folder. If Tippy sees it in your theme folder, it will use that one rather than the one that came with the plugin.

As for adding the rule to your theme’s stylesheet, make sure the rule is more specific than the default rule so the browser knows which set of rules to follow. Something as simple as “body .tippy_header” should do it. Look up CSS specificity to learn more about what’s going on.

What data do you wish to insert that you cannot insert? Does it not work or is it just lacking a feature you wish it had?

Don’t think I see the effect you’re describing. The tooltip scrolls under the menubar when the bar is fixed at the top, which seems like it would be the desired behavior. I’m looking at it in the latest Chrome.

Do you have a caching plugin installed? Those often display the cached version of a site when not logged in. Try clearing the cache and see if it works after that.

I’ve been pretty busy lately and supporting the plugin hasn’t been able to be as high a priority, but I’ll try to make some time later today to figure out the issue.

Here’s what’s happening. The actual tooltips go into the markup at the end of a post rather than where you place the tippy shortcode. I did it this way because of issues with some nested block-level elements (in particular, a div inside a paragraph tag). The tooltip is set position: absolute and positioned accordingly. This means its parent element (usually .entry) needs to be position: relative. This often works fine, but there can be a problem if the tooltip link is inside a position: relative element.

In your case, your tooltip links are inside your .grid elements. When the jQuery code calculates the link’s position (in order to know where to place the tooltip), positions are calculated relative to .grid rather than .entry, since .grid is the closest relative element. This is why the tooltips are showing way too high: position is being calculated on a much smaller scale than it should be.

Two ways to handle this:

Remove relative position from .grid. This would be the easiest approach and if you don’t need those grid blocks position relative, that’s what I’d recommend.

It’s also possible to tell Tippy to use a different container when displaying the tooltip. This one takes extra work and still might not work quite right (if you want to try it, try it for just one tooltip and see how it does). Every div containing a tooltip would need either a unique id or a unique classname. You might call the first one something like <div id=”essentieeldocumenten” class=”grid one-fourth”> Then in the tippy tooltip itself, add a container attribute: [tippy title=”I’m a tooltip” container=”#essentieeldocumenten” This way, the tooltip will be displayed relative to the specified container rather than where it’s initially placed in the markup.

I see what it’s doing, but I’m getting rusty on my own plugins so I’m having to think back to the best way to address it.

One thing you can try: in your dashboard Tippy settings, look for the Calculate Position option, the last one on the right column, and change it to “Relative to the document” and see if that does it.

I’m not doing much with the ESV Plugin anymore (most people nowadays are using the Reftagger plugin) but do you have this at a url where I can take a look and see what it’s doing?

mungle, try putting it in child-theme/jquery.tippy.css rather than in the plugin folder. I haven’t tested with child themes, so that still might not work.

Strange, nothing between them should collide but from what you tried it sounds like they are. Are you able to check your JavaScript console to see if it’s tossing out any errors, or can you paste a url where I can look at it myself?

That option is not available at this time. Multi-slider remains pretty low key.

You can access all previous versions of Tippy through the WordPress repository. We’re on 6.2 now, are you looking for the last one in the 5.x series? The link is https://downloads.www.ads-software.com/plugin/tippy.5.3.2.zip you can find links to all other versions at https://www.ads-software.com/plugins/tippy/developers/

On your message, I’m afraid it didn’t come through. I use the Contact Form 7 plugin for the contact page and several people have been having trouble with that plugin lately, I need to find a workaround for the problem. In the meantime, you can email me directly at [email protected]

On your error: that’s not something that Tippy would generate. It sounds like it hit a problem while updating. Tippy shouldn’t interfere with that at all.

I’ve just set up a small multisite install and tested out Tippy and didn’t see any issues. This is my first time to even touch multisite so there may be significant differences with the different setups, but I don’t see any reason why Tippy wouldn’t work on any given setup and don’t know why it would have any trouble with multisite. It certainly wouldn’t cause an issue when upgrading WordPress, which is what your error is showing.

As for going back a version, do you mean with Tippy or with WordPress? It is possible to downgrade either one, but going back with WordPress is difficult, especially if it’s already upgraded your database.

So you want your button to trigger the tooltip popup? Interesting idea. ?? I’ve just added an attribute to Tippy, alttrigger, which can be used to set an alternate trigger link. In Tippy you would add something like alttrigger=”.trigger_audio” then your link would need the class trigger_audio – anything with that class will trigger the tooltip. It will respond to hover or click depending on which one you specify globally or per-tooltip.

Look for this in Tippy 6.2.0 which I should release tonight.

There is no commercial version, but I’ll take a look tonight and see if I can figure out the multisite issue.