Bug 13454 – Scanner doesn't pre-cache placeholder artwork due to missing Slim::Web::HTTP::getStaticContent()

Bug 13454 - Scanner doesn't pre-cache placeholder artwork due to missing Slim::Web::HTTP::getStaticContent()

Summary:

Scanner doesn't pre-cache placeholder artwork due to missing Slim::Web::HTTP:...

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Alarm
Version:	7.4.0
Platform:	Macintosh MacOS X 10.5

Importance:	P1 normal (vote)
Target Milestone:	7.4.0
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:	9757
	Show dependency tree / graph

Reported:	2009-08-18 08:35 UTC by Michael Herger
Modified:	2009-10-05 14:36 UTC (History)
CC List:	2 users (show)

See Also:	9919
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Herger 2009-08-18 08:35:06 UTC

As the scanner doesn't initialize the web UI, that function isn't loaded. It crashes the artwork scanning code silently for inexistent artwork files. We might want to rewrite it locally (in the Graphics code).

Comment 1 SVN Bot 2009-08-19 01:38:47 UTC

 == Auto-comment from SVN commit #28224 to the slim repo by michael ==
 == https://svn.slimdevices.com/slim?view=revision&revision=28224 ==

Bug: 13454
Description: use NoWeb skin when running artwork scan

Comment 2 Michael Herger 2009-08-19 01:40:41 UTC

fixed in change 28224

Comment 3 James Richardson 2009-10-05 14:36:07 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.