I started this project back in February of last year(!) and was pulled off of it for over half of 2019, so after an entirely too long dev cycle, I am pretty stoked to let you guys know about this.
If I was to zero in on what makes v5 so much better than v4, it's that it's all about density and consistency. I spent a lot of time making things consistent across all media types and pages. Everything finally feels like it's a lot more at home and where it belongs. This is also a design that can scale with some of the new data we plan to start incorporating over the next few years.
While it is mostly feature complete, I am aware of a few lingering issues. They are as follows:
If you see something that is clearly wrong, by all means feel free to mention it below. I need more eyes on this, so just use it as you see fit and I'll be spending the next few weeks wrapping everything up.
My goal is to have this launched in production sometime in the next few weeks.
Thanks as always!
Update on March 27: v5 is now live on production!! This has been the longest and hardest thing I have ever pulled off in the past 11 years building TMDb. Of course there's still work to be done, and we're not stopping here but I'm taking a breather for the weekend. Hope everyone is staying safe out there, feel free to reply to this thread with issues if they crop up. Thanks as always.
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de 没有了遇见
le 29 février 2020 à 22h07
Does this version solve the problem of no access to API in China
Réponse de lemonred
le 2 mars 2020 à 20h17
Countries and languages are showing Brazilian Portuguese translations when content language is set to Portuguese (pt-PT). Could you please correct them?
Can these changes be done by a user? I've tried to update tmdb-web-translations/countries/pt-PT.yml, but I'm not sure if I've done it properly. (Sorry.)
Réponse de Philippe LeMarchand
le 3 mars 2020 à 10h47
Bug: The "Discussion Activity" box when you click "View Activity" in v5 is empty.
I'm also unconvinced by the colour scheme, but that could just be the shock of the new!
Réponse de PT 100
le 3 mars 2020 à 12h50
Agreed. Blue is my favorite color (and the favorite of most people), but I'd much prefer either a Ford Bright Blue or a softer/more muted Royal Blue. The aqua is meh.
Réponse de ticao2 🇧🇷 pt-BR
le 3 mars 2020 à 14h23
I went to the Translations page in v5 and saw that next to each language is the language-COUNTRY code.
In the case of the Portuguese language we see:
Chinese (zh-CN)
Chinese (zh-HK)
Chinese (zh-TW)
French (fr-CA)
French (fr-FR)
Portuguese (pt-BR)
Portuguese (pt-PT)
See here: https://v5.themoviedb.org/movie/419704-ad-astra/translations?language=pt-BR
Is this how it appears to you?
Réponse de lemonred
le 3 mars 2020 à 14h50
Yes, I'm seeing the same thing, but in Portuguese. (According to that page, Ad Astra has 42 translations, some of them empty.)
But some of the languages are written in Brazilian Portuguese. And the same happens with the production countries.
Réponse de ticao2 🇧🇷 pt-BR
le 3 mars 2020 à 15h12
@lemonred
I think I understand what the problem is. Correct me if I'm wrong.
I am from Brazil and the language selected in my profile is pt-BR.
When I enter the Translations page, the entire interface is in English.
I am assuming that the pt-BR language has not yet been added or configured.
When I change the language of my profile to pt-PT, then the language of the TMDb interface is in Portuguese.
You are saying that the language is pt-BR and not what it should be, pt-PT.
It is likely that pt-PT is replaced by pt-BR.
And pt-BR, not implemented.
Can you quote 4 or 6 words from the interface that are different between pt-PT and pt-BR?
Just to be able to more easily identify when the interface languages are switched.
EDIT
If possible also 4 or 5 examples of different country names in pt-PT and pt-BR.
Réponse de ticao2 🇧🇷 pt-BR
le 3 mars 2020 à 15h42
@lemonred
It seems that this problem has already been fixed pt-PT and pt-BR.
Can you confirm that?
Réponse de lemonred
le 3 mars 2020 à 16h15
@ticao2
This list shows the countries that have a different name or spelling in pt-PT and pt-BR: https://github.com/travisbell/tmdb-web-translations/pull/6/commits/282ad3609a414ea6b2c31e1df1859dddc548ee08
I can do a similar list with languages.
Réponse de Travis Bell
le 3 mars 2020 à 16h49
@ticao2 Compare that to the
pt-BR
translations: https://github.com/travisbell/tmdb-web-translations/blob/master/countries/pt-BR.yml@lemonred Your pull request is the right way to do it. I will merge it shortly. Thanks for the contributions.
Réponse de ticao2 🇧🇷 pt-BR
le 3 mars 2020 à 22h38
@lemonred
Understand. So the list of countries in pt-BR was being used for pt-PT.
A single correction.
It looks like you removed the quotes from Norway's 'NO'.
I think the quotes must be there for another reason.
Perhaps not to be confused with NO Coubtry. Or some other reason.
@travisbell , am I wrong?
Réponse de Travis Bell
le 3 mars 2020 à 23h07
The quotes do need to be there, ya.
NO
/no
is a reserved word in YAML.Réponse de lemonred
le 4 mars 2020 à 13h25
@ticao2 @travisbell Thanks. And sorry for my mistake.
Réponse de Philippe LeMarchand
le 7 mars 2020 à 07h45
Getting used to the blue, but missing the separate search bar. A search takes an extra press!
I've always felt that the search should be a bit "fuzzier" though - one incorrect letter and it throws it.
Réponse de Travis Bell
le 7 mars 2020 à 11h00
Re: blue, good stuff. I've been using v5 for so long now that when I got back to the old site, it feels old and cramped and unorganized.
Re: extra press, it actually doesn't! It was one click before (right on the bar) and it's still one click. Clicking the search icon focuses the search bar, so it's one click in both sites. Pro tip: when you're on a computer, you can tap the letter
s
and it will auto focus the search bar as well. I often find it easier to use the keyboard, than move the mouse around.Yes, this is something I will be adding this year at some point, but don't have time to include as part of v5. I get bit by this as well and am aware that it needs to be better.