Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Net-Twitter CPAN distribution.

Report information
The Basics
Id: 65506
Status: resolved
Priority: 0/
Queue: Net-Twitter

People
Owner: Nobody in particular
Requestors: znmeb [...] borasky-research.net
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 3.14002
Fixed in: (no value)



Download (untitled) / with headers
text/plain 1.1k
I'm getting errors from trends_location - the error I'm seeing looks something like this: {"request":"\/1\/trends\/location.json?woeid=1","error":"No data for WOEID location"} Here's the code: #!/usr/bin/perl -w use strict; use warnings; use Carp; use English qw(-no_match_vars); use Net::Twitter; my $handle = Net::Twitter->new(); my $available = $handle->trends_available; foreach my $entry (@$available) { my $name = $entry->{name}; my $woeid = $entry->{woeid}; print "${name} ${woeid}\n"; } my $object = eval {$handle->trends_location(1)}; if ($EVAL_ERROR) { print "Hello world"; } exit; I'm running this in Komodo - I can set breakpoints and dump things. It looks like what's happening is that the request getting built is http://api.twitter.com/1/trends/location.json?woeid=1 When I try that in http://app.apigee.com/console/twitter I get the same error: { "request" : "/1/trends/location.json?woeid=1", "error" : "No data for WOEID location" } What Apigee builds for this function is http://api.twitter.com/1/trends/{woeid}.json When I do this with {woeid} = 1, it works. I think Twitter changed the API - their documentation isn't quite clear.
Subject: trends_location broken
Download (untitled) / with headers
text/plain 416b
Fixed in 3.14003 I don't know if the API changed or if this was broken in the initial implementation. Seems likely the API changed based on the way the implementation read. I would have renamed trends_location to "trends" and kept the former as an alias, but "trends" is a method in the Search API which causes a conflict when both are used. So, trends_location it remains. Thanks for the bug report, Ed. -Marc


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.