tzdk

Site is known? Is not known to any blacklist, including WOT http://www.mywot.com/en/scorecard/simplewpthemes.com How about changing that? Not really a good idea to remove link. Has no effect but reporting can have, the more the better.

I have done Google http://www.google.com/safebrowsing/report_badware/

Partly pissing in the pants but very annoying for such sites and it should also be annoying to see them all “Clean” and green. As you can see from the 1 comment on WOT “they” are aware. And WOT is gamed – hence pissing reference. But battle is on…

Well I was also telling you to look the wrong place, heh

/wp-content/lightbox-plus/css/fancypants/helper.js

“/plugins/” should be put in there.

Change duration from 0 to 1/1000sec. in helper.js – or that works for me. Seems like some weird jquery workarounds dev. need to look at. 1/1000sec make no sense but take away the blinking. Anything but zero.

You have already moved styles to custom folder so easy for you to change last 0 to 1 or above. Is last part with “Show close button with a delay” comment.

jQuery(document).ready(function($){

    $(document).bind('cbox_open', function () {
        // Hide close button initially.
        $('#cboxClose').css('opacity', 0);
    });
    $(document).bind('cbox_load', function () {
        // Hide close button. (It doesn't handle the load animation well.)
        $('#cboxClose').css('opacity', 0);
    });
    $(document).bind('cbox_complete', function () {
        // Show close button with a delay. So he says but 0 is not much of a delay! 0 = disable duration. 1/1000sec is better.
        $('#cboxClose').fadeTo('fast', 1, function () {$(this).css('opacity', 1)});
    });
});

I hope you can reproduce fix. But dont click resolved if you can do that. Dev. needs to see this I think.

.fadeTo doc http://api.jquery.com/fadeTo/

This thread is going places 🙂

Your problem is this http://cdn.designfather.com/wp-content/themes/open/js/jquery.tools.min.js Name hints file consist of jQuery.tools stuff and it does but oops, also includes jQuery 1.3.2 and then all bets are off. You can see in JS error console that Lightbox Plus think jQuery is 1.3.2 and so its .delegate http://api.jquery.com/delegate/ does not compute as it was added in 1.4.2

Also has some “jquery.event.wheel.js” thing. Besides of course jQuery tools script. That is another jQuery library thing used for tabs etc.

I see theme is from Themeforest so you should be able to contact dev. and ask for a fix? You cant because he removed theme? (I cant find it!) Well, then find another. May be from someone who updates their premium stuff? Idea of bundling is pretty good as an optimizing tweak, less http request, but not for mission critical scripts like this. No need to say jQuery 1.8.3 is ALSO loading. This bundle script is not identified or can act as a genuine jQuery = mess. And besides it is dirt old and probably wont work with lots of newer plugins, Lightbox Plus is one of them.

If you can fiddle with theme code you can fix this with no dev. Brute force is simply to edit out the ancient jQuery. That would be hmm the first 2 lines under

* File generated: Fri Sep 18 05:25:32 EDT 2009

both starting with

