The Movie Database-ondersteuning

The API is returning the wrong release dates for movies, it is returning the most recent release date (often a physical release) for a given country. For example:

The API claims The Goonies is 2020 movie (UK) and Beetlejuice is a 2018 movie (UK).

Can the API please be updated so that only the original theatrical release date is retrieved? It seems really odd the API for TMDB would appear to be claiming films in the 1980's were only released a few months ago.

8 antwoorde (op blad 1 van 1)

Jump to last post

@ProjectVRD said:
API returning wrong release dates
The API is returning the wrong release dates for movies, it is returning the most recent release date (often a physical release) for a given country. For example:
The API claims The Goonies is 2020 movie (UK) and Beetlejuice is a 2018 movie (UK).
Can the API please be updated so that only the original theatrical release date is retrieved?
It seems really odd the API for TMDB would appear to be claiming films in the 1980's were only released a few months ago.

Receiving in response only "primary_release_date" depends on how the API Request was built.
Some people want to receive exactly these Bluray physical release dates.
So...

In order for someone to help you with API Request questions, it is critical that you post here the API Request you are using.
Remember to replace your Key with THE_KEY , or something like that.

@ticao2 said:

@ProjectVRD said:
API returning wrong release dates
The API is returning the wrong release dates for movies, it is returning the most recent release date (often a physical release) for a given country. For example:
The API claims The Goonies is 2020 movie (UK) and Beetlejuice is a 2018 movie (UK).
Can the API please be updated so that only the original theatrical release date is retrieved?
It seems really odd the API for TMDB would appear to be claiming films in the 1980's were only released a few months ago.

Receiving in response only "primary_release_date" depends on how the API Request was built.
Some people want to receive exactly these Bluray physical release dates.
So...

In order for someone to help you with API Request questions, it is critical that you post here the API Request you are using.
Remember to replace your Key with THE_KEY , or something like that.

Strangely enough I using the Plex media scraper and the devs there said it was upto TMDB to fix the problem. I can go back to them citing this discussion.

@ProjectVRD said:
Strangely enough I using the Plex media scraper and the devs there said it was upto TMDB to fix the problem. I can go back to them citing this discussion.

Can you post here the link to this conversation on the Plex Forum?


EDIT
In November 2019 something similar happened.
And it was corrected by Travis Bell.
At that time I realized the problem when using MediaElch for scraper.
Now, using MediaElch, everything is fine.
Is it happening again?

I'm not seeing anything strange about The Goonies or Beetlejuice on the API. Here's The Goonies as an example:

Request

