/users/show/id.{json|xml} missing fields in the response

[Kevin Tronkowski]

I have recently noticed discrepancies with responses to the users/show/
id.{json|xml} API call and was not able to find mention of it in this
group or in the API documentation.

What I have noticed is that depending on what user is specified, some
of the fields (everything between <followers_count> and <status> in
the examples below) are missing in the response. I see this issue with
both with the xml and json return formats.

Here is an example of what I am seeing:

** complete response **

curl -u ID:PW http://twitter.com/users/show/yakkle.xml
<?xml version="1.0" encoding="UTF-8"?>
<user>
<id>10540282</id>
<name>Yakkle</name>
<screen_name>yakkle</screen_name>
<location>New England, USA</location>
<description>Yakkle is a the free, instant collaboration tool.</
description>
<profile_image_url>http://s3.amazonaws.com/twitter_production/
profile_images/37734742/yakkle64x64_normal.jpg</profile_image_url>
<url>http://www.yakkle.com</url>
<protected>false</protected>
<followers_count>20</followers_count>
<profile_background_color>9ae4e8</profile_background_color>
<profile_text_color>000000</profile_text_color>
<profile_link_color>0000ff</profile_link_color>
<profile_sidebar_fill_color>888888</profile_sidebar_fill_color>
<profile_sidebar_border_color>20cffe</profile_sidebar_border_color>
<friends_count>15</friends_count>
<created_at>Sun Nov 25 01:15:15 +0000 2007</created_at>
<favourites_count>2</favourites_count>
<utc_offset>-21600</utc_offset>
<time_zone>Central Time (US &amp; Canada)</time_zone>
<profile_background_image_url>http://s3.amazonaws.com/
twitter_production/profile_background_images/2327338/background.gif</
profile_background_image_url>
<profile_background_tile>false</profile_background_tile>
<following>false</following>
<notifications>false</notifications>
<statuses_count>25</statuses_count>
<status>
<created_at>Fri Jun 20 18:29:18 +0000 2008</created_at>
<id>839717387</id>
<text>@hmross Thanks. We have seen that on some (small portion) of
computers with our client (and others). We will take another look for
you.</text>
<source>web</source>
<truncated>false</truncated>
<in_reply_to_status_id>839065892</in_reply_to_status_id>
<in_reply_to_user_id>14446249</in_reply_to_user_id>
<favorited></favorited>
</status>
</user>

** incomplete response **

curl -u ID:PW http://twitter.com/users/show/leolaporte.xml
<?xml version="1.0" encoding="UTF-8"?>
<user>
<id>3829151</id>
<name>Leo Laporte</name>
<screen_name>leolaporte</screen_name>
<location>I St </location>
<description>I've experiments to run, there is research to be done,
on the people who are watching TWiT Live.</description>
<profile_image_url>http://s3.amazonaws.com/twitter_production/
profile_images/52691463/leo65x75_normal.jpg</profile_image_url>
<url>http://leoville.com</url>
<protected>false</protected>
<followers_count>46618</followers_count>
<status>
<created_at>Wed Jul 09 02:45:09 +0000 2008</created_at>
<id>853367892</id>
<text>Karl Susman - @karlwireless - is working on a Santa Monica
meetup at the 3rd St Apple Store Friday for the iPhone launch.</text>
<source>&lt;a href="http://www.twhirl.org/"&gt;twhirl&lt;/a&gt;</
source>
<truncated>false</truncated>
<in_reply_to_status_id></in_reply_to_status_id>
<in_reply_to_user_id></in_reply_to_user_id>
<favorited></favorited>
</status>
</user>


Thanks in advance for helping to clarify why this is happening,
Kevin

[Evan Weaver]

I know what's happening; it is a cache cross-pollination problem. I
will fix it.

Evan

--
Evan Weaver

[Kevin Tronkowski]

Evan,

Cool, thanks!

Kevin

On Jul 9, 12:23 pm, "Evan Weaver" <ewea...@twitter.com> wrote:
>  I know what's happening; it is a cache cross-pollination problem. I
> will fix it.
>
>  Evan
>
> On Wed, Jul 9, 2008 at 10:25 AM, Kevin Tronkowski
>
>
>
>
>
> <Kevin.Tronkow...@gmail.com> wrote:
>
> > I have recently noticed discrepancies with responses to the users/show/
> > id.{json|xml} API call and was not able to find mention of it in this
> > group or in the API documentation.
>
> > What I have noticed is that depending on what user is specified, some
> > of the fields (everything between <followers_count> and <status> in
> > the examples below) are missing in the response. I see this issue with
> > both with the xml and json return formats.
>
> > Here is an example of what I am seeing:
>
> > ** complete response **
>

