Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

cainlevy's latest activity

Tuesday, December 01 2009
3113 ActionMailer only works correctly with sent_on set in in the local time zone was updated in Ruby on Rails
  • cainlevy
    • Tag changed from 2-3-stable, actionmailer, timezone to 2, actionmailer, bugmash-patch, timezone
    by cainlevy at 10:01 PM
Friday, October 09 2009
3113 ActionMailer only works correctly with sent_on set in in the local time zone was updated in Ruby on Rails
  • cainlevy
    • Tag changed from actionmailer, timezone to 2-3-stable, actionmailer, timezone
    by cainlevy at 10:57 PM

    Fixed the problem for me. +1

Tuesday, September 08 2009
2761 avoid calling #valid? on destroyed associated records was updated in Ruby on Rails
  • cainlevy
    cainlevy commented at 8:08 PM

    Looks like it didn't make it in. Bump to next milestone?

Thursday, June 04 2009
2761 avoid calling #valid? on destroyed associated records was updated in Ruby on Rails
  • cainlevy
    cainlevy commented at 11:00 PM

    It'd probably help if I hadn't commented out the code that, you know, does stuff.

    Eloy also suggested aliasing #frozen? to #destroyed? for better semantics.

  • cainlevy
    cainlevy created the ticket at 9:21 PM

    An associated record may be invalid in memory even though it has been destroyed in the database. This should not prevent the parent object from being valid.

Sunday, May 24 2009
2704 allow calltime list of allowed attributes for mass assignment was updated in Ruby on Rails
  • cainlevy
    cainlevy commented at 9:43 AM

    Yep. It would certainly be easy to distribute the assign() method via a plugin. It'd be much harder to extend the change to the other mass assignment methods fo...

  • cainlevy
    cainlevy commented at 8:13 AM

    Hey Koz, thanks for the reply --

    I certainly hope I'm not just creating complexity for everyone. How does this ticket do that? This change (ignoring #2705) is n...

2705 deprecate attr_accessible, attr_protected was updated in Ruby on Rails
  • cainlevy
    cainlevy commented at 8:25 AM

    True. The base case does cover a lot of ground. And until I finally did away with ActiveScaffold (the beast) and went back to a more light-weight admin interfac...

  • cainlevy
    cainlevy created the ticket at 4:16 AM

    This is a follow-up to #2704, which revisits mass assignment and one-ups attr_accessible and attr_protected. If that patch is accepted, then I don't see enough ...