Forums (Obsolete)

Member

dcollins-marketwired - 1/27/2014 3:46:49 PM

What animals must be sacrificed to clear cache?

I have cleared my browser cache, I have changed filenames, I have deleted f8iles and reuploaded, I have gone into System and cleared cache - nothing.

I have images in my forms of my doc types. I use GetImage, which references the GUID. No matter how much I update them - and they tell me they're the right files I can tell bewcause of the dimensions - I keep getting the old images when I preview. No amount of cache clearing, deleting or file-renaming will give me the latest files.


Member	dcollins-marketwired - 1/27/2014 3:54:41 PM RE:What animals must be sacrificed to clear cache? I think this is an actual bug. If you load an image into a form of a doc type, then you update the image by any means, it updates the image but does not adjust the dimensions. So your new image shows at the same size as the old one.

Member

dcollins-marketwired - 1/27/2014 4:26:51 PM

RE:What animals must be sacrificed to clear cache?

This should duplicate the bug I'm experiencing:

In Photoshop, make two images: big: 200x150, small: 100x75. Make sure the image identifies which is which(put the dimensions right in the image). Save them somewhere.

In Kentico, create a new doc type "myDoc" that contains a form with an attribute of type "File", field of type "direct uploader". Call it "myImage".

Use that doctype "myDoc" on a page, say, in a repeater.

Create a transform to display "myDoc" form so that it contains <div class="myImage"><%# GetImage("myImage") %></div>

Add a new document of type "myDoc" to the page. Call it "myDoc1".

Fill out the "myDoc1" form. Field "myImage" will display a little table: [Actions Update Name Size]. Use the file sector control to point at your image "small". Save the form.

Preview. You will see "small 100x75", and if you look at the properties of the image, it will indeed be 100x75.

Now go back to editing the "myDoc1" form. "myImage" will display the little table again: [Actions Update Name Size]. Click the "Update" button and choose the big image. Save the doc and preview.

You will see "big 200x150" - but the image dimensions will only be 100x75. You cannot change them through any act of refreshing or cache clearing.

The only way to update the dimensions of a new image is to return to editing myDoc1 myImage (the little table again: [Actions Update Name Size]) end EDIT it. There you will find Resize options By percetnage and By absolute size. You must manually change the dimensions and save.

I suppose that's less of a bug than a missing feature. It really messed me up because my before and after images (original and updated) are very similar - only different in size. So it took me a half hour to realize that the image had changed while for some reason not displaying at the correct dimensions. (There is no styling applied to the image to force it to the old size - it ought to have automatically rendered at 100%. A mystery).


Kentico Support	kentico_jurajo - 1/28/2014 5:26:33 AM RE:What animals must be sacrificed to clear cache? Hello, What caching options are you using and what web parts are displaying the data? what are the caching settings set for the web parts? Have you tried using cache items and cache access debugs? Best regards, Juraj Ondrus

Member

dcollins-marketwired - 1/28/2014 9:20:20 AM

RE:What animals must be sacrificed to clear cache?

kentico_jurajo wrote: Hello,

What caching options are you using and what web parts are displaying the data? what are the caching settings set for the web parts?

Would it be presumptuous to believe that Site Manager > Admin > System > Clear Cache would clear out all these, regardless of their settings? Because I'm doing that constantly without success.

Kentico Support

kentico_jurajo - 1/28/2014 9:27:40 AM

RE:What animals must be sacrificed to clear cache?

Hi,

Yes, but you have not mentioned it in your first post. What about the debugs? Have you tried them? I was unable to reproduce the issue so far. So, it seems that there is something else that is caching it - are any proxy servers or other elements in the way?
What about the suggestion in the other post?

Best regards,
Juraj Ondrus