Module would benefit from a "Requires GD2" error trap

Image Resize Filter isn't actually dependent on GD2 (you can use ImageMagick also), it'll use whatever toolkit is set up at admin/settings/image-toolkit. That page should also give you an error if you don't have an available toolkit at all.

This patch makes it so that the module may not be enabled if no toolkits are available. Image resize filter now provides support for ImageAPI through #512046: Add support for ImageAPI if available.

I know this is an old patch, but I just ran into a bugger of an edge case where I couldnt get image_resize_filter installed.

I had enabled image_api, but hadnt configured it yet and as such had not enabled any imageapi default toolkits, though I *did* have gd installed and live at admin/settings/image-toolkit, so the test at line 25 of image_resize_filter.install was erroneously telling me I didnt fullfill the requirements

function image_resize_filter_requirements($phase) {
  $requirements = array();
  $t = get_t();
  if ($phase == 'install' && function_exists('image_get_toolkit')) {
    if (function_exists('imageapi_default_toolkit') && !imageapi_default_toolkit() || !image_get_toolkit()) {
      $requirements['image_resize_filter'] = array(
        'title' => $t('Image resize filter'),
        'description' => $t('Image resize filter requires at least one active image toolkit on your server.'),
        'severity' => REQUIREMENT_ERROR,
      );
    }
  }

  return $requirements;
}

perhaps inverse the logic in that if statement to the following:

unless ((function_exists('imageapi_default_toolkit') && imageapi_default_toolkit()) || image_get_toolkit()) {

(thats assuming that one requirement or the other is satisfactory)

Thanks, that does make sense. ImageAPI should really kick and scream at people if they've enabled ImageAPI but not one of the toolkits, that's bitten me a few times before too.

I think my initial patch actually may have done exactly what I intended it to do, since you shouldn't have ImageAPI installed at all if you're not using it. However it really isn't the place of Image Resize Filter to be trying to enforce such requirements. I've committed this patch which makes the change as you suggest.

Right on... I probably wouldnt have run into this issue as I *am* using imageAPI.. but I was setting up a new site, and as such didnt necessarily flip on and configure all the modules I was planning on using in the proper order (ie. used drush dl/drush en a bunch). So I had it installed, enabled and not configured (yet).

Patch works for me, thanks!