404 errors from 20 png files

I have the same exact problem on my website!
I am using it with nextgen 1.9

I’m getting a lot of 404 errors also. The path is wrong.

The problem is still there, everyday…..
someone can give us an answer???

Seeing the same thing on a couple sites where I use Fancybox for WP.

It looks like the images path are loading incorrectly relative to whatever post is being viewed, like:
/post-name-one/fancybox/fancy_shadow_nw.png
/post-name-two/fancybox/fancy_shadow_nw.png

This seems like a really basic issue; hopefully the developer updates at some point.
If I have a sec, I’ll look into it; if I find a temp fix I’ll report it here…

This doesn’t seem to be the plugin developer’s problem as much as it is with the original Fancybox (assuming it’s a pretty direct implementation)…

The issue lies with the Internet Explorer-specific filters within the plugin’s fancybox.css file (located in plugins/fancybox-for-wordpress/fancybox).

At the bottom of that file you’ll see:

.fancybox-ie #fancybox-bg-n { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='fancybox/fancy_shadow_n.png', sizingMethod='scale'); }
.fancybox-ie #fancybox-bg-ne { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='fancybox/fancy_shadow_ne.png', sizingMethod='scale'); }

… and so on … from lines 350-357, 8 lines in total.

It seems that this filter loads the image relative to the page it is called from, and not the CSS file: https://msdn.microsoft.com/en-us/library/ms532928%28v=vs.85%29.aspx

In any case, I’m simply commenting ALL out those lines for the time being (if you make any edits be sure to do them again if you update!).

What do you mean by “simply commenting”??
what to do? delete those entries?

To comment out CSS, place /* and */ at the beginning and end of the css you wish to deactivate respectively.