Approved Collections Automatically Use folder.jpg

[cybrsage 4]

When I setup collections in MB3 does not use the folder.jpg file located in the root of the collection folder.  There was only one, so it could not get confused.  MB2.6 used it automatically.

 

The fix is to open the web interface and manually select the folder.jpg in every single collection I setup.  Yes, I only have to go through that pain once for every collection, but it is still painful.

 

I would like to see MB3 parse the base folder locations for a collection and, if there is only one folder.jpg, automatically select it.  If not, then either ask which the user wants or default to the current process of using nothing.

[Luke 37058]

Yea, we missed this. If a collection only has one folder, then we should support images stored in that location.

[Luke 37058]

This is approved and will be handled in a future release:

 

https://github.com/MediaBrowser/MediaBrowser/issues/616

[ebr 14910]

Yea, we missed this. If a collection only has one folder, then we should support images stored in that location.

 

You mean a single media location?

[Luke 37058]

Yea.

[cybrsage 4]

NICE!  That will save me a LOT of time and effort!