hrm, back to square one then...

Abraham - the value of $users is:
2142731,14125623,15998931,19560364,16559320,17036420,14791918,16908659,5538992,14984281,20188175,14277276,111226850,14327961,20257060,94168006,107679193,54567920,18171797,8886022,16390772,69422500,171538302,818340,168929218,141333525,132534968,14124542,14408989,138293290,2039761,6752072,111896485,175801197,14912789,22907920,15099178,16583906,10870772,94269486,174521748,82002786,15395087,39407092,123734452,17193910,16362662,7762662,21514744,7596972,31563269,23147529,27440127,14337563,1528701,82497472,19251912,15292430,17005679,7192042,14600753,97484744,2023641,92086501,15447441,98735657,16950385,2023191,14411651,23111875,2900,15039436,14479810,16024218,57933102,8453452,18363508,16569530,21034443,17007607,7029452,54997124,47397228,15226527,18193201,22278762,15127641,14204449,60616288,16465359,10371312,15805506,14995035,27727035,19211127,35279958,18023868,9369722,8088412

That's 99 users, in what I believe to be the correct format.

I also ran a test with just 8088412 like this, with the same (blank)
result:
$users = 8088412;
$added = $connection->post("{$user->screen_name}/lists/$listid->id/
create_all", array('user_id' => $users));
print_r($added);


Since it seems like the 'create_all' call itself that's the problem, I
decided to run another test:
$blahblah = $connection->post("{$user->screen_name}/{$list->id}/
qhweoi", array('user_id' => $users));
print_r($blahblah);

This returned nothing, similar to my 'create_all' call.  Since
'qhweoi' is not a valid Twitter API call, I'm wondering if either
twitteroauth just doesn't do the "create_all" call for lists or if my
implementation of it is broken...

Thanks everyone!
-Jim

On Aug 23, 12:56 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> I'm filled with misinformation today.
>
> But after being set straight by my colleague Matt Harris, I can tell you
> that the correct end point for this method is in actuality:
>
> http://api.twitter.com/1/:user/:list_id/members/create_all.format
>
> Our list methods are obviously confusing in their lack of a distinguished,
> consistent namespace.
>
> Taylor
>
> On Mon, Aug 23, 2010 at 9:07 AM, Abraham Williams <4bra...@gmail.com> wrote:
> > Jim,
>
> > What is your value for $users?
>
> > Abraham
> > -------------
> > Abraham Williams | Hacker Advocate |http://abrah.am
> > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > This email is: [ ] shareable [x] ask first [ ] private.
>
> > On Mon, Aug 23, 2010 at 08:55, Jim Chevalier <jcheval...@gmail.com> wrote:
>
> >> Hello,
>
> >> Thanks for the clarification!
> >> It seems I'm still having trouble with the 'create_all' command.
>
> >> I've updated my code:
> >> $added = $connection->post("{$user->screen_name}/lists/$listid->id/
> >> create_all", array('user_id' => $users));
> >> print_r($added);
>
> >> This still has no output.
> >> I noticed you specified "/create_all.json" in your example, so I
> >> double checked and twitteroauth does default to having the response
> >> format as json.
> >> The 'create_all' call isn't just off at the moment, is it?...
>
> >> Thanks for your help,
> >> Jim
>
> >> On Aug 23, 10:51 am, Taylor Singletary <taylorsinglet...@twitter.com>
> >> wrote:
> >> > Hi Everyone,
>
> >> > Think we found a nasty documentation bug around lists here, and we'll
> >> get
> >> > them fixed as soon as we can.
>
> >> > I believe the issue here is that we haven't indicated a necessary path
> >> > component.
>
> >> > The API call should be to:
>
> >> > POSThttp://api.twitter.com/1/:user/lists/:list_id/create_all.json
>
> >> > Sorry about the confusion!
>
> >> > Taylor
>
> >> > On Sun, Aug 22, 2010 at 12:41 PM, Jim Chevalier <jcheval...@gmail.com
> >> >wrote:
>
> >> > > I'm getting no response from 'create_all' (
> >>http://dev.twitter.com/doc/
> >> > > post/:user/:list_id/create_all) when using twitteroauth (http://
> >> > > github.com/abraham/twitteroauth).
>
> >> > > This is the code that I'm using:
> >> > > $added = $connection->post("{$user->screen_name}/{$list->id}/
> >> > > create_all", array('user_id' => $users));
> >> > > print_r($added);
>
> >> > > Nothing is displayed; no error is provided.
> >> > > Other POST calls are functioning properly, and the 'members' (http://
> >> > > dev.twitter.com/doc/post/:user/:list_id/members) call is working just
> >> > > fine.
>
> >> > > So, you're not alone Aditya...
> >> > > -Jim
>
> >> > > On Aug 18, 9:30 pm, whizcreed <aditya.inter...@gmail.com> wrote:
> >> > > > Hi,
>
> >> > > > I am using ruby-auth gem to interact with twitter api.
>
> >> > > > Unfortunately in situation of an error I am unable to find out much
> >> > > > information on the cause.
>
> >> > > > I am facing quite a strange problem. Consider following output:
>
> >> > > > >> r = u.twitter.post("/adityaraj/19567361/members.json", "id" =>
> >> > > '35671043')
>
> >> > > > => {"slug"=>"ruby-on-rails", "name"=>"Ruby-on-rails", "uri"=>"/
> >> > > > adityaraj/ruby-on-rails", "subscriber_count"=>0, "member_count"=>8,
> >> > > > "mode"=>"public", "id"=>19567361, "full_name"=>"@adityaraj/ruby-on-
> >> > > > rails", "description"=>"", "user"=>{}, "following"=>false}
>
> >> > > > >> r = u.twitter.post("/adityaraj/19567361/create_all.json",
> >> "user_id" =>
> >> > > '35671043')
>
> >> > > > TwitterAuth::Dispatcher::Error: An error occurred processing your
> >> > > > Twitter request.
> >> > > >         from
> >> /home/aditya/work/twitter/vendor/plugins/twitter-auth/lib/
> >> > > > twitter_auth/dispatcher/shared.rb:35:in `handle_response'
> >> > > >         from
> >> /home/aditya/work/twitter/vendor/plugins/twitter-auth/lib/
> >> > > > twitter_auth/dispatcher/oauth.rb:22:in `request'
> >> > > >         from /var/lib/gems/1.8/gems/oauth-0.4.1/lib/oauth/tokens/
> >> > > > access_token.rb:44:in `post'
> >> > > >         from (irb):12
> >> > > >         from :0
>
> >> > > > I have tried using create_all method with multiple screen_names but
> >> no
> >> > > > luck.
>
> >> > > > API link:http://dev.twitter.com/doc/post/:user/:list_id/create_all
>
> >> > > > Can anyone please point out if there is any obvious mistake in this
> >> or
> >> > > > if you are able to make it work.
>
> >> > > > Regards,
> >> > > > Aditya Raj

Reply via email to