WordPress.org

Support

Support » Plugins and Hacks » Tippy » A Couple Suggestions

A Couple Suggestions

  • First, thanks for this awesome plugin, it’s super helpful in certain situations!

    I wanted to offer a couple suggestions. 1) either set the cursor to cursor:help when hovering over a tippy link, or give us an easy option to do so. 2) Create a box in the settings that allows us to input custom CSS for the plugin that won’t be overridden when updating the plugin (this would also solve #1). So we can set things like font, color, etc right in the plugin settings, and it would be preserved with each update (assuming the CSS was the same in the update–but even then we’d still know how we wanted it, just have to find the new class/id/etc.)

    Just some ideas. Thanks again for the awesome plugin, whether you implement the suggestions or not.

Viewing 13 replies - 1 through 13 (of 13 total)
  • similar sentiments re css & gratitude. A Gem.

    but does v.3.3.2 work ?

    Plugin Author Chris Roberts

    @columcille

    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.

    First. It is a class plugin. Thanks.

    3.3.1 All well.

    tried 3.3.2 and 3.3.3 but on hover (which was the configuration) does not appear to function. gone back to 3.3.1 for the time being.

    No worries as i am only trying things out.

    It could well be something I’m doing that can’t work with the higher versions.

    Plugin Author Chris Roberts

    @columcille

    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.

    Sorry. am using Version: 3.2.0. which works.

    i also have running jQuery Slick Menu ??????

    will install latest version and report back.

    ok (on local site-Safari) – disabled jquery slick menu- installed your 3.4- no change

    errors

    NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7: An attempt was made to modify an object where modifications are not allowed. FB.Share:6
    dom_tooltip.js:91TypeError: Result of expression ‘event’ [undefined] is not an object.
    newsruby:213ReferenceError: Can’t find variable: domTip_clearTip
    dom_tooltip.js:91TypeError: Result of expression ‘event’ [undefined] is not an object.
    newsruby:213ReferenceError: Can’t find variable: domTip_clearTip
    dom_tooltip.js:91TypeError: Result of expression ‘event’ [undefined] is not an object.
    newsruby:213ReferenceError: Can’t find variable: domTip_clearTip

    hope this helps

    Plugin Author Chris Roberts

    @columcille

    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

    ok. I’m afraid there is no change.

    I did it two ways as i actually don’t have a clue.

    1) i replaced what was there with what you gave me. no change

    2) i added (as requested) what was there to what you gave me ie

    function domTip_setPositions(domTip_tipElement, event)
    {
    if (!event)
    var event = window.event;
    etc

    }

    then

    {
    domTip_scrollPageX = jQuery(window).scrollLeft();
    etc

    }

    no change. anyway

    Plugin Author Chris Roberts

    @columcille

    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.

    no joy (for me) i’m afraid with 3.4.1.

    Wonder if other users are affected ? If not, i’m ok with 3.2.

    errors:

    FB.Share:6 NO_MODIFICATION_ALLOWED_ERR: DOM Exception 7: An attempt was made to modify an object where modifications are not allowed.
    dom_tooltip.js:103TypeError: Result of expression ‘domTip_jQuery(“#” + domTip_tipElement).offset()’ [null] is not an object.
    newsruby:233ReferenceError: Can’t find variable: domTip_clearTip
    dom_tooltip.js:103TypeError: Result of expression ‘domTip_jQuery(“#” + domTip_tipElement).offset()’ [null] is not an object.
    newsruby:233ReferenceError: Can’t find variable: domTip_clearTip
    dom_tooltip.js:103TypeError: Result of expression ‘domTip_jQuery(“#” + domTip_tipElement).offset()’ [null] is not an object.
    newsruby:233ReferenceError: Can’t find variable: domTip_clearTip

    Plugin Author Chris Roberts

    @columcille

    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?

    trial site at http://danny.de-nws.com/

    hard coded into header.php see “Why join ?”

    excuse delay!

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘A Couple Suggestions’ is closed to new replies.
Skip to toolbar