You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It took me a little bit to work that out, as it wasn't really obvious what the issue was. The image would actually upload successfully, and the binary would appear in the image table - but the file_name and content_type properties would be empty so the image couldn't be retrieved via paperclip.
What's weird, is that ":rails_root/public/system/:class/:attachment/:id_partition/:style/:filename" is meant to be the default value for the :path setting anyway according to the paperclip documentation.
Is this something that needs to be fixed in paperclip_database?
If not, maybe add a note about setting the :path to the README?
The text was updated successfully, but these errors were encountered:
What's strange is that this all worked fine until I had to wipe my computer. All of the gems and libraries that are listed for both Paperclip and Paperclip database are installed.
To get working on Heroku, I had to set the
:path
in the call tohas_attached_file
like so:It took me a little bit to work that out, as it wasn't really obvious what the issue was. The image would actually upload successfully, and the binary would appear in the image table - but the file_name and content_type properties would be empty so the image couldn't be retrieved via paperclip.
What's weird, is that ":rails_root/public/system/:class/:attachment/:id_partition/:style/:filename" is meant to be the default value for the
:path
setting anyway according to the paperclip documentation.Is this something that needs to be fixed in paperclip_database?
If not, maybe add a note about setting the
:path
to the README?The text was updated successfully, but these errors were encountered: