Page MenuHomePhabricator

Error creating thumbnail on mw 1.6.x
Closed, ResolvedPublic

Description

Author: stanley

Description:
I found "error creating thumbnail" when trying to create thumbnail smaller then
the original PNG images. Works fine when the thumbnail larger then original
size. Also works fine on 1.5.8 whatever the thumbnail size. These failed on
1.6.3, 1.6.7 and 1.7 r15313

mw 1.6.7 testcase: http://202.148.16.226/mw167/index.php/Main_Page
mw 1.6.3 testcase: http://202.148.16.226/mw163/index.php/Main_Page
mw 1.5.8 testcase: http://202.148.16.226/mw158/index.php/Main_Page
mw 1.7 testcase: http://202.148.16.226/mw17/index.php/Main_Page

All wikis are fresh installation and installed on the same server running
Windows 2003 Server, PHP 5.0.4 Apache 2.0.5.5 ImageMagick 6.2.7


Version: 1.6.x
Severity: normal
OS: Windows Server 2003
Platform: PC

Details

Reference
bz6540

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 9:17 PM
bzimport set Reference to bz6540.
bzimport added a subscriber: Unknown Object (MLST).

robchur wrote:

Check permissions. Apache needs to be able to write to the thumbnail
directories. Check that ImageMagick is set up right. Check that the path to
convert is correct in each configuration.

stanley wrote:

If the issue was permission, the mw.1.5.8 should produced error which is not.

stanley wrote:

After spending hours of trial and error, I found that the problem caused by
extra characters . " 2>&1"; on include/image.php. After removing that, image
thumbnailing is working again. I'm not a PHP expert, and I don't know the use of
this extra characters, but still this is a workaround to my problem. These
characters are not found on mw 1.5.8 (mw 1.5.8 works fine with image
thumbnailing, see initial description and comment #2).

modified include/image.php:

wfEscapeShellArg($thumbPath);
//wfEscapeShellArg($thumbPath) . " 2>&1";

2>&1 means "redirect standard error to standard output".
That's probably used to hide errors in apache logs.

Closing bug. Probably solution should be added (where?) to document it.

Bug was already closed in c5.