Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Filebrowser thumbnailer: 'Generate Thumbnails' results in a blank screen and no thumbs
Not being a techy, I have no idea if the server has the GD2 library or where to get it/how to install it if it doesn't. Would that be causing this problem?
This problem doesn't occur on smaller images, but I am having problems on my 600k+ files.
0
This discussion has been closed.
Comments
For larger files, I sometimes have to increase the php_memory limit in a .htaccess file. It is usually set at about 8MB, so I double it and see if that works.
I could be totally off the mark here, but this can do no harm. Stick this in a .htaccess file in the filebrowser directory:
# PHP is hungry. Give it more resources. php_value memory_limit 16M
Please let me know how is works out
Could it be the same issue as this? (although they don't say if they see an error message - I just get a blank screen). I don't begin to understand the stuff in the grey box on that thread, and there seems to be no solution offered there.
Does it time out or simply complete the task without actually generating the image?
It can't be a permissions problem as it makes some thumbnails already. If you are using different directories though, make sure (most important, as you are with MediaTemple by the looks of it. they are picky.) your permissions are chmod 777 for all the folders the images are in, including the one the filebrowser is in.
It doesn't complete the task without generating the image - I never see a confirmation screen (it just remains blank).
Permissions for all folders set to chmod 757 as per the readme file that came with Filebrowser, but changing that to 777 makes no difference with the problem.
Thanks again for your assistance! I hope we can fix it :-)
jeandeluxe resolved the issue, but without leaving instructions for others with the same problem.
Why would this bug have anything to do with the filename??
However, if you use Nathan's code:
# PHP is hungry. Give it more resources. php_value memory_limit 16M
But, bump it up to like... 32M, it should work.
I am working with files about 500-800k and I can do 3 at a time. I haven't tried more then that. But it works for me.