The Parental Control doesn't work after installation of build 3.0.5168.16132

[Dan64 30]

Here the MBT Screenshot

 

[Dan64 30]

Here the Web Client screenshot

 

[Dan64 30]

Is all already specified in the title. After the installation of the new build 3.0.5168.16132 the parental control doesn't work. All the films are shown indipendently of the assigned rating.

 

 

[Luke 42077]

can you provide a specific example, with screenshots. thanks.

[oldschool 16]

Same here - restrictions not working for the users.

[Dan64 30]

Here some screenshot

 

 

 

 

 

[Luke 42077]

Does the issue occur in the web client?

[Dan64 30]

I'm able to see all the films using: MBC, MBT and the Web Client.

Edited February 25, 2014 by Dan64

[ebr 16170]

I haven't seen this exact scenario but I have found a lot of my movies missing their ratings and I have to go manually refresh them to bring the rating in.

[Abobader 3464]

I haven't seen this exact scenario but I have found a lot of my movies missing their ratings and I have to go manually refresh them to bring the rating in.

 

Yes, same issue here as well.

[ebr 16170]

I haven't seen this exact scenario but I have found a lot of my movies missing their ratings and I have to go manually refresh them to bring the rating in.

 

Something I'm noticing in trying to fix this.  On some of my movies that are properly identified but missing the rating, refreshing brings the rating in.  On others, it doesn't.  When I go to tmdb on the ones that don't the rating information is actually missing from all the release info out there too.

 

What may be going on here is tmdb lost a bunch of this information and is in the process of re-adding it.  So, a couple days ago there was no rating but now there is (for some of them).  That is all conjecture but plausible.

[Abobader 3464]

hmm, I did not check about that Ebr, since waiting for library scan to finish.

[oldschool 16]

When I changed folder types from mixed content to movies and TV, the parental rating worked on those folders.

[oldschool 16]

This is an interesting quirk. I confirmed that a movie with an official rating above a restriction was being shown on a restricted account, but once I set a custom rating, the movie was filtered out of the list. It looks like this bug only applies to metadata that does not have a custom rating assigned.

[ebr 16170]

No, I don't think it is exactly that because pretty much none of mine have custom ratings and it is working fine.  Gotta be something more obscure...

[Dan64 30]

My folders have already the correct type. I have also tried to remove and re-add the library to force the rebuild. But this trick doesn't work on my installation. I can confirm that the only way to force the respect of the restriction is to use the Custom rating. 

 

If somebody can help me and suggest where to look in the source code, I will try to debug the server this week-end to see what is happening on my installation.

Edited February 27, 2014 by Dan64

[Dan64 30]

Here a Screenshot of the debug window. The comparison is performed on the variable CustomRatingForComparison (filled with PG), and seems that the variable OfficialRatingForComparison is ignored. I think that the problem here is that when the field CustomRating is blank is filled with the value of the Parent folder (named "Azione") that in this case was set to PG. Removing this value I was able to enforce the restrictions. I think that the logic here is too simple, when the value of CustomRating is empty should considered before the value of the OfficialRating, only if even this field is empty should taken into consideration the value of the parent folder.

 

Edited February 28, 2014 by Dan64

[Luke 42077]

Yea I suspected this was the reason, and i think I disagree. CustomRating is generally used as a means to block content. With what you're suggesting it would not be possible to block a whole tv series from a user simply assigning it a custom rating. You'd have to go and set the custom rating on the series and then every season and episode.

[Dan64 30]

In my case the problem was related mainly to the boxsets. In the old version of MB if in a boxset there were 3 films rated PG, R, PG-13 to the boxset was assigned (by default) the highest rating, blocking the possibility to navigate inside the boxset. To override this behaviour the only solution was to set the CustomRating of the boxset to the lowest rating (in this case PG). Then I decided to add the CustomRating PG to all folders and boxsets. After the migration to MB3 all these settings were in place and MB3 worked as expected giving me the ability to navigate inside all the folders and boxsets. It is with the installation of the last version of MB3 that the behaviour is changed. I do agree that the Custom Rating is used to override the OriginalRating, but this override should be applied to the same level. Using the previous example if to the boxset I assign a CustomRating of PG, the current version of MB3 will allow to play even the movies rated R, while with the previous version of MB3 this was not possible, that for me is a better behaviour.

 

In any case now I have removed all the CustomRating from the boxsets and folders and MB3 is respecting the restrictions.      

Edited March 1, 2014 by Dan64