Skip to content
New issue

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

Custom Fanart not found when 'mjb.scanner.hashpathdepth' enabled #1622

Closed
Omertron opened this issue Mar 15, 2015 · 2 comments
Closed

Custom Fanart not found when 'mjb.scanner.hashpathdepth' enabled #1622

Omertron opened this issue Mar 15, 2015 · 2 comments

Comments

@Omertron
Copy link
Member

Original issue 1623 created by Omertron on 2010-10-03T12:09:22.000Z:

The FanartScanner uses 'movie.getBaseName()' for the getting the base file name. If 'mjb.scanner.hashpathdepth' is enabled, not only the filename comes back, but also a hashcode. This way the FanartScanner fails to find custom fanart.

Example:

The FanartSanner searches for fanart with this filename:
'coraline-1080pa63ffb67.fanart.jpg'
(hashcode in filename included)

But it should just look for:
'coraline-1080p.fanart.jpg'
(no hashcode in filename)

This bug can be fixed using "movie.getBaseFilename()" instead.
In Fanartscanner.java ~ line 83.

@Omertron
Copy link
Member Author

Comment #1 originally posted by Omertron on 2010-10-04T01:02:39.000Z:

OK thanks, never knew there was a mjb.scanner.hashpathdepth ;)

@Omertron
Copy link
Member Author

Comment #2 originally posted by Omertron on 2010-10-05T11:46:23.000Z:

This issue was closed by revision r1823.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant