Auto BoxSets - not displayed correctly in Dashboard

[CBers 7450]

Just noticed that some of my BoxSets don't display correctly in the Dashboard:

 

 

Is there an easy way to fix this, or is it just a case of delete and re-create ??

 

TIA.

 

 

.

Edited March 3, 2014 by CBers

[Tikuf 663]

Keith hit refresh and they should come back . But not sure why they are not there in the first place.

[CBers 7450]

Keith hit refresh and they should come back . But not sure why they are not there in the first place.

 

OK, I did that for one, but I have multiples.

 

Is there a quick way, or just one at a time ??

[Tikuf 663]

From top level doesn't work?

 

not sure if it will help or not but if top level doesn't work you could  try the refresh within the boxsets plugin

[CBers 7450]

From top level doesn't work?

 

not sure if it will help or not but if top level doesn't work you could  try the refresh within the boxsets plugin

 

Nothing within the Collections to refresh - have to go into each BoxSet.

 

Just hit the Refresh BoxSets in the plugin - I'll see what that does.

 

Thanks.

[CBers 7450]

From top level doesn't work?

 

not sure if it will help or not but if top level doesn't work you could  try the refresh within the boxsets plugin

 

 

Nothing within the Collections to refresh - have to go into each BoxSet.

 

Just hit the Refresh BoxSets in the plugin - I'll see what that does.

 

Thanks.

 

The Refresh BoxSets option in the plugin didn't seem to work.

 

I still have BoxSets as above.

 

I'll have to do them manually.

[CBers 7450]

The Refresh BoxSets option in the plugin didn't seem to work.

 

I still have BoxSets as above.

 

I'll have to do them manually.

 

OK, I decided to delete all of the contents of my BoxSets folder and allow the plugin to re-create.

 

It did find 111 potential boxsets:

 

2014-03-03 14:21:52.7833 Info - Automatic BoxSets: Executing Automatic BoxSet creation.  Found 111 potential box sets.
2014-03-03 14:21:52.7903 Debug - Automatic BoxSets: Found box set 131635 with 2 members.
2014-03-03 14:21:52.8063 Debug - Automatic BoxSets: Created new box set: \\MEDIASERVER-3\Movies\BoxSets\MB Auto Set [Boxset][tmdbid=131635]
2014-03-03 14:24:04.5089 Debug - Automatic BoxSets: Found box set 131635 with 2 members.
2014-03-03 14:24:04.5589 Debug - Automatic BoxSets: Box set already exists. Will confirm members.
2014-03-03 14:24:04.5989 Debug - Automatic BoxSets: Member The Hunger Games: Catching Fire already exists
2014-03-03 14:24:04.5989 Debug - Automatic BoxSets: Member The Hunger Games already exists

And it seemed to create 59, but I still have the same issues as before, but all BoxSets are in the same state now:

 

 

If I manually refresh each boxset (GI Joe for example), it seems to be fetched OK, but not via the plugin/library scan.

 

Log here if anyone can shed any light on this please.

 

TIA.

Edited March 3, 2014 by CBers

[Scott84Z28 39]

I had the same thing happen on the weekend.  To fix it I had to manually refresh each individual "MB Auto Set". 

[ebr 16169]

Scott - are you on the dev server too?

[Scott84Z28 39]

Nope, I'm on the Beta release.  Version 3.0.5171.19958

The Boxset plugin is 0.0.1.2

 

It seems to be working fine now.  I put a few new films on there last night, and it created the box set correctly.

[ebr 16169]

There must be some situation that causes them to lose metadata and not get refreshed.  We'll have to keep an eye on it.

[CBers 7450]

So no solution other than manually refreshing (59) BoxSets ??

[ebr 16169]

If you do it from MBC, you can do it at the media folder level and it will get them all.

[CBers 7450]

If you do it from MBC, you can do it at the media folder level and it will get them all.

 

Thanks - only left with 3 to manually refresh.

[AlwinHummels 134]

I've another strange behavour. I get some red warning triangles on my dashboard but don't know what the mean.

 

Dutch error when I try ti identificate one off the red triangled BoxSets.

Kan een gedeelte van het pad C:\Users\MyName\AppData\Roaming\MediaBrowser-Server\cache\tmdb-collections\168545\all-nl.json niet vinden.

 

All the red triangled boxsets give me a same can not find ..\all-nl.json

All others are fine so I don't understand why he didn't create those all-nl.json files. is this because tmdb has no dutch translation for the boxsets? if so I create some Dutch but still no luck. I tought there is a fallback to English too ;-)

 

Hope my description of the problem is clear enough to solve the problem.

Edited March 4, 2014 by AlwinHummels

[ebr 16169]

Are you on the dev server?

[AlwinHummels 134]

Yes I'am ;-) Version 3.0.5176.6 I removed my library.db and all cache files also removed all the collection shortcuts but still the same issue on the same boxsets

Edited March 4, 2014 by AlwinHummels

[ebr 16169]

I think that is a feature that is in-progress.  Probably indicates the fact that the system did no properly identify that item.

[AlwinHummels 134]

Okay I'll wait for one off the next releases. Thanks for the quick reply

Below are the boxsets that failed maybe it helps to find out what's wrong ;-)

• MB Auto Set [boxset][tmdbid=167613]
• MB Auto Set [boxset][tmdbid=168545]
• MB Auto Set [boxset][tmdbid=177675]
• MB Auto Set [boxset][tmdbid=220498]
• MB Auto Set [boxset][tmdbid=257053]

Edited March 5, 2014 by AlwinHummels

[AlwinHummels 134]

Still have this issue with the same boxsets. Used All the latest Dev verslons.

Edited March 19, 2014 by AlwinHummels

[CBers 7450]

Still have this issue with the same boxsets. Used All the latent Dev verslons.

 

I had a couple as well.

 

I had to manually set the collection ID and then refresh, or delete the boxset if the collection ID didn't exist, as for Pixar Shorts.

Edited March 19, 2014 by CBers

[ebr 16169]

That symbol means the item is potentially mis-identified.  I'm not positive what makes it think that but maybe a mismatch in release dates or it can't find the id at the provider.

[AlwinHummels 134]

thanks again can't see why "alvin and the chipmunks collection" give me that message because i cant find what's wrong with it.

It seems that all my warnings have a isue with the all-**.json. It exists for all collections exepts the mentioned earlyer with the warning.