Closed jwoertink closed 10 years ago
This is expected behavior and all actions should be called on the real_
object :) The problem with this gem is that we are using active resource that feels much like active record. This causes a lot of confusion.
This is more of a shout out just so others will know what to do if they stumble on this as well.
Thanks for the report!
If you find a subscription through a customer, then methods like cancel, and reactivate won't exist. This is shown through
It looks like there are two different Subscription classes due to the scope.
So calling cancel on subscription would throw an error, but calling cancel on real_subscription would work fine.