search for: fightonfightw

Hello! Sometime ago I ran across a webpage where someone had identified the full callback sequence for an object lifecycle including AASM with it''s :enter and :exit and whatnot callbacks. Unfortunately, I can''t find it and searches don''t seem to help. Does anyone have a reference to a page that shows the callback sequence with Acts As State Machine (the gem)? I think

So I''m happy to see that ActionMailer supports layouts now (it may have for a while, but I just now realized it). But I don''t see a way to turn them off selectively or by multipart type. For example, if I have a layout that''s really simple in "layouts/ email.html.erb": <div style="border:1px solid gray"> <%= yield %> </div> I

There''s got to be an easier way... I am building an event manager and as part of it, the user selects the time zone of the event from a drop-down list using the time_zone_select helper. This is stored in the events table as a string. Because of legacy data which is stored in UTC, I want to keep the dates and times in the table as UTC but when I display it, I want to show the abbreviated

I''m sending plain text and html emails by having multiple files for each email I send. For example, for my registration email I have a registration.text.plain.erb file and a registration.text.html.erb file. I want to use a layout for the html version of my emails. In my mailer I put: class AccountsMailer < ActionMailer::Base layout ''email'' ... end

Hi all: For example I have: class Color < ActiveRecord::Base belongs_to :ball end class Ball < ActiveRecord::Base has_many :colors end What I want to do is to write a method that: 1. takes the result of Ball#colors, which is an array of Color objects 2. do something with the array 3. return the result but I want to name my method Ball#colors, i.e. I want to overload the generated

Acts_as_soft_deletable is a rails plugin that provides the ability to soft delete or disable models. When models are destroyed, they will be archived so that they can later be restored easily. Its similar to acts_as_paranoid but uses a different approach that should make it a little more foolproof. See the README at the following url for a better description. github url:

Considering an object with several has_many :through => associations, what is the ''best'' way to handle validations? As an example: class Student < ActiveRecord::Base # some attrbutes like # :name # :grade # relationships has_many :students_assignment, :dependent => :destroy has_many :assignments, :through => :students_assignment has_many

We''re developing a system that''s used for tracking company IPO data and we''re running into a few number storage issues. For large numbers, i.e. numbers greater than 100 million, MySQL insists on storing these as scientific notation. I don''t really have a problem with that but when we want to edit these fields using something like: <% form_for(@company) do