recreating thumbnails error message

[-okapi-]

while trying to recreate thumbnails i get the following errror message:

Warning: imagejpeg(): Unable to open '../thumbnails/thumb_20050425184819_2004_07_07_01.jpg' for writing in /**/***/***/includes/functions.php on line 92
Warning: chmod(): Operation not permitted in /**/***/***/includes/functions.php on line 94
the images folder and the thumbnails folder are chmod 777.
what can be the reason for this error?

[Joe[y]]

you should know the drill by now... post your info from admin/ please.

[-okapi-]

sorry, but how should i know? i've never had database related problems.
here is the info from admin panel:

Pixelpost Version
You are running version 1.4.1 of Pixelpost. Released 24 April 2005.

Host Information
PHP-version 4.3.10 (Pixelpost's min requirement: PHP version 4.3.0)

MySQL version 4.0.24-standard (Pixelpost's min requirement: MySQL 3.23.58)

GD-lib bundled (2.0.28 compatible) with JPEG support

Server software Apache

EXIF Pixelpost is using exifer v1.5 for EXIF information.

Paths
Guessed imagepath: /**/***/web/images/

Configured Imagepath /**/***/web/images/

Image Directory: OK - Can we write to the directory? YES.

Thumbnails Directory: OK - Can we write to the directory? YES.

Language Directory: OK

Addons Directory: OK

Includes Directory: OK

Templates Directory: OK

----------------------------------------------------------------------

the thumbnails directory is writable, but the maybe the thumbnails are not, and therefore can't be overwritten?

[raminia]

this addon irritates me!!

[Joe[y]]

this addon irritates me!!

what addon?

[raminia]

oops:) I meant this regenerating of thumbs...

[Joe[y]]

the only thing that i can possibly look at for a problem is the **/***/ but as far as that goes as a solution, it helps none at all. I was just wondering if that was your actual path as it is slightly odd.

[raminia]

the only thing that i can possibly look at for a problem is the **/***/ but as far as that goes as a solution, it helps none at all. I was just wondering if that was your actual path as it is slightly odd.

what?! problem with **/***/ ?!

[Joe[y]]

i didn't say it was a problem. it just looked unusual to me - i've never seen directories on a server named like that. but obviously it isn't a problem.

[-okapi-]

:wink:

i wrote the ***/**/ as placeholders for the absolute server path to my site. i thought it might not be the best idea to make it public!

[tanjatiziana]

I came to the forum today to post the same problem. Everything on my blog works fine cept that if i try to do re-crop an old thumbnail or generate all new thumbnails through the "options" area, i get that error.

[raminia]

I don't like this bug!!

[raminia]

I don't have a clear idea about this bug but lets try to consider posibilities:

- wrong path name?
- Server is busy?
- Sever Timeout?
- CHMOD ? permission problem?
- Problem with the source jpg?
- Long file names?
- Special GD or PHP versions or components?
- Security permission of the server for accessing directories?
- Something from Mars?

[-okapi-]

i think it's something from mars. :lol:

[-okapi-]

i chmoded 777 all thumbnail jpgs, not just the thumbnails folder, but again - the same error message:

Warning: chmod(): Operation not permitted in /***/***/**/***/web/includes/functions.php on line 94

don't know what's going on.

[raminia]

I really think it's a problem with paths!

[Peloria]

I'm having this same issue, having finally upgraded to 1.4.1 this evening. Everything works great, except for this feature. I keep getting the error:

Warning: chmod(): Operation not permitted in /home/runtdog/public_html/photos/includes/functions.php on line 94

The path is correct, as far as I can tell, and permissions are set correctly. Is there any solution to this?

*edit* If I try to change one thumbnail at a time, I get an "Cannot modify header information" error as well. I tried clearing my cache and cookies, but it still doesn't work.

Also note: If I upload a NEW image, the cropping utility works fine. It's only on older entries.

[Joe[y]]

can you post your general info please peloria! :D

[Peloria]

Sorry about that - here you go:

Host Information
PHP-version 4.3.10 (Pixelpost's min requirement: PHP version 4.3.0)
MySQL version 4.0.24-standard (Pixelpost's min requirement: MySQL 3.23.58)

GD-lib bundled (2.0.28 compatible) with JPEG support

Server software Apache/1.3.33 (Unix) mod_gzip/1.3.26.1a mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.3.10 FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.7a

EXIF Pixelpost is using exifer v1.5 for EXIF information.


Paths
Guessed imagepath: /home/runtdog/public_html/photos/images/
Configured Imagepath /home/runtdog/public_html/photos/images/

Image Directory: OK - Can we write to the directory? YES.

Thumbnails Directory: OK - Can we write to the directory? YES.

Language Directory: OK

Addons Directory: OK

Includes Directory: OK

Templates Directory: OK

[Joe[y]]

looking at your general info i see that we have miraculously identical specs throughout. ie, my blog is running exactly the same way with everything that should matter with pixelpost. so I have to assume there is something we've overlooked as my blog works fine with this.

can you please first double and triple check your permissions as i remember a user before not have the correct permissions despite pp telling them they did... even if it says 777 try re-chmoding it or something

and if that doesn't work create a file called phpinfo.php somewhere on your server with the following code contained:

<?PHP
phpinfo();
?>

then link us to that so i can perhaps look for the difference in your php from mine that is causing the problem.

[Peloria]

I checked and re-checked permissions, and they seem to be okay. I even deleted my photos, reuploaded them from backup, and reset permissions again - no change.

[blinking8s]

*scratches head*

did you inquire your hosting support about the issue...I always go ahead and do that just to get it out of the way.

I had a similar error once and it was a result of // in my path, which the server kept slipping in for some reason...but you paths seems correct listed there...humph

[Joe[y]]

i've only been on the team since 1.4.1 so i'm afraid i can't shed any light on what changed with this function...


cue the 1.4.1 developers! :arrow: