Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating from paperclipped extension? #59

Open
jfahrenkrug opened this issue Feb 7, 2012 · 2 comments
Open

Migrating from paperclipped extension? #59

jfahrenkrug opened this issue Feb 7, 2012 · 2 comments

Comments

@jfahrenkrug
Copy link
Member

On 0.9 I used the paperclipped ext, now I'm in the process of moving to 1.0 and I've ditched paperclipped for clipped.

So far, my assets on disk are in the form of .../890/someimage_normal.jpg someimage_thumbnail.png someimage_icon.png

I've run the clipped migrations and also made sure that ImageMagick's identify command can be run.

In the admin interface, I can upload assets and edit them, but only the original sized images work: Neither the icons nor the thumbnails work. Is there a migration process or something that I'm missing?

@jomz
Copy link
Member

jomz commented Feb 7, 2012

2 guesses;

  • after running the migrations or altering the clipped configuration, I think you have to restart the server and thén regenerate thumbnails for the thumbnails to be generated to the correct location
  • check Radiant.config["paperclip.url"] and Radiant.config["paperclip.path"]; these are used to get the paths. At some point, this was changed from public/assets/... to public/system/assets
    What are the values for these, and what is the complete path where Radiant is trying to fetch the thumbs?

@jfahrenkrug
Copy link
Member Author

Hi @jomz,

Thank you for your reply. So I did restart the server, but that didn't help.

Here are the relevant parts of my Radiant.config:

assets.additional_thumbnails normal=640x640>
assets.display_size original
assets.content_types image/jpeg, image/pjpeg, image/gif, image/png, image/x-png, image/jpg, video/x-m4v, video/quicktime, application/x-shockwave-flash, audio/mpeg, video/mpeg
assets.max_asset_size 5
assets.skip_filetype_validation true
assets.image_magick_path /opt/csw/bin/
assets.path :rails_root/public/system/:class/:id/:basename:no_original_style.:extension
assets.url /system/:class/:id/:basename:no_original_style.:extension
paperclip.url /system/:class/:id/:basename:no_original_style.:extension
paperclip.path :rails_root/public/system/:class/:id/:basename:no_original_style.:extension
paperclip.skip_filetype_validation true
paperclip.storage filesystem
paperclip.fog.public? true
assets.create_image_thumbnails? true
assets.create_video_thumbnails? false
assets.create_pdf_thumbnails? false
assets.thumbnails.image normal:size=640x640>
assets.thumbnails.video normal:size=640x640>,format=jpg
assets.thumbnails.pdf normal:size=640x640>,format=jpg
assets.insertion_size normal
assets.create_video_thumbnails false

The actual files are at shared/system/assets. Example: shared/system/assets/627:

img_icon.png  img_normal.jpg  img_thumbnail.png  img.jpg

Is that normal that there are some assets and some paperclip settings?
Btw, with exactly the same settings and the paperclipped extension on Radiant 0.9.1, everything works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants