The Movie Database Support
Support → API Support
Bug: Person profile_path set in search result, but not in individual lookup
posted by matthias_kSTAFFMOD on July 6, 2013 at 1:52 PM
Compare:
> curl "http://api.themoviedb.org/3/search/people?query=brad+grey"
{
"page": 1,
"results": [
{
"adult": false,
"id": 1298,
"name": "Brad Grey",
"popularity": 2.8,
"profile_path": "/7PntYF8xh3wqBEn7YvOXeovrk5R.jpg"
}
],
"total_pages": 1,
"total_results": 1
}
with:
> curl "http://api.themoviedb.org/3/person/1298
{
"adult": false,
"also_known_as": [
],
"biography": null,
"birthday": "1957-12-29",
"deathday": null,
"homepage": null,
"id": 1298,
"imdb_id": "nm0340522",
"name": "Brad Grey",
"place_of_birth": null,
"popularity": 2.8,
"profile_path": null
}
why would profile_path be missing in the full person resource?
Reply by Travis Bell
on July 6, 2013 at 4:24 PM
Not sure but the website isn't showing an image either. Neither the search results or the full person page.
I'm not sure where the API search is getting that profile from, I'll have to dig into it. I've created a new ticket for this but am busy with some fairly large feature work and won't be looking at this for a month or two.
Cheers.
Reply by matthias_k
on July 7, 2013 at 4:50 AM
Okay fair enough. Thanks for tracking it as an issue. Meanwhile, do you have a feeling for how many records might be affected? Is this something I will see all over the place or is this an edge case? I picked up work again on an Android frontend for TMDB that I had parked for a few months, and I don't remember having this issue before.
Reply by Travis Bell
on July 7, 2013 at 2:15 PM
I wouldn't have much of an idea as this is the very first time anyone has reported it since v3 went live 2 years ago. Given that though, I would say not very common.