Coppermine and PHP 4.4.1 - imagejpeg workaround Coppermine and PHP 4.4.1 - imagejpeg workaround
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Coppermine and PHP 4.4.1 - imagejpeg workaround

Started by kegobeer, November 02, 2005, 11:56:47 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

kegobeer

November 02, 2005, 11:56:47 PM Last Edit: December 04, 2005, 11:51:53 PM by kegobeer
If your server is running PHP 4.4.1 and is also running in safe mode, you may have issues with uploading jpeg images.  You may receive this type of error message:

Unable to create thumbnail or reduced size image.
imagejpeg(): unable to access

There is a bug report at bugs.php.net about safe_mode and imagejpeg() in 4.4.1.

http://bugs.php.net/?id=35060

This workaround will fix the issue, until a fix from PHP is released.  Open up picmgmt.inc.php, find (around line 209)

Code Select
imagejpeg($dst_img, $dest_file, $CONFIG['jpeg_qual']);

and replace with

Code Select
$fh=fopen($dest_file,'w');
fclose($fh);
imagejpeg($dst_img, $dest_file, $CONFIG['jpeg_qual']);

If you are using GD1, look a few lines above and make a similar change.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

JDuc

#1
November 28, 2005, 11:38:17 PM
where should picmgmt.inc.php be located?  what folder?

thanks :)

dizydizzy

#3
December 01, 2005, 09:44:46 PM
After 3 days of searching this forum I finally found the answer here in this thread...thnx to Kegobeer I finally got CPM to work.

Big  :-* to you.  ;)

Poom

#4
December 04, 2005, 06:45:20 PM
This won't work for me :(

kegobeer

#5
December 04, 2005, 11:08:13 PM
Quote from: PoomThis won't work for me

Because you did not apply the fix correctly, as stated in your related thread.

This thread is now locked.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Joachim Müller

#6
February 24, 2006, 05:32:23 PM
@dev team: should this go into the maintenance release?

Joachim Müller

#8
February 26, 2006, 06:54:47 PM Last Edit: March 01, 2006, 07:56:06 PM by GauGau
The code in this fix has gone into cpg1.4.4 - users running any previous versions may have to apply the fix, users who run cpg1.4.4 (or better) won't have to.

[edit GauGau 2006-03-01]
The fix didn't go into cpg1.4.4, sorry folks - see postings below
[/edit]

kegobeer

#9
March 01, 2006, 07:07:21 PM
I don't see it in the 1.4.4 release.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Joachim Müller

#10
March 01, 2006, 07:55:03 PM
dang, something went wrong:  the last-minute commit didn't make it into the package. Oh well, sorry then: I edited my above posting accordingly.

Joachim Müller

#11
May 18, 2006, 06:12:51 AM
The fix has gone into stable and devel branch today. This means that the fix will go into cpg1.4.6. All users who run an older version together with PHP4.4.1 will have to apply the fix manually (or even better upgrade to cpg1.4.6 once it got released).
Print
Go Up Pages1
User actions