> > curl -u ID:PWhttp://twitter.com/users/show/yakkle.xml

> > curl -u ID:PWhttp://twitter.com/users/show/leolaporte.xml

> Evan Weaver- Hide quoted text -
>
> - Show quoted text -

[Steven Ghyselbrecht]

Is this issue already fixed? Or has this nothing to do with the empty
favorited-field?

Thanks in advance,

Steven

On 9 jul, 18:23, "Evan Weaver" <ewea...@twitter.com> wrote:
>  I know what's happening; it is a cache cross-pollination problem. I
> will fix it.
>
>  Evan
>
> On Wed, Jul 9, 2008 at 10:25 AM, Kevin Tronkowski
>
>
>
> <Kevin.Tronkow...@gmail.com> wrote:
>
> > I have recently noticed discrepancies with responses to the users/show/
> > id.{json|xml} API call and was not able to find mention of it in this
> > group or in the API documentation.
>
> > What I have noticed is that depending on what user is specified, some
> > of the fields (everything between <followers_count> and <status> in
> > the examples below) are missing in the response. I see this issue with
> > both with the xml and json return formats.
>
> > Here is an example of what I am seeing:
>
> > ** complete response **
>

> > curl -u ID:PWhttp://twitter.com/users/show/yakkle.xml

> > curl -u ID:PWhttp://twitter.com/users/show/leolaporte.xml

[Colby Palmer]

I am still seeing the users/show/id.json API method missing this
information for *some* users:

profile_background_color
profile_text_color
profile_link_color
profile_sidebar_fill_color
profile_sidebar_border_color
friends_count
created_at
favourites_count
utc_offset
time_zone
profile_background_image_url
profile_background_tile
following
notifications
statuses_count
status/source
status/truncated
status/in_reply_to_status_id
status/in_reply_to_user_id

The XML returns seem consistent, except they have an empty "status/
favorited" field where the JSON files do not. Are there plans to
remedy this?

Thanks,
Colby



On Jul 11, 2:35 pm, Steven Ghyselbrecht

<steven.ghyselbre...@gmail.com> wrote:
> Is this issue already fixed? Or has this nothing to do with the empty
> favorited-field?
>
> Thanks in advance,
>
> Steven
>
> On 9 jul, 18:23, "Evan Weaver" <ewea...@twitter.com> wrote:
>
> >  I know what's happening; it is a cache cross-pollination problem. I
> > will fix it.
>
> >  Evan
>
> > On Wed, Jul 9, 2008 at 10:25 AM, Kevin Tronkowski
>
> > <Kevin.Tronkow...@gmail.com> wrote:
>
> > > I have recently noticed discrepancies with responses to theusers/show/
> > > id.{json|xml} API call and was not able to find mention of it in this
> > > group or in the API documentation.
>
> > > What I have noticed is that depending on what user is specified, some
> > > of the fields (everything between <followers_count> and <status> in
> > > the examples below) are missing in the response. I see this issue with

> > > both with the xml andjsonreturn formats.

[Alex Payne]

Yes. You can find our list of issues at
http://code.google.com/p/twitter-api/issues/list

--
Alex Payne
http://twitter.com/al3x

[Colby Palmer]

Awesome, thanks!


On Jul 21, 2:15 pm, "Alex Payne" <a...@twitter.com> wrote:
> Yes.  You can find our list of issues athttp://code.google.com/p/twitter-api/issues/list

[Derek Gathright]

Not sure if this is related or not, but it has to do with JSON caching for the "showUser" method, so seems like a good place to post it.  

So I just updated my profile bio & pic, and while the XML feed this method is up to date, the JSON feed still has the old data and it's been about an hour.  Is this a bug or by design?  If by design, I'll have to update the code to grab the XML feed.  If bug I'll just wait for a fix cause it isn't a very big deal.

[Alex Payne]

Changing your profile bio and pic won't cause a cache invalidation.
So, this is by design.

--
Alex Payne
http://twitter.com/al3x

[Derek Gathright]

Thanks for the clarification.