Serendipity Forums

Domainfactory kindly made an alteration to my SQL db. They actually insist on reimporting the SQL dump themselves if it is over a certain size. I had all my jpgs and some pdfs on Movable Type, before the import to Serendipity, in a directory. I wanted the directory name changed. The results looked good: my images appeared. However, since I had some thumbnails I presume, and maybe there were some other files in there I wasn't aware of, when I put a jpg in the media library and then wanted to insert it in a new entry, I got a fatal error message. I repeat that at the end.

Question: do I just need to change the lines cited, or might there be a lot more that didn't appear because of the fatal error?

Why would the size exceed what I'm allowed? Just software conflicts?

I want to ask the technical assistance at df, but I think I already irritated them because I had not corrected the SQL dump and they redid it for me.

All I wanted to do was not have to repost all my images by hand. I see there was a problem with one specific image, but the other error messages refer to lines, not files.

Here it is:

>>Warning: imagecreatefromjpeg(): '/kunden/187871_90762/webseiten/serendipity/uploads/MT_archives/benjiw.jpg' is not a valid JPEG file in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1231

Warning: imagesx(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1232

Warning: imagesy(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1233

Warning: Division by zero in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1282

Warning: Division by zero in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1283

Warning: imagecreatetruecolor(): Invalid image dimensions in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1247

Warning: imagealphablending(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1251

Warning: imagesavealpha(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1252

Warning: imagecopyresampled(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1255

Warning: imagejpeg(): supplied argument is not a valid Image resource in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1258

Fatal error: Allowed memory size of 52428800 bytes exhausted (tried to allocate 14000 bytes) in /kunden/187871_90762/webseiten/serendipity/include/functions_images.inc.php on line 1231<<

TIA for any assistance,

Margaret

Everything seems to be in order. I tried to load the image benjiw.jpg to a new entry, but it didn't work. The file benjiw.jpg looks OK, but benjiw.SerendipityThumb.jpg is empty. (How did an MT thumbnail turn into a Serendipity thumbnail?)

So could this have been a one-off problem with a corrupted file?

Margaret

Hi!

Check the s9y configuration for the "automatgic synchronization of images", this is responsible for automatically iterating over all your uploaded images and building s9y thumbnails.

Regards,
Garvin

I've got 'enable media synchronization on the fly' checked. Could it be that, when I looked at the media library, it synchronized the lot and crashed because that one file was defective? The problem seems to have gone now. I still don't know what will happen to the thumbnail images, but as long as it doesn't crash that is OK. I was worried about bringing down the server, but I have paid to be given more space if there is an emergency increase of traffic.

Margaret

Hi!

Exactly like this, yes. In your case, you should disable that synchronization feature.

Regards,
Garvin

Right, I will do that. (So it could happen again?)

Margaret

Hi!

Yes, it can happen everytime when you have too many files in your upload directory that the MDB did not know about, and tries to import them all at once, which takes a lot of time.

Regards,
Garvin