(function()

Next problem could be jQuery tools as that is also very old. http://jquerytools.org/release-notes/version-1.1.1.html from 2009 so if compatible with jQuery 1.8.3 or not I dont know.

If I am not blind and dev. really has removed theme you cant re-download it so make backup before doing anything. And perhaps start looking for new theme. Since this is crazy outdated other things probably are less than great. Time to die…

Dev is still selling there http://themeforest.net/user/Maximus/portfolio so you can always ask if he can help. Oh, they have own forum and there is one for “Open” theme http://support.themedemo.net/forum/open

You have a plugin forcing latest jQuery 1.9 from Google CDN.

http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js?ver=2.4.5

Not wise as it does it in a stupid way, caching is hosed with “/1/”, but with jQuery 1.9 it has become critical as a migrate.js script is required to fix incompatible scripts. You do not load that so this can cause issues. The plugin forcing jQuery load has no clue of jQuery 1.9 and the almost required migrate.js file. Dev. thought he/she was smart using “/1/” as then latest version would always load. Nope not smart! Tons of scripts are not 1.9 compatible. Is only a little trick for devs., should not be in released plugin.

http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-final-released/

Load both if on 1.9 and then check error console which will tell you when jquery-migrate-1.0.0.js is working = saving you from broken scripts.

If relevant for this popping up issue I dont know but very likely will be for what ever else you run. I dont know how bleeding edge Lightbox dev. is but you probably should do testing on the version coming with WordPress 3.5 – that would be 1.8.3

Works fine for me on jQuery 1.9 but JS can act up in mysterious ways. You definitely will want migrate.js script if not very much on top of jQuery issues.

I am not developer but CSS comes from Colorbox not this WP plugin. http://www.jacklmoore.com/colorbox

Well as said I would use CSS-Lint for CSS. Or try check/validate HTML5 BoilerPlate, Twitter Bootstrap or similar “authority” things and you will probably get in to a spin of who to guide you. Those validator services are not supreme court, or necessarily updated! = not relevant with everything. CSS Lint is updated, over and over. Not even sure about how updated as I think they still insist on IE10 prefixes which have been deprecated since last summer! And IE9 dont even know them so what is the point? Site is ultra conservative I think. ColorZilla also still use them. Dont believe all you see on internet. “Lots of stuff need updating” http://www.impressivewebs.com/dropping-ms-vendor-prefixes-ie10/ sure, in 1 year or so…. Until then you can say “invalid” all day long 🙂

Apparently CSS Lint call red alert for the old IE6 hack I mentioned, _behavior, but if used like that to avoid issues with normal browsers it make sense even if invalid. Using a body/hmtl class would be better and probably why they declare “parsing error” or stupid hack.

I actually dont use the plugin right now but have before and then I deregistered themes. Copied CSS to other file and removed stuff, like the IE6 chuncks. Nothing stops you from doing that. I am also pedantic with correctness – and hate fluff and more http requests than necessary. Speed is also a parameter.

Choose a theme, lets say no. 3. Then you have that + 1 CSS file the Zoom part to get rid of.

add_action ('wp_enqueue_scripts', 'dropColorboxCSS');
function dropColorboxCSS() {
wp_deregister_style('colorbox-css'); // jquery-colorbox-zoom.css file
wp_deregister_style('colorbox-theme3'); // colorbox.css in theme3 folder
}

One thing to remember is the /images/ folder under each theme. 3, or at the very least 3, calls to those files will need to be changed in your own CSS file. Change to absolute path or relative to own CSS file/folder.

Also in other folder where jquery-colorbox-zoom.css is you see

background: url("../images/zoom.png") no-repeat scroll 50% 50% transparent;

So it will look for /images/ folder 1 level higher up. Wont match your own CSS so have to change path and/or placement of those images. Besides this it totally works and you can change/improve what you like.

This info you can get out of /jquery-colorbox/includes/jquery-colorbox-frontend.php file. I think he use some variable for theme number but if you want no. 5 just change number in above snippet.

Is probably because this plugin recently updated Colorbox script and that one is not compatible with your 3 year old WP install 🙂

http://www.jacklmoore.com/colorbox

Current version: 1.3.20 ( Released under the MIT License | Github | Changelog )

Tested in: jQuery 1.4.3+ in Firefox, Safari, Chrome, Internet Explorer 6, 7, 8, 9, Opera 11.
For older versions of jQuery (1.3.2+), use version 1.3.18

Your WordPress install is 2.8.4 and use jQuery 1.3.2, best of 2009.

So you are in a hole but might be able to stay there if you use old plugin version. Or perhaps replace colorebox script with 1.3.18 as colorbox dev. suggest.

But most will scream Nooooo!

Site does not seem to have much JS stuff, except Nextgen, but possible your old theme will go crazy on latest WordPress. Or other PHP stuff. Dont know, test carefully. Take full backup so you can restore historic code. Newer theme or fix for old could then be tactic.

Technically tool is correct as issue was a link to an infected website of a translator. Was black listed by Google, think it was this one https://www.virustotal.com/url/c3ce6d5afef4b923185e80c561b3f28fb1efea7c719eed5d42067d1f15312e2b/analysis/1351651331/

If you do a re-scan right now you will see it is clean.

Text file can contain malware, does not even have to be a text file so I do not think it is an error of scanner to include text and such files. Or to include “You wont die by looking” bad links category. That is what it is supposed to. But site is of course not infected, must translate findings to real life before doing anything 🙂