Hi skt,
First of all: I would highly encourage you to upgrade immediately to at least
3.0.20.
Second: What method are you calling exactly to get that error?
On Wed, Sep 3, 2014 at 2:35 PM, skt wrote:
> Hello,
> I am on an old version of Rails (3.0.5) and can't upgrade right now. When I
Hello,
I am on an old version of Rails (3.0.5) and can't upgrade right now. When I
try to use assign_attributes on a model I get the error that the method is
not found as below
NoMethodError - undefined method `assign_attributes' for
#:
activemodel (3.0.5) lib/active_model/attribute_methods.
There's an interesting idea, but since yaml is fairly standard I would suggest
you'd to better to package this up as a Gem.
On Aug 29, 2014, at 1:32 PM, Laurent Arnoud wrote:
> It's more easy to use json file with other languages like javascript for
> example.
> I join the patch I've done
Please submit a pull request. We usually don't use json as configuration
file but I don't see why not accept your patch.
Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca
On Fri, Aug 29, 2014 at 2:32 PM, Laurent Arnoud
wrote:
> It's more easy to use json fi
We don't have plans to backport it. We worked to make upgrading to Rails
4.2 an easy task so it would not require to us maintain old Rails versions.
That said I don't see a good reason to us maintain a backported feature.
On Sep 2, 2014 12:23 PM, "Andrew Kane" wrote:
> Hey,
>
> Any plans to backp
Hey,
Any plans to backport Active Job to earlier versions of Rails? This would
be super useful for external gems that do asynchronous tasks (exception
reporting, geocoding, etc). If not, I'll take a stab at it.
Thanks,
Andrew
[originally incorrectly posted in Ruby on Rails: Talk]
--
You re
It's more easy to use json file with other languages like javascript for
example.
I join the patch I've done for make it work.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from
Looking over the callback order I am thinking it would be nice to simplify
things.
The current callback list is as follows
before_validation
- validate
after_validation
before_save
around_save
before_create/update
around_create/update
- sa
Looking over the callback order I am thinking it would be nice to simplify
things.
The current callback list is as follows
**
before_validation
- validate
after_validation
before_save
around_save
before_create/update
around_create/update
- save
after_c
