Attachment::path shouldn't be private
Reported by Nathan Stitt | April 12th, 2008 @ 12:36 AM
I'm attempting to incorporate paperclip into a project where I need to be able to open the original image so I can perform various post processing on it.
However the only way I can see to find the path were it's stored at is to call the path method, but it's marked as private. Of course I could calculate the path myself, and it is fairly simple to do so, but why duplicate what already there?
For now I've done it on my own copy, but then I have to remember to do so every time I upgrade.
Any chance we could get this changed?
Thanks for the great lib, it's exactly what I was hoping attachment_fu would be, but it turned out to be a bit to heavy for my tastes.
Comments and changes to this ticket
-
Jon Yurek April 15th, 2008 @ 05:21 PM
- → Assigned user changed from “” to “Jon Yurek”
- → State changed from “new” to “open”
You know, I was intending that it be backend-agnostic, but I don't see why this can't be public, so yeah. I'll get that added soon.
-
Jon Yurek April 16th, 2008 @ 10:41 AM
- → State changed from “open” to “resolved”
This has been changed in the latest version.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
