Thread

Hi,

Been busy with this error for a while… searched through the forums and did not found a proper solution.

Description of symptoms:
- file uploads for files bigger than 2MB are throwing the error ‘Fieldname - thumbnail could not be created for the image. please make sure the thumbnail directory is writable.’

- files smaller than 2MB are working fine

- all directories are CHMOD 777 with the right group

- error is unrelated to safecracker, the filemanager and addon ‘Mega upload’ throw the same error

- GD2 is enabled (screen from phpinfo: http://take.ms/BVy)

- upload through regular php uploadform is working for big files (4MB +)

- upload_max_filesize is set to 16M (screen from phpinfo: http://take.ms/CVy)

- created a new upload destination: same error

- synchronisation of files works fine, no errors are thrown during this process

- doesn’t matter if i set ‘allowed filetypes’ to only images or all files, same error

- I’m not on a windows machine where slashes should be backslashes

- I’m using EE v2.5.5 - Build: 20121220, Safecracker 2.1

- Php ver. 5.3.3-7+squeeze3

I would love to receive some tips where to search next!

Hi, did you find a solution to this problem? I’m in exactly the same situation.

- Thumbs for files up to 2M size are generated
- All directories have 777 file permissions
- GD installed as follows:

GD Support enabled
GD Version bundled (2.0.34 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.3.11
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version 6b
PNG Support enabled
libPNG Version 1.2.49
WBMP Support enabled
XPM Support enabled
XBM Support enabled

- post_max_size 36M
- memory_limit 128M

All other details very much like you’ve provided above. It’s the creation of thumbnails that looks to be killing the process. This is getting pretty urgent, if left with no other option I might have to hack the core files to stop the thumbnail error occurring.

I’ve arrived at a solution for this problem myself.

We’re using a virtual server solution. It allowed us to configure the PHP memory limit per site and I’d set it to 128M, which seemed plenty.

However, despite what was shown in the phpinfo output, the site was using the limit in the server php.ini - 32M. I modified this to 256M and all is now working.

Hi,

Yes, it seemed to be the memory. After upgrading the memory the error disappeared.