On Sat, Oct 16, 2010 at 9:51 AM, Bobby Johnson wrote:
> Not yet, I am still fighting with it. Mostly my newbishness around how to
> debug these problems in ruby, so at least it's a learning experience.
> Jim's response was pretty helpful in clarifying exactly what the problem was
> and helping me
Not yet, I am still fighting with it. Mostly my newbishness around how to
debug these problems in ruby, so at least it's a learning experience.
Jim's response was pretty helpful in clarifying exactly what the problem was
and helping me to understand the radiant environment. The feed me directions
Had you any luck with extension ?
I'd like to use it and doesn't really want to dive into that right
now...
Regards
On Sep 27, 3:56 pm, Bobby Johnson wrote:
> Hi Jim,
>
> Thanks for the response. I am currently using Radiant (0.9.1) which I was
> under the impression was Rails 3 compliant. I may
Hi Jim,
Thanks for the response. I am currently using Radiant (0.9.1) which I was
under the impression was Rails 3 compliant. I may have misread that. Thanks
for the pointers to other version of AWS, I will give them a shot.
Thanks again,
Bobby
On Sun, Sep 26, 2010 at 10:58 AM, Jim Gay wrote:
I'm not very familiar with ActionWebService, but you could check other
forks for support of rails 3
http://github.com/datanoise/actionwebservice/network
Are you running the rails 3 branch of radiant? Because we bundle rails
2.3.8 with the current gem (0.9.1)
On Fri, Sep 24, 2010 at 8:12 AM, Bobby
Ok, so I have dug in a bit more and it looks like ActionWebServive was
replaced with ActionResource which is intended to provide RESTful interfaces
of your ActiveRecord entities. Not sure how to make ActionResource conform
to the metablogapi xmlrpc api. But I am digging more. Are there any good
doc
