First of all, great plugin from what I've read in this forum. I went through every single thread. Your patience and readiness to respond to those with issues is much appreciated, especially when sometimes people are both demanding and less-than-courteous...
Now, unfortunately, I'm having trouble getting Imaguard to work for our site.
The site's server runs PHP 5.2. DG Library enabled.
WP Permalinks enabled. That's how it's been for years.
WP SuperCache cache deleted. Imaguard plugin deactivated and then reactived.
Checked Google Images search on Chrome, both signed in to Google & anonymous browsing.
Unfortunately, neither Imaguard's "redirect" nor the "show darkened image" option worked for us.
Possible causes for the problem (now it gets a little complicated):
Imaguard modifies the site's .htaccess file in the "blog" (WP) folder. The site, however, has another .htaccess file in its root folder, "above" WP.
We had an anti-hotlinking protection code pasted there. With or without Imaguard activated, that code works. (Blurry images; but if the browsing individual has signed in to Google, the full size, high-res. image is shown -- much to our outrage).
If our anti-hotlinking code is removed and Imaguard is left alone, *nothing* works. In other words, the images on Google Images are loaded full size, high-res. for *everyone*.
We also tried removing our own anti-hotlinking code and pasting the Iamguard .htaccess code on the site's topmost .htaccess file. That didn't work either. Hotlinked images were loaded normally.
Important: Our images are NOT wp-upload images. They're found in a different folder, uploaded via regular FTP, *outside* the WP folder.
Could that be the issue? If so, is there a workaround?
I'd like to send you both .htaccess files and links to the site so you can see for yourself what's going on, but I'll wait for your go-ahead before I do so.
P.S. Regarding comments found elsewhere in this Imaguard forum: My understanding is that Google Images sends a blank referrer when uploading your images. We currently allow blank referrers, which helps to explain why our high-res. images are loaded to those who have signed in to Google. Now, we did try blocking blank referrers and that worked in preventing high-res. images from loading to *anyone*. The glitch: Google wouldn't index our new images and several older ones were dropped from their index. It's infuriating, maddening, outrageous -- but that's how their system works now. (Until the inevitable class-action lawsuit...)