Comments on: FileColumn: regenerate images

By: Alexander Lang

Alexander Lang — Sun, 10 Feb 2008 20:49:01 +0000

i think you are right. capitalize works as long as the class name only consists of one word, which has been the case for all our classes so far.

By: Sascha

Sascha — Wed, 06 Feb 2008 14:31:32 +0000

I changed class_name.to_s.capitalize to class_name.to_s.classify, because calling update_model(:common_page_asset, :asset) was not working with capitalize. Maybe i misunderstood your parameter convention or the script has to be changed when using model names with underscores. However, thanks for the script!

By: thilo

thilo — Fri, 07 Sep 2007 10:13:16 +0000

Hi Homan, thanks for your insight. Are u sure that it can’t access the version information? Because I have to provide the model object anyway (e.g. url_for_image_column(@auto, ‘photo’, :badge_5) . And as far a I can see it always ends up in create_magick_version_if_needed. And it works just fine for us, deleting just specific versions. Because it checks each version, as it can be seen in the above mentioned method, here ‘File.exists?(absolute_path(version_options[:name]))’. We just use it in one case, so maybe it just works by coincident. But I hope not

By: Homan

Homan — Thu, 06 Sep 2007 22:32:25 +0000

There are some conditions as to whether url_for_image_column will regenerate a new image version on the fly. File_column places the master version in the directory:

model_name/column_name/record_id/image_name.ext

Alternate named versions like ‘thumb’ will be placed in the same directory but in a folder of the same version name:

model_name/column_name/record_id/thumb/image_name.ext

Now, if you delete the image in the thumb directory, no new image will be regenerated. You just get a broken link. If however, you delete the thumb directory entirely, url_for_image_column will attempt to generate a new named version for you. However, it is not smart enough to determine the size from the versions information defined in the model, you must specify the crop and size options in the url_for_image_column parameters.

By: Marc

Marc — Sat, 25 Aug 2007 08:04:02 +0000

Thanks Thilo!

I had never heard of url_for_image_column before. Once I started searching for it, the only good documentation I found was in the source files themselves. That has accomplished exactly what I needed.

By: Thilo

Thilo — Tue, 21 Aug 2007 08:09:44 +0000

We don’t integrate the script in our site. We ran it on demand. Because it regnerate all images. This puts serious load on our serve ran took a couple of days.

If you need new inmage versions on demand it is better to use: url_for_image_column. It checks if a version exitst and renerate it if not. But it can’t update geometrie of existing versions. Hope that helps.

By: Marc

Marc — Sun, 19 Aug 2007 19:30:33 +0000

Great workaround Thilo!

I apologize if this is a trivial question, but how would one integrate this into their Rails site? It seems like there would be several possibilities, so how would you do it?