Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Nicholas Westby 2054 posts 7100 karma points c-trib
    Feb 13, 2019 @ 18:07
    Nicholas Westby
    0

    ImageProcessor.Web Not Resizing Images with Query String

    Using Umbraco And Getting Started
    Umbraco 7

    In short, none of the images on a site I'm building can be resized with ImageProcessor. Here's one such image: https://nicholaswestby.box.com/s/12plmqwaoinxe94lfj62jxt0u62vqzei

    Same image:

    Random FP Image

    When I attach "?width=50" (using any number), the original image is served up rather than a resized image. This resizing works fine on other sites (even ones with the same Umbraco version).

    When I try to resize an image, there are no error log entries created.

    I still have a few things to try (upgrade ImageProcessor, compare to other installs, etc.), but if anybody has run into this in the meantime I'd appreciate it.

    Some notable things about this project that may impact image resizing:

    • We're using dependency injection (Autofac).
    • We upgrade to .Net 4.7.2.
    • We've password-protected the entire site (using IIS users).

    Version numbers:

    • Umbraco 7.13.2
    • ImageProcessor 2.6.2.25
    • ImageProcessor.Web 4.9.3.25
    • ImageProcessor.Web.Config 2.4.0
    • ImageProcessor.Web.PostProcesor 1.3.1.25
    Copy Link
  • Nicholas Westby 2054 posts 7100 karma points c-trib
    Feb 13, 2019 @ 18:27
    Nicholas Westby
    0

    Tried it on my local and the issue is there too, so the problem isn't the password-protected staging server.

    Copy Link
  • Nicholas Westby 2054 posts 7100 karma points c-trib
    Feb 13, 2019 @ 18:53
    Nicholas Westby
    0

    I upgraded all the ImageProcessor NuGet packages and that seems to have fixed it. I'll report back if I find out any particular details about why that might be.

    Copy Link
  • Nicholas Westby 2054 posts 7100 karma points c-trib
    Feb 13, 2019 @ 19:05
    Nicholas Westby
    100

    The NuGet upgrade seems to have added this to the web.config:

      <imageProcessor>
    <security configSource="config\imageprocessor\security.config" />
    <caching configSource="config\imageprocessor\cache.config" />
    <processing configSource="config\imageprocessor\processing.config" />
  </imageProcessor>

    Could be that this being missing was causing the issue. Unsure why it was missing (there are like 7 developers on this projects, so lots of moving parts).

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft