# Attachment\_fu, temporary uploads, and RMagick manipulations

**URL:** <https://www.ruby-forum.com/t/attachment-fu-temporary-uploads-and-rmagick-manipulations/108820>\
**Category:** Rails\
**Created:** [July 7, 2007, 5:47pm UTC](https://www.ruby-forum.com/t/attachment-fu-temporary-uploads-and-rmagick-manipulations/108820 "2007-07-07T17:47:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Spence\_Akiri](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/45deac/32.png) [@Spence\_Akiri](https://www.ruby-forum.com/u/Spence_Akiri)\
**Post date:** [July 7, 2007, 5:47pm UTC](https://www.ruby-forum.com/t/attachment-fu-temporary-uploads-and-rmagick-manipulations/108820/1 "2007-07-07T17:47:51Z")

</div>

I want to provide users the option to upload images and have them  
manipulated with RMagick before scaling them down. The problem is,  
I’m not sure how to set up the controller to treat images that aren’t  
passed through the manipulation stage.

Users:

1. upload an image with a form, through which the image is resized to  
something manageable with attachment\_fu’s :resize\_to,
2. are thereafter redirected\_to to a new action where they can choose  
to manipulate the picture with RMagick filter(s),
3. after choosing to manipulate the image (or not), the image is  
scaled down further.

Basically, I don’t want pictures to stay big for long, but if the user  
navigates away from the manipulation action, the image is never scaled-  
down.

How do I ensure that images are scaled down a second time?  
Is this a job for an app-wide before\_filter?