what exact version of Umbraco are you using?

Do you have any other styles/classes on the image or container that may be overriding the crop size?

I'm using 13.4.1 and have no problems with crop sizes.

Hi Huw,

Thanks for the reply. Im using 13.4.1 as well.

I dont think any thing else is overriding it, because if I browse to the umbraco 8 server

https://

the image is the correct size (ie 100 by 100 pixels) but if I do the same to my dev machine (exact same url with just the host changed): https://localhost:44339/media/jivjqlnq/technician-using-ipad-app.jpg?width=100&height=100&v=1d7378a2e39bf70

The image is the full size of the image

It is possible that this is how it is supposed to be, and that the behaviour in 8 and before is wrong. The actual page which displays it is using a Media Picker insteaed of an Image Cropper. Could that be the cause? It worked in v8, but in 13 all the images are their full size rather than the resized size.

Thanks again,

Kap.

No, there is no mention of "image" in the logs. When viewing the image directly from the browser, I am not seeing any logs entries at all.

I will try and create a new Umbraco 13 site and see if I get the same issue.

Thanks

Kap.

No, this is all I have in Program.cs

builder.CreateUmbracoBuilder()
.AddBackOffice()
.AddWebsite()
.AddDeliveryApi()
.AddComposers()
.Build();

WebApplication app = builder.Build();

await app.BootUmbracoAsync();


app.UseUmbraco()
    .WithMiddleware(u =>
    {
        u.UseBackOffice();
        u.UseWebsite();
    })
    .WithEndpoints(u =>
    {
        u.UseInstallerEndpoints();
        u.UseBackOfficeEndpoints();
        u.UseWebsiteEndpoints();
    });

await app.RunAsync();

I created a new Umbraco 13 project, and it correctly resizes the same image, so it must be something with either the existing code or the database. I will investigate further.

Thanks again for the Help Huw.

We ran into something very similar here. The issue is in fact the UseStaticFile() Handler. If you don't isolate it to avoid /media items, umbraco can't grab that request and manipulate the file on load as necessary. To avoid this, just add something like:

app.UseWhen(context => !context.Request.Path.StartsWithSegments("/media"),
    appBuilder => appBuilder.UseStaticFiles());

This will tell umbraco, for any requests outside of /media for static files, go ahead an allow it like usual (images in /wwwroot, etc). But for anything inside /media, do not all that route to process and instead let Umbraco process it.

is working on a reply...