We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original issue 2673 created by Omertron on 2013-09-03T21:03:00.000Z:
I think kinopoisk again change database
kinopoisk.ru have 2 type certification (russian and mpaa) for examle http://www.kinopoisk.ru/film/484599/
In properties set:
kinopoisk.russianCertification=true
Sometime was fine and plugin get russian certification, but today I rescan base and get mpaa certification
string from updated xml <certification source="KINOPOISK">PG-13</certification>
correct string should be <certification source="KINOPOISK">age12</certification>
I tried on working and fresh configurations
yamj 2.10 r3731
The text was updated successfully, but these errors were encountered:
Comment #1 originally posted by Omertron on 2013-09-04T04:15:19.000Z:
<empty>
Sorry, something went wrong.
Comment #2 originally posted by Omertron on 2013-09-04T04:40:06.000Z:
This issue was closed by revision r3732.
Comment #3 originally posted by Omertron on 2013-09-04T11:55:17.000Z:
Thanks Ilgizar, everything is working fine now. Thank you very much.
Omertron
No branches or pull requests
Original issue 2673 created by Omertron on 2013-09-03T21:03:00.000Z:
I think kinopoisk again change database
kinopoisk.ru have 2 type certification (russian and mpaa)
for examle http://www.kinopoisk.ru/film/484599/
In properties set:
kinopoisk.russianCertification=true
Sometime was fine and plugin get russian certification, but today I rescan base and get mpaa certification
string from updated xml
<certification source="KINOPOISK">PG-13</certification>
correct string should be
<certification source="KINOPOISK">age12</certification>
I tried on working and fresh configurations
yamj 2.10 r3731
The text was updated successfully, but these errors were encountered: