Rails: carrierwave uninitialized constant error

Question

I have Rails 3

Carrierwave 0.5.4

//app/uploaders/fasta_uploader.rb

class FastaUploader < CarrierWave::Uploader::Base
  storage :file
  def store_dir
      'public/data/01_fasta'
  end
end

//migration

class AddFileUpToCvits < ActiveRecord::Migration
  def self.up
    add_column :cvits, :fasta, :string
  end

  def self.down
    remove_column :cvits, :fasta
  end
end

//app/models/cvit.rb

class Cvit < ActiveRecord::Base
    attr_accessible :fasta
    mount_uploader :fasta, FastaUploader
end

//form

<%= form_for(@cvit, :html => {:multipart => true, :onsubmit => "return ray.ajax()" }) do |f| %>
  ...
  ...
  <%= f.file_field :fasta %><br></br>
  <div class="actions">
    <%= f.submit "Submit"%>
  </div>
<% end %>

I get this error: uninitialized constant Cvit::FastaUploader

Any suggestions???

score 65 · Accepted Answer · answered Jul 07 '11 at 18:27

65

A simple reset of the server fixed the problem -_- You live and you learn.

answered Jul 07 '11 at 18:27

bdeonovic

4,130
7
40
70

4

The server reset is necessary if you have not restarted since generating your first uploader. I believe it's because your first uploader class results in a new 'uploaders' folder being created, and it is not on the search path by default. – Mike E Nov 30 '11 at 16:12
2

I made it too, and you save me any real time in solving it. – Narfanator Jan 08 '13 at 02:46
1

Ha, struggled for a while with this - the old "off and on again" sorted it, cheers dude! – Crwydryn Apr 14 '14 at 13:24
3

On my Mac, I had to close the terminal session and restart rails console. A simple stop and restart in the same terminal session didn't work for me. – Feckmore Dec 08 '14 at 21:33
@Feckmore thats suprising, I am pretty sure 3 years ago when I did this I was working on a Mac. – bdeonovic Dec 09 '14 at 01:03
5

And if you use spring with rails, make sure to `spring stop` as well. – Peleg Dec 13 '14 at 16:01
2

got me too... doh!. Even 4 years later. – Sebyddd May 12 '15 at 17:19
1

I had numbers in the name of my upload file, once I changed it to all letters it worked. – Harry Wang May 27 '15 at 18:29
2

I heard there was a restart server fixing problems party here. got me too... doh! – nach Jun 08 '15 at 19:47
2

got me too... doh! But well I'm already the 53rd guy upvoting this answer. And the first from 2016. – Cyril Duchon-Doris Mar 18 '16 at 00:13
2

got me too... doh! – typicalk May 23 '16 at 19:53
1

got me too... doh! (isn't it amazing how many "issues" can be solved by restarting the Rails server and how easy it is to forget do do it?) – conorom May 23 '17 at 19:27
1

got me too... doh! – BooBailey Jul 12 '17 at 19:22
2

for me i had to clear redis cache and it worked – Amir El-Bashary Jan 26 '21 at 15:02

score 0 · Answer 2 · answered Feb 09 '23 at 07:28

0

Restarting the server doesn't work for me. I restarted my mac and it fixed the issue.

answered Feb 09 '23 at 07:28

Taimoor Hassan

365
2
11

score 0 · Answer 3 · answered Jun 01 '23 at 21:27

0

Looks like my problem was with some initialization code before the uploader could be initialized itself.

I had a reference to one of my models that had a reference to the uploader inside of an initialization file located at config/initializers.

answered Jun 01 '23 at 21:27

Thomas

2,622
1
9
16

Rails: carrierwave uninitialized constant error

3 Answers3