Rails3 and attachment_fu #30
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It doesn't seem to work on rails 3.0.3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hey technoweenie,
first I am thankful to you for developing attachment_fu in the first place.
I have a production project running on rails 2.3.8 with attachment_fu. I started upgrading to rails3.0.3 and run into a bunch of problems. at first I got a little scared and thought I should just switch my code to use something like paperclip or carrierwave. looking at those projects made me realize I would run into many more troubles trying to convert my code.
so I cast away all the fear and pulled up my sleeves. I made some minor changes to attachment_fu and made it compatible with the latest rails release.
maybe You want to pull this for other developers that may be walking the same path.
all the best and thanks again!
Mihael