Thumbnails in assets pane are really full-size images?

Ted
Ted
Vote:
 

While switching Episerver's built-in thumbnail generator for ImageResizer I noticed something peculiar. I might be missing something really basic here, but it seems to me the thumbnail URLs in the assets pane actually produce full-size images as opposed to the thumbnails?

The URL in the assets pane looks like:

/CMS/Content/contentassets/xxxx/some-image.png,,123/Thumbnail?epieditmode=False?1234

That URL produces the full-size image, even though it's shrunk to 48x48 pixels through CSS in the assets pane.

However, if I remove the ,,123 part of the URL...

/CMS/Content/contentassets/xxxx/some-image.png/Thumbnail?epieditmode=False?1234

...I do get the thumbnail of the image.

So what am I missing? How come the assets pane isn't actually rendering the thumbnail image?

#143438
Jan 23, 2016 10:10
Vote:
 

I have hade the same thought and suspicion my self and we found this for a customer last week who complained about slow assets pane. Did not find any solution sadly. But am looking forward for one.

My first thought was that we need to add a blob size in the mediaclass like in the baseclass for imagedata.. 

#143444
Jan 24, 2016 21:28
Ted
Vote:
 

I should probably point out that this is Episerver 9.6, older versions do not seem to exhibit this behavior.

#143455
Jan 25, 2016 11:16
Vote:
 

Hi Ted,

I did experience the same problem (latest version of EPi). Downgraing ImageResizer to v3 is "resolving" the issue. Did you manage to find a solution?

Thanks,

Maciej

#143505
Jan 25, 2016 22:29
Vote:
 

We discussed the same issue in this thread and downgrading is doing the trick for both of us. Not sure why though. But it seems that imageresizer might have done some changes that I am not aware of.

http://world.episerver.com/forum/developer-forum/-EPiServer-75-CMS/Thread-Container/2015/10/imageresizer-not-resizing-after-upgrade-to-episerver-9.2/

#143507
Jan 25, 2016 22:33
Vote:
 

Regarding NuGet package. Not sure if that was the right decision, but there is 2 type of package versions. 3.x is for ImageResizer v3.x. 4.x -> for latest ImageResizer.

There has been an issue with IR to kick in pipeline for the previous version (3.0). Please use latest version - 3.0.1.

And give feedback about versioning of the NuGet package. It follows similar path as you may experience for EF, Asp.Net Mvc and other packages. If this is not obvious - I'll change versioning.

Thanks! (Thanks Eric for the answers)

#143510
Jan 25, 2016 23:09
Vote:
 

I'll did some smoke tests on v4 of ImageResizer, but guess - there has to be more covered tests.

The only thing that is changed between v4 and v3 -> plugin name in web.config (IR changed plugin system naming conventions a bit) and references to IR v4 assemblies.

#143512
Jan 25, 2016 23:13
Ted
Vote:
 

Thanks everyone for helping! I'm not very keen on downgrading to ImageResizer 3, mainly because it feels like "giving up" instead of actually resolving the issue. :)

Valdis, regarding the versioning: I think a single NuGet package where the major version number and dependency aligns with ImageResizer's major version is the right way to go. Thanks for keeping it current!

#143521
Jan 26, 2016 9:59
Vote:
 

Will test properly with v4 soon

#143522
Jan 26, 2016 10:15
Vote:
 

Sweet! I need it :)

#143573
Jan 27, 2016 9:01
Vote:
 

This code in EPiServerBlobPlugin fix the problem

 private void OnPostAuthorizeRequestStart(IHttpModule sender, HttpContext context)
        {
            if (context.Request.Url.ToString().Contains("Thumbnail?epieditmode"))
                return;
...
#144078
Feb 05, 2016 10:00
Vote:
 

Is this for v4? Can you please make pull request? 

Thx

#144080
Feb 05, 2016 10:34
Vote:
 

Yes, this is for v4.

I have made pull request and it was merged.

#144099
Edited, Feb 05, 2016 16:51
Vote:
 

Have you made pull request to correct repo? This is official repo for the NuGet package

#144106
Feb 05, 2016 20:44
Vote:
 

Look for v4.0.2 version on the feed.

#144115
Feb 08, 2016 0:13
Vote:
 

Thanks Valdis! Works prefectly now.

#144219
Feb 09, 2016 11:55
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.