$ curl -v "http://api.themoviedb.org/3/movie/9340?api_key=###"
*   Trying 65.8.64.81:80...
* Connected to api.themoviedb.org (65.8.64.81) port 80 (#0)
> GET /3/movie/9340?api_key=### HTTP/1.1
> Host: api.themoviedb.org
> User-Agent: curl/7.72.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json;charset=utf-8
< Content-Length: 1498
< Connection: keep-alive
< Date: Sun, 08 Nov 2020 17:24:47 GMT
< Server: openresty
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: GET, HEAD, POST, PUT, DELETE, OPTIONS
< Access-Control-Expose-Headers: ETag, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After, Content-Length, Content-Range
< Cache-Control: public, max-age=21600
< x-memc: HIT
< x-memc-key: e2e8f1de05b763d0580ab5f07e8a1d4c
< x-memc-age: 17080
< x-memc-expires: 4520
< ETag: W/"af438dda184b21a609f0f28e6fbf99ec"
< Last-Modified: Sun, 08 Nov 2020 17:24:47 GMT
< Vary: Accept-Encoding,Accept-Encoding,Accept-Encoding
< X-Cache: Miss from cloudfront
< Via: 1.1 c3c2330b03b76e8da8566ca59448eb19.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: YVR50-C1
< X-Amz-Cf-Id: xg5xiD8j3xSpUCYpKcX7vd8toP7lCUpZnhy75-VCrhgdSaBTL3FkUg==
<
* Connection #0 to host api.themoviedb.org left intact

Response

{
  ...
  "id": 9340,
  "release_date": "1985-06-07",
  ...
}

The UK does have a "Physical" release added (see here), so this might have more to do with how you're querying the API.

What's the query you're making?

Sorry for the late response folks, here is the Plex conversation.

https://forums.plex.tv/t/plex-movie-database-scraper-pulling-the-wrong-release-date/649870

Gotta say, barring this (admittedly very rare) issue I am blown away at how well the TMDB API and Plex work together. My library looks absolutely fantastic and really professional thanks to all the hard work you are putting into this service.

@ProjectVRD said:
Sorry for the late response folks, here is the Plex conversation.
https://forums.plex.tv/t/plex-movie-database-scraper-pulling-the-wrong-release-date/649870

I went to read the question at the Plex Forum.
And I read the " xml output from PMS " files in .txt with the result of the API Request.
In these files I believe that what matters is the 2nd line: ```

We don't know what API request Plex sends to the TMDb Server.  
But the Request must be this:  
https://api.themoviedb.org/3/movie/9340?api_key=THE_KEY&language=en-US  
An information caught my attention:  

guid="com.plexapp.agents.themoviedb://9340?lang=en"

If they are only using " **en** ", this may be the problem.  
I don't know what programming language they are using.  
I think they should try to test the API Request using " **en-US** ".  
Perhaps that will solve the problem.  See this case similar to yours:  
https://www.themoviedb.org/talk/5fc33915cf9ba30042c1ee9d  
Regardless of all this, if you have an API Key, you can test it yourself and see the response that is sent.  
These are the possible variations of the API Request:  

https://api.themoviedb.org/3/movie/9340?api_key=THE_KEY&language=en-US
https://api.themoviedb.org/3/movie/9340?api_key=THE_KEY&language=en
https://api.themoviedb.org/3/movie/9340?api_key=THE_KEY

Just exchange **THE_KEY** for your **API Key**.

You edited your text and added this:

@ProjectVRD said:
Gotta say, barring this (admittedly very rare) issue I am blown away at how well the TVDB API and Plex work together. My library looks absolutely fantastic and really professional thanks to all the hard work you are putting into this service.

Just a correction.
TVDB (TV Data Base) is a traditional TV Series data provider.
Here you are on TMDB (The Movie Data Base).

@ticao2 said:

You edited your text and added this:

@ProjectVRD said:
Gotta say, barring this (admittedly very rare) issue I am blown away at how well the TVDB API and Plex work together. My library looks absolutely fantastic and really professional thanks to all the hard work you are putting into this service.

Just a correction.
TVDB (TV Data Base) is a traditional TV Series data provider.
Here you are on TMDB (The Movie Data Base).

My apologies, that was a typo. I meant TMDB, you guys. I'll edit again. :-)

Kan ’n rolprent of TV-program nie vind nie? Teken aan om dit te skep.

Globaal

s fokus op soekbalk
p open profielkieslys
esc sluit ’n oop venster
? open sneltoetsvenster

Op mediablaaie

b gaan terug (na ouer waar van toepassing)
e gaan na wysigblad

Op TV-seisoenblaaie

(regterpyl) gaan na volgende seisoen
(linkerpyl) gaan na vorige seisoen

Op TV-episodeblaaie

(regterpyl) gaan na volgende episode
(linkerpyl) gaan na vorige episode

Op alle beeldblaaie

a open beeldtoevoegvenster

Op alle wysigingsblaaie

t open vertaalkieser
ctrl+ s dien form in

Op besprekingsblaaie

n skep nuwe bespreking
w tokkel kykstatus
p tokkel openbaar/privaat
c tokkel maak oop/toe
a open aktiwiteit
r reageer op bespreking
l gaan na laaste reaksie
ctrl+ enter dien u boodskap in
(regterpyl) volgende blad
(linkerpyl) vorige blad

Instellings

Wil u hierdie item gradeer of tot ’n lys toevoeg?

Teken aan