>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1696448. --> Reported by: [thedavidmeister](https://www.drupal.org/user/657782) >>> <p>Project page - <a href="http://drupal.org/sandbox/thedavidmeister/1672224">http://drupal.org/sandbox/thedavidmeister/1672224</a></p> <p>$ git clone <a href="http://git.drupal.org/sandbox/thedavidmeister/1672224.git">http://git.drupal.org/sandbox/thedavidmeister/1672224.git</a></p> <p>Comments by me on other sandboxes under review:<br> - <a href="http://drupal.org/node/1694474#comment-6260750">http://drupal.org/node/1694474#comment-6260750</a><br> - <a href="http://drupal.org/node/1696494#comment-6260824">http://drupal.org/node/1696494#comment-6260824</a><br> - <a href="http://drupal.org/node/1684700#comment-6260890">http://drupal.org/node/1684700#comment-6260890</a></p> <p>This module is for both Drupal 6 and 7 but since ImageCache was merged into core in D7 it works with the core's "Image" module instead of ImageCache there.</p> <h2>Image(Cache) Defaults</h2> <p>This module allows for default images to be configured for ImageCache presets and/or Image styles. This module is intended to address two primary use cases:</p> <ol> <li>The intended or implemented layout of a site relies heavily on images for its structure. Often it becomes difficult or disproportionately time consuming to maintain these sites in a way that degrades gracefully when those images are absent.</li> <li>A developer working locally with an imported codebase or distribution profile wants to create a development instance of a production site by (re)importing a copy of the database but she wants to avoid dealing with the cumbersomely large files directory or the inappropriate/incomplete content generated by the <a href="http://drupal.org/project/devel">Devel Generate</a> module. Avoiding both can easily lead her to introduce new layout issues that aren't detected until after deployment (which is bad) simply because she isn't working with an accurate enough representation of the production environment.</li> </ol> <p>This module is intended for developers who want to minimise that frustrating time spent importing and deploying projects with large files directories that contain mostly images. We do our best here to make sure this module works "out of the box", but still provides intelligent configuration options and is 100% exportable if you're working with <a href="http://drupal.org/project/features">Features</a> and Distribution Profiles.</p> <h3>What Image(Cache) Defaults currently does</h3> <ul> <li>Scans <em>"sites/[site]/files"</em>, <em>"sites/all/files"</em>, <em>"profiles/[current_profile]/files"</em>, <em>"path/to/imagecache_defaults/images"</em> (in that order) for an image named "imagecache_defaults" and sets this as the default image for Image(Cache).</li> <li>Detects if a broken file-path is about to be sent to Image(Cache) to be rendered and replaces it with the default image</li> <li>Works equally well with ImageCache presets in Drupal 6 and core Image styles in Drupal 7</li> <li>(Optional) Allows you to apply a preset/style to the default image in addition to the preset/style that would be applied to the broken image</li> <li>(Optional) Logs a watchdog message to the database when broken file paths are detected</li> <li>(Optional) Remove all broken images from your markup completely to avoid 404 errors instead of replacing them with the default</li> </ul> <h3>Alternatives</h3> <p>For an alternative way to work around broken image links, have a look at <a href="http://drupal.org/project/stage_file_proxy">Stage File Proxy (SFP)</a> which allows you to automatically point your broken image links at a custom url but at the time of writing it has a few limitations that ImageCache Defaults doesn't:</p> <ul> <li>SFP doesn't check if certain files exist before replacing them so you can accidentally DOS yourself with it <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/stage_file_proxy/-/work_items/1545912" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/stage_file_proxy/-/work_items/1545912</a></span></li> <li>SFP can't remove broken image tags from your page completely</li> <li>SFP isn't recommended for use on production sites so there's an extra step in downloading, enabling and configuring it every time you reimport your production site</li> <li>SFP doesn't log the location of broken images to watchdog</li> <li>SFP relies on server configuration but has only been tested on Apache 2 on Mac OSX and Linux</li> <li>SFP requires the developer to have the same relative paths to system file directories on development and production sites</li> <li>SFP requires more configuration than simply enabling it before it starts working</li> </ul>