Viewing 10 replies - 1 through 10 (of 10 total)
  • sounds like a javascript conflict… do you have a link for me ?

    Thread Starter Om Swami

    (@om-vaishnav)

    Sorry But I don’t have a link, Actually I am working on local server.

    If you use FireFox, Opera or Google Chrome browser with any sort of developer toolbar/plugin, you will be able to see what the javascript error console messages tell you… Can you paste any related messages here?

    Thread Starter Om Swami

    (@om-vaishnav)

    Hi now I have a live portfolio here. You can check here and please reply again.
    Thanks

    Apart from the twitter API error, I see no errors in console. ??

    I have no idea what could be happening here and it would be ‘out of my league’ to quickly disect the Cufon script and asses where my highlight script would interfere. Sorry.

    The only advise I can give is either switch off highlighting or use a plain CSS alternative to cufon with any of the fontface kits from https://www.fontsquirrel.com/fontface for example…

    Thread Starter Om Swami

    (@om-vaishnav)

    Thanks for reply, I will disable the highlight plug-in.

    I get this error too – Cufon fonts flash up but it looks like they then go ‘invisible’ when the HLST JS kicks in. I’m guessing that the insertion of the <span class="hilite"> element breaks Cufon’s ability to manipulate the DOM?

    Heh. Just tried a quick fix. Whack Cufon.refresh(); in just before the end of the jQuery document.ready function – i.e. before the last })); in both compressed and uncompressed versions of the plugin’s JS file.

    Will try to contact plugin author too, but hope this helps…

    Cheers,

    divydovy

    David, thanks for sharing your findings ??

    One question: because throwing in Cufon.refresh(); for anyone without the cufon script running, will trigger an Uncaught exception error, could you tell me if the following code works as I suppose is should with cufon loaded:
    if ('function'==typeof Cufon) Cufon.refresh();

    If so, it will be in the next version…

    Hi RavanH,

    Thanks for your engagement.

    Yes, your ‘if’ condition works. I’ve tested it both with and without Cufon being loaded and I get no errors either way.

    A really useful extension to this (by someone cleverer than me) would be to add the ability for the HLST’s that appear IN Cufonised text to have the highlight too. I’ve tried (quickly) adding a CSS class and/or a Cufon background colour statement, but with no success.

    So, in the meantime, this solution will work fine as long as you’re not using Cufon for titles of search results. In this case I am, so I guess I’ll just give the client the choice of whether to forgo highlights in titles, or forgo Cufon entry-title’s for the search loop.

    Cheers,

    divydovy

    And thank you for your insight and testing ??

    It surprises me the Cufonised text does not keep the span class with its background color… I thought styling like background and font size/color and line-height was compatible with Cufonised text?

    Apparently, the span wrapping the search term inside the head tag first breaks Cufon and then gets stripped out upon Cufon.refresh()…

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Plugin: Highlight Search Terms] This plug-in create problem with cufon font replacement’ is closed to new replies.