Databases
StackOverflow2013
Postsdbo
POPaperclip ruby on rails s3 to_file method
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPaperclip ruby on rails s3 to_file method
    primarykey
    data
    text
    <p>I'm very confused here as to why paperclip isn't working for me.</p> <p>When accessing a previously saved file on s3 for processing this method of the paperclip s3 storage class causes an error:</p> <pre><code> def to_file style = default_style return @queued_for_write[style] if @queued_for_write[style] filename = path(style).split(".") extname = File.extname(filename) </code></pre> <p>What is happening is the path is being split into an array which then isn't accepted by File.extname which returns the error "can't convert Array into String". </p> <p>I'd really appreciate some advice on this; maybe my path is wrong but I cannot see how split is going to return anything but the array which causes an error on File.extname. This works fine in development but not on heroku where it worked previous to last weekend.</p> <p>Thank in advance.</p> <p>EDIT</p> <p>Have added a weighty bounty on this which reflects my ongoing frustration. Really if someone can help me troubleshoot this I'd be incredibly grateful. I've ruled out previous doubts I had, that maybe it was the heroku repository, by freshly installing the app again. </p> <p>All pertinent code as far as I can tell:</p> <pre><code>#photo.rb has_attached_file :photo, :styles =&gt; { :list =&gt; "150x100#", :article =&gt; "264&gt;x210", :large =&gt; "558&gt;x380", :original =&gt; "1024&gt;x768" }, :storage =&gt; :s3, :s3_credentials =&gt; "#{RAILS_ROOT}/config/s3.yml", :url =&gt; ":s3_alias_url", :s3_host_alias =&gt; "files.mydomain.com", #s3 bucket with dns cname record to subdomain :path =&gt; "/photos/:hashed_path/:style/:id.:extension" #config/s3.rb bucket: files.mydomain.com access_key_id: ******************* secret_access_key: ********************************** </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmark
    1. USmark
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. USpjmorse
      1. VTFavorite
    2. VO
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. USmark
      1. VTFavorite
    1. COThat code does look wrong. Would it be possible for you to create a minimal test application demonstrating the problem and put it on github?
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. USkch
    2. COUnfortunately not. This cannot be a fault with paperclip from whence came this code as it works fine in development. Not being able to reproduce the error locally has me pretty wound up to be honest. I'm going to post a whole bunch of code just shortly.
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. USmark
    3. COI'm planning to run the app on heroku with s3. (I came here from your zendesk support ticket. Sorry that was not clear.)
      singulars
      1. POPaperclip ruby on rails s3 to_file method
      1. USkch
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload