ruby-on-rails-3.2

My question: Should I roll my own model versioning or use one of the versioning gems that's already out there? If I should use a gem, which one seems best for this application? Info about my app My app is a simple Checklist app. There are Checklists and Jobs, and I track user responses with Responses and Submissions. The Response tells me what the use said ("Done", with a note "We need more mops.") and the Submission tells me when that particular Checklist was filled out (because there may be many submissions and sets of responses for a given checklist). I'll show my associations below, in

I am deploying with Capistrano to my new VPS. After the first deploy(cap deploy) everything was OK (site was running), but the second deploy failed on assets:precompile error. I am running rails 3.2.13, ruby 2.0.0, rvm. error: * executing "cd -- /home/rails/releases/20140116121250 && RAILS_ENV=production RAILS_GROUPS=assets bundle exec rake assets:precompile" servers: ["IP"] [IP] executing command *** [err :: IP] bash: line 1: 23406 Killed RAILS_ENV=production RAILS_GROUPS=assets bundle exec rake assets:precompile command finished in 84187ms *** [deploy:update_code] rolling back * executing

I have a problem, I don't planned my database correctly, so always I need to use 'alternatives'. I want pre-selected multiple values in select_tag. But I'm adding the vacancies 'manually' in table vacancy. My controller: def create @hr_curriculum_generic = HrCurriculumGeneric.new(params[:hr_curriculum_generic]) # Tabela CandidatosxVagas unless params[:vacancy_ids].nil? @vacancies_ids = params[:vacancy_ids] -- my form: @vacancies_ids.each do |vacancy_id| # Armazena os id do curriculum, vaga e do cargo na tabela CandidatosxVagas @candidates_vacancies = CandidatesVacancy.new <% @vacancies =

Lets say I have a user model that has many articles. If I call user.articles.new many times I will have many unsaved article objects associated with the user. They are visible when you run user.articles. Calling user.save will save all of this unsaved records. How can I delete unsaved records? I plan on calling user.save but I don't want those unsaved records to be there I use the following workaround before_validation :remove_blank_articles! : class User has_many :articles validates_associated :articles before_validation :remove_blank_articles! private def remove_blank_articles! self.articles

I am getting following error even after starting forreman and starting sunspot:solr : RSolr::Error::InvalidRubyResponse - 200 OK Error: <result status="1">java.lang.NullPointerException at org.apache.solr.handler.XmlUpdateRequestHandler.doLegacyUpdate(XmlUpdateRequestHandler.java:129) at org.apache.solr.servlet.SolrUpdateServlet.doPost(SolrUpdateServlet.java:87) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet

developers! I can't understand next situation For Example I have model class Pg::City < ActiveRecord::Base belongs_to :country #virtual accessors attr_accessor :population #attr_accessible :city, :isdisabled, :country_id end I can use code like this: c = Pg::City.new({:population=>1000}) puts c.population 1000 But if I uncomment attr_accessible code above throw warning WARNING: Can't mass-assign protected attributes: population How can I use virtual attributes for mass-assigmnment together with model attributes? Thanks! Using attr_accessor to add a variable does not automatically add it to

I have upgraded from Rails 3.2 to Rails 4 by following the Ruby Screencast guide. My tests are running and the server starts, yet I receive an error when I send a request: ERROR NoMethodError: undefined method `tagged' for #<Formatter:0x000000057f5dc8> /home/mahoni/.rvm/gems/ruby-2.0.0-p195/gems/activesupport-4.0.0/lib/active_support/tagged_logging.rb:67:in `tagged' /home/mahoni/.rvm/gems/ruby-2.0.0-p195/gems/railties-4.0.0/lib/rails/rack/logger.rb:21:in `call' /home/mahoni/.rvm/gems/ruby-2.0.0-p195/gems/quiet_assets-1.0.2/lib/quiet_assets.rb:18:in `call_with_quiet_assets' /home/mahoni/.rvm

Trying to create an instance of a model, I get the following error... u = User.create # or .where(...).first_or_create # or .where(...).first_or_initialize ArgumentError: wrong number of arguments (2 for 1) Is anyone having the same problem with Rails 3.2? Have you overloaded your model's initialize method? In my case, I had overloaded it with: def initialize(attributes=nil) ... end Which I had to fix to: def initialize(attributes = nil, options = {}) ... end In Rails 3.2, the commit 7c5ae0a88fc9406857ee362c827c57eb23fd5f95 (Added mass-assignment security :as and :without_protection support to