Problem with js/thickbox/loadingAnimation.gif & GPU Usage

I took a quick look at your site, and here’s what I see:

It appears you’re using TB (ThickBox) as a plugin, and it also appears that you have multiple instances of TB loaded.

You have this one:

<script type='text/javascript' src='https://consequenceofsound.net/wp-content/plugins/wp-shopping-cart/js/thickbox.js?ver=Instinct_e-commerce'></script>

And then you have this one:

<script type='text/javascript' src='https://consequenceofsound.net/wp-includes/js/thickbox/thickbox.js?ver=3.1'></script>

I suspect that’s not a good idea. I couldn’t quickly find an image that clearly should have been loading with TB. I tried the images in the sidebar (Springsteen, etc) and they didn’t load with TB, so it’s not clear that TB is working. The 2 instances of it might be why.

In my configuration, I’m loading TB not from a plugin, which simplifies things in a way. For you to sort this out, I’d try to eliminate 1 of the 2 TB instances, and then get in touch with the plugin author.

To answer your last question, your link with festival-outlook in it is from a page with that name. You’ll know it’s working when it doesn’t generate a bad link. The plugin isn’t following the standard TB behavior; maybe there is another setting for the plugin? If you were using only the javascript TB (rather than a plugin), the fix you made would be done.

Btw, here’s a link to the forum of the original developer of TB:

https://codylindley.com/thickboxforum/

Since you aren’t using TB by itself, they may just refer you back to the plugin author, but the folks there know a lot more about TB than I do.

Good luck.

https://core.trac.www.ads-software.com/ticket/6453

I think this is a problem in the thickbox.js that’s included with WordPress

I did something stupidly hacky to deal with this.

I was noticing that the file does exist at ?/wp-includes?/js?/thickbox?/loadingAnimation.gif

But I was getting all sorts of requests for it for URLS like /<some page name>?/wp-includes?/js?/thickbox?/loadingAnimation.gif

My “hack” to avoid dealing with it for now is I setup a regex with the Redirect Plugin.

All it does is look for /(.*)/wp-includes/js/thickbox/loadingAnimation.gif
and send any of those to /wp-includes/js/thickbox/loadingAnimation.gif

Yeah, I know that’s ugly, but for the moment, I’m happy with it.

._.

Does anyone know how much consequence this has on the server? We are dying over here from error hits on that dog.

/wp-includes/js/thickbox/thickbox.css 37,248

I had it working with the redirection plugin, but now it’s back again. Perhaps something in 2.8.5 did kill this.

I’m not even sure what is calling that tickbox thingy in the first place. Can’t remember installing a plugin using it.

Upgraded three blogs to Version 2.8.6. Got buried in 404 reports for

/page/wp-includes/js/thickbox/loadingAnimation.gif
and
/xxxx/xx/xx/wp-includes/js/thickbox/loadingAnimation.gif

So the system is now looking for the images in non-existent directories. I am guessing this is a change in how WP is is calling pages – might be a change not yet picked up by a plugin, but I don’t think so.

As suggested above, I have “fixed it” with Redirection 301 redirects:

Source URL: /(\d*)/(\d*)/(\d*)/wp-includes/js/thickbox/loadingAnimation.gif
Target URL: /wp-includes/js/thickbox/loadingAnimation.gif

Source URL: /page/wp-includes/js/thickbox/loadingAnimation.gif
Target URL: /wp-includes/js/thickbox/loadingAnimation.gif

Paul

another solution is to put this in your footer right above </body></html>

<script type=”text/javascript”>
tb_pathToImage = “/wp-includes/js/thickbox/loadingAnimation.gif”;
tb_closeImage = “/wp-includes/js/thickbox/tb-close.png”;
</script>

this will avoid having to use cpu to do the rewrite method (which is a fine solution tho)

The problem you are having is that wordpress’s version of thickbox is being included. That version however is specifically coded for the admin side of the site. While it can be used easily for front end stuff, it has this nasty side effect.

If you don’t want to add that to your footer, just edit thickbox.js in wp-includes/js/thickbox. problem there tho is new versions of wordpress will overwrite your change. Best to just add this to footer.php of your theme.