Selectively replace broken, unlicensed, and other problematic images on a site's public-facing "Front End."

CK MacLeod

<p>WP Replace Unlicensed and Broken Images (WP-RUBI) replaces images selected by date, post, category, author, file location, and/or image type with a user-adjustable default image on a site’s public-facing Front End – in other words, on display – and will also, unlike common Javascript/jQuery solutions for broken images and links, prevent load errors and search engine “crawl” errors that can harm Search Engine Ranking. A primary use will be for sites where – due to policy change or concerns relating to usage rights and copyright infringement – administrators need to expunge images that have been used without permission or under lapsed or lapsing usage licenses, while avoiding a time-consuming, complex, hard-to-reverse, potentially costly and inefficient database purge. Another use will be for sites whose image archives have been corrupted or lost.</p>
<p>WP-RUBI will do nothing until the site administrator has determined which images or types of images to remove and replace. All post images and image links that are matched in posts selected either individually or globally – for instance, all posts from before a certain publication date – will be replaced by links to a simple, customizable “image removed” image when the page is displayed: The change is made just-in-time as the post is loaded, altering the page “source” as rendered, but <em>not</em> affecting the database. If at some future time the site operator wishes to restore lost images, or “whitelist” a post, author, category, time frame, or image type, then the original links and formatting information will still be easily accessible.</p>
<p><strong>WP-RUBI is a powerful plug-in, potentially allowing for far-reaching alterations in your site’s appearance, but it makes no permanent changes to your posts database or image library or any other files: Changes can be immediately rolled back by resetting to defaults via Main Settings, or by de-activating (or uninstalling). Still, as generally with WordPress Plug-Ins, the further your installation diverges from a “basic” WordPress site – by employing unique frameworks, complex themes or plug-ins, or specialized customizations – and the higher your traffic, the more care and caution you should employ when installing, activating, and configuring WP-RUBI.</strong></p>
<p>Also note that WP-RUBI is designed with typical WordPress sites in mind. Though it can also be set to remove and replace copy-protected and externally served images (as long as display relies on <code><img src=</code> tags), it may not function optimally, if at all, or may require careful adjustment, when used with sites or themes relying on unusual image delivery and display methods, or that significantly diverge from other standard practices: “gallery”-style themes that may extract image links from post content and convert them into CSS backgrounds, for example. More commonly, caching and copy protection plug-ins, CDNs lacking purge options, and so on, may need to be flushed and reset, or in some instances disabled, for WP-RUBI to achieve the intended results.</p>
<h3>Background</h3>
<p>In recent years, with the maturation of the internet and especially of the “blogosphere,” sites where photos and other images have been copied and displayed without concern for the rights of artists and services have come under enhanced scrutiny, sometimes resulting in costly lawsuits and threats of lawsuits. In addition, some site operators, especially as they have gotten more successful, have simply undergone a change in thinking about common internet practices viewed by some artists as theft.</p>
<p>Many or perhaps most bloggers still operate without concern for image licensing, and some have discovered – sometimes at significant cost – that, as one victim of a “copyright-trolling” lawyer put it, “Current Fair Use image copyright laws say that you’re financially liable for posting copyrighted images.”* You may be liable for unlicensed use of images even if:</p>
<ul>
<li>You did it by accident</li>
<li>You immediately take down the picture after receiving a DMCA takedown notice</li>
<li>The picture is resized</li>
<li>The picture is licensed to your web developer</li>
<li>You link back to the photo source and cite the photographer’s name</li>
<li>Your site isn’t commercial and you make no money from your blog</li>
<li>You have a disclaimer on the site</li>
<li>The pic is embedded instead of saved on your server</li>
<li>You found it on the Internet (that’s not an excuse!)</li>
</ul>
<p>The core of this plug-in was originally implemented on a large site in one such predicament: The operators, after having been challenged by a copyright lawyer demanding thousands of dollars in payment for the use of a single unpaid-for image, and facing a steep legal bill even in pursuit of an eventually successful defense, decided to stop displaying any images whose usage rights were not fully cleared.</p>
<p>The operators were left with thousands of unlicensed images associated with archived posts – along with many images that were used fairly (because original to the site or author, or in the public domain). Finding and replacing images as well as image links presented numerous complications: Simply deleting image archives rather than editing the posts would produce numerous load errors, which would harm the site’s search engine ranking, produce unprofessional “broken images” display, and make restoration of good posts difficult where not impossible. Using a Javascript solution that obscured broken images and links might improve display, but would leave errors in place, and have no effect on unwanted images that were not deleted.</p>
<h3>Using WP Replace Unlicensed and Broken Images</h3>
<p>WP Replace Unwanted and Broken Images enables an Administrator to bring his or her site into effective compliance quickly, and then to recover “good” images if desired, while preserving archives.  The plug-in adds numerous additional choices and other improvements to the earlier “WP Replace Old Images,” making it easier for an Administrator to refine the “purge,” and for the site’s editors and authors to restore old posts and archives to full health.</p>
<p>Improvements include:</p>
<ul>
<li>Posts can be excluded or included via Edit Post</li>
<li>Posts can be excluded or included via All Posts Quick and Bulk Editing</li>
<li>Featured images (or thumbnails) also can be removed/replaced</li>
<li>Easy Inclusions or exclusion from image removal/replacement for authors and categories, and for “after” as well as “before” dates</li>
<li>Replacement images provided with “cache-busting” queries (so changes to Front End can take effect immediately)</li>
<li>User can upload own replacement image from Settings page, or choose “blank” and “erasure” replacement modes</li>
<li>Installation routine preserves old settings on upgrade</li>
<li>Detailed usage notes/tips/documentation</li>
<li>Translation-ready</li>
</ul>
<p><em>ALSO NOTE DISCLAIMER: Developer makes no promises or guarantees that use of this plug-in will secure a site against all claims of copyright infringement based on past practices. No one can do that!</em></p>
<p>*Description and list of Fair Use liability issues from <a href="http://www.contentfac.com/copyright-infringement-penalties-are-scary/" rel="nofollow ugc">“The $8,000 Mistake That All Bloggers Should Beware”</a></p>
<h3>Additional Info</h3>
<h4>Still to Come</h4>
<ol>
<li>“Recuperation” workflow – list and select cured/uncured posts/authors/categories</li>
<li>Additional image selection patterns and inclusion/exclusion options</li>
<li>Optional database purge</li>
<li>Development of Digital Artists Alliance site and network</li>
</ol>
<p>Check the <a href="http://ckmacleod.com/wordpress-plugins/wordpress-replace-unlicensed-and-broken-images/" rel="nofollow ugc">WP-RUBI home pages</a> for additional background, usage tips, and minor updates, or to <a href="http://ckmacleod.com/wordpress-plugins/wordpress-replace-unlicensed-and-broken-images/get-replace-images-support/" rel="nofollow ugc">contact the developer</a>.</p>
<h4>Thanks!</h4>
<p>To all of the developers and everyday code-hackers, far too numerous to name, upon whose work I have depended. And  Thanks to <a href="https://profiles.wordpress.org/thatgrrl" rel="nofollow ugc">thatgrrl</a> for catching a bad link to the plug-in’s home page!</p>


Alternatives to WP Replace Unlicensed and Broken Images

Top alternatives