Starting with Paperclip version 4.0, all attachments are required to include a content_type validation, a file_name validation, or to explicitly state that they’re not going to have either. Paperclip raises Paperclip::Errors::MissingRequiredValidatorError error if you do not do any of this. In your case, you can add any of the following line to your Post model, … Read more
Rails 4+: Article.where.not(title: [‘Rails 3’, ‘Rails 5’]) Rails 3: Topic.where(‘id NOT IN (?)’, Array.wrap(actions)) Where actions is an array with: [1,2,3,4,5]
You should read that, it’s still valid. You’ll adapt the function you use depending on your needs. Basically: if you already load all entries, say User.all, then you should use length to avoid another db query if you haven’t anything loaded, use count to make a count query on your db if you don’t want … Read more
You’ll probably have to be more verbose here name = “Blue Jeans” model = Product.where(‘lower(name) = ?’, name.downcase).first model ||= Product.create(:name => name)
To exit Pry unconditionally, type exit-program Edit from @Nick’s comment: Also works: !!!
I think this may solve your problem: in config/application.rb: config.autoload_paths << Rails.root.join(‘lib’) and keep the right naming convention in lib. in lib/foo.rb: class Foo end in lib/foo/bar.rb: class Foo::Bar end if you really wanna do some monkey patches in file like lib/extensions.rb, you may manually require it: in config/initializers/require.rb: require “#{Rails.root}/lib/extensions” P.S. Rails 3 Autoload … Read more
hash[:new_key] = hash.delete :old_key
The API docs on link_to show some examples of adding querystrings to both named and oldstyle routes. Is this what you want? link_to can also produce links with anchors or query strings: link_to “Comment wall”, profile_path(@profile, :anchor => “wall”) #=> <a href=”http://stackoverflow.com/profiles/1#wall”>Comment wall</a> link_to “Ruby on Rails search”, :controller => “searches”, :query => “ruby on … Read more
If your model is really “responsible” for the constants you should stick them there. You can create class methods to access them without creating a new object instance: class Card < ActiveRecord::Base def self.colours [‘white’, ‘blue’] end end # accessible like this Card.colours Alternatively, you can create class variables and an accessor. This is however … Read more
You can use helpers.<helper> in Rails 5+ (or ActionController::Base.helpers.<helper>) view_context.<helper> (Rails 4 & 3) (WARNING: this instantiates a new view instance per call) @template.<helper> (Rails 2) include helper in a singleton class and then singleton.helper include the helper in the controller (WARNING: will make all helper methods into controller actions)