php-tmdb / api Goto Github PK

Hi :)
i don't know if it's a problem, or if i haven't understand how this API call works, but if i do this request:

$token  = new \Tmdb\ApiToken(TMDB_API_KEY);
$client = new \Tmdb\Client($token);

$movieChanges = $client->getChangesApi()->getMovieChanges(array(
    'page' => 1,
    'from' => '18-06-2014',
    'to'   => '19-06-2014'
));

var_dump($movieChanges);

or this:

$token  = new \Tmdb\ApiToken(TMDB_API_KEY);
$client = new \Tmdb\Client($token);

$movieChanges = $client->getChangesApi()->getMovieChanges(array(
    'page' => 1,
    'from' => '10-10-2012',
    'to'   => '14-10-2012'
));

var_dump($movieChanges);

return always 741 total result with always the same movie ids, i have also tried with this date format: YYYY-MM-DD, that is write in the TMDB API documentation, because you use this: MM-DD-YYYY and i can't understand what is the right format to send, and the result is always the same, with the same ids, i make some mistake?

thanks

Hi! It's me again :)
I want know if it's possible add a Language parameter for the Video request for a movie, for example this call:

$videos = $client->getMoviesApi()->getVideos(87421);

thanks!

See http://docs.themoviedb.apiary.io/#post-%2F3%2Flist%2F%7Bid%7D%2Fclear

Provide an easy way to supply the Language and Adult filter options, keeping in mind we might also need default image parameters ( e.g. size )

in \Tmdb\Model\Search\SearchQuery\TvSearchQuery()
this
$this->set('year', (int) $year);
should be
$this->set('first_air_date_year', (int) $year);

according to http://docs.themoviedb.apiary.io/#search and my own tests.

New Feature: Person search responses now have a 'known_for' array.

We've been working on ways to help find data better and more accurately and one of the requests we've got around people is that a 'known_for' array would be really helpful.

Starting yesterday, the popular person, person search and multi search methods now return more information for the person record. This is especially useful on the search methods. You can see example responses in the docs, or here, just try it yourself.

http://docs.themoviedb.apiary.io/reference/search/searchmulti/get
http://docs.themoviedb.apiary.io/reference/search/searchperson/get

I'm sure you can imagine where else we might extend this, like perhaps some extra info in the movie search results too. All in due time ;)

• Factories should be expanded I suppose, and the associated objects.

Cut off the dependency on the Guzzle library

To keep the library up to date we need to move on;

• Guzzle v4
• PHPUnit v4

This will deprecate php 5.3 support and will bump this up to 5.4

https://github.com/guzzle/retry-subscriber

https://www.themoviedb.org/documentation/api/status-codes

Every request will soon have these 3 headers:

X-RateLimit-Limit: 30
X-RateLimit-Remaining: 18
X-RateLimit-Reset: 1394060670

Helpers to obtain these headers should be available in Tmdb/Client.

Currently the state of logging & caching was merely a quick fix, while focusing on other things. There's a couple of issues that need to be addressed:

• The Client currently knows too much about these things and some methods should be removed.
• A custom implementation of the logger should be able to be passed through, with an own LogSubscriber we could depend on the Psr\LogInterface and make this compatible with whatever anybody's flavor is.
• I think the further caching methods should dissappear, in favor of explicitly registering these as EventSubscriber objects.

As caching is always enabled by default ( just following http protocols ), somehow an custom implementation should then also be forced to be on?

New Feature: TV shows and episodes now support account states

The following two methods are now hooked up and live.

https://api.themoviedb.org/3/tv/{ID}/account_states?api_key=###&session_id=###

https://api.themoviedb.org/3/tv/{ID}/season/{SEASON_NUMBER}/episode/{EPISODE_NUMBER}/account_states?api_key=###&session_id=###

This rounds off making the `account_states` available for the 3 main rateable objects in our db. Both of these are documented in the docs.

• Should be implemented at all levels

Hi,

Very good job ! So, I have a little request, when I load a movie with :

$repository = new \Tmdb\Repository\MovieRepository($client);
$movie = $repository->load([move_id]);

The movie object doesn't have information concerning "production_compagnies" and "production_countries". Whereas the The Movie Database API send this informations.

Thanks a lot

See documentation from http://guzzle.readthedocs.org/en/latest/plugins/cache-plugin.html

New Feature: The TV series content rating method is finally live. Check the docs for the details: http://docs.themoviedb.apiary.io/reference/tv/tvidcontentratings

Bug Fix: The popular person method wasn't paginating properly. This has been corrected.

• Expand the factory(ies?) and associated model(s)

Allow easier implementation for different Http libraries.

http://docs.themoviedb.apiary.io/#guestsessions

Maybe the best way to approach this is to take care of this under the hood provided the type of session was given.

New feature: Movie discover just got a nice upgrade!

We just added some really nice new sorting options (up to 14 now!) that we think are pretty awesome. Some of the queries you can build now are pretty darn powerful.

On top of the new sort options, we also added 7 new filters. You can now filter by primary_release_date.gte, primary_release_date.lte, vote_count.gte, vote_count.lte, with_cast, with_crew, with_people and with_keywords.

I started writing some example queries but you know what, there's just too many! Take a look at this page some examples:

https://www.themoviedb.org/documentation/api/discover

• Might be fun to provide some filters by default to use, especially for the less experienced folks, other than that there are no changes necessary.

http://docs.themoviedb.apiary.io/#get-%2F3%2Ftv%2Fairing_today

Currently the code is pretty tied up to Guzzle v3, to move things forward and make the code extendable to a higher level there should be a generic interface to replace Guzzle completely.

Planned adapters

• Guzzle v4

OriginCountry should be a GenericCollection of Country objects.

Allow the TMDB configuration API method to supply arguments to the ImageRepository and possibly the ImageHelper.

Continuing from #42 on wards, @mihaeu maybe you can create a generic outline?

http://docs.themoviedb.apiary.io/#timezones

• Implement an http adapter for Guzzle v4

Hi Micheal

I did see you have a Symfony2 bundle.
Do you have Laravel experience? If yes, do you plan to make a bundle for Laravel?

Regards

Should contain a GenericCollection with CastMember's.

• Make sure image related objects provide relevant methods, and refactor them to be more explicit ( Image\Poster becomes Image\PosterImage ).
• Extract duplicate code and provide a generic entry for hydration.

Should review on both the API and Repository levels all methods are implemented.

#54
#55
#56
#57
#58
#59

Hi,
i love your library, really love it!
I want know if you will add the new feature of the TheMovieDB API to get the tagged people in images: /person/{id}/tagged_images.

Thanks!

• Reduce overhead in the factories, and make them cleaner.
• Allow modifying collections before they are returned.
• Allow modifying requests and responses.

Make sure the TV languages hydration includes proper objects for the languages returned ( currently just an array ).

Hey guys, we deployed a few things this morning:

1. Fixed creating lists via the API (this works again)
2. Added a 'origin_country' to TV search results
3. Added a `production_companies` field to the TV info method
4. Added `first_air_date` to person crew credit methods
5. Exposed the TV certification list method

Everything has been updated and added to the docs, so be sure to take a look.

• Implementation at factory levels and objects I