On Nov 18, 2:55 pm, Nik B [email protected] wrote:
That’s the issue with (perhaps poor) design - it’s a temporary object
never stored on the server. It’s attributes are defined merely with
attr_accessor’s. At the end of the checkout process the virtual
attributes are stored on Authorize.NET, and the actual record
attributes are just an id and a customer_address_id which is used to
retrieve it on Authorize.
in that case I’d store a hash of those attributes in the session
Seems like perhaps it has something to do with the attributes_cache…
but I can’t find much information on how the attributes cache works.
Unlikely. attributes_cache is just to do with caching attributes that
are expensive to create (mostly datetimes)