Build 2.02 Beta 1: Upload Error Reporting
12 posts by 4 authors in: Forums > CMS Builder
Last Post: January 22, 2010 (RSS)
By Dave - January 21, 2010
Hi Guys,
Thanks for the feedback. We're absolutely on the same page as you and agree.
Any strange errors that occur just let us know and we'll figure out how to work around it or display more user-friendly errors.
Thanks!
Thanks for the feedback. We're absolutely on the same page as you and agree.
Any strange errors that occur just let us know and we'll figure out how to work around it or display more user-friendly errors.
Thanks!
Dave Edis - Senior Developer
interactivetools.com
interactivetools.com
Re: [Dave] Build 2.02 Beta 1: Upload Error Reporting
By Dave - January 22, 2010
Just a follow-up post on the image resizing errors issue for anyone following.
It turns out that in this case the host had some additional memory limits that weren't displayed by CMSB. We added a new line to the next release under Admin > General to show these. It's called "Server Resource Limits".
Also, images are highly compressed and thumbnailing them requires decompressing them, which takes a lot of memory.
We made a test script and it turns out a 2meg image takes approx 40megs of memory to open it for thumbnailing (which was more memory than this host supports).
We haven't found a way to detect when we hit the memory limit in cases like this, the host just kills the CMSB process and you get an error.
So the work-arounds for now if you have a host with a lower memory limit are:
- Ask your host to increase your memory limit
- Limit the max upload size to 1 meg
- Turn off all thumbnailing (which requires loading images)
- Switch hosts
Hope that helps! Let me know if anyone has any other questions about this.
It turns out that in this case the host had some additional memory limits that weren't displayed by CMSB. We added a new line to the next release under Admin > General to show these. It's called "Server Resource Limits".
Also, images are highly compressed and thumbnailing them requires decompressing them, which takes a lot of memory.
We made a test script and it turns out a 2meg image takes approx 40megs of memory to open it for thumbnailing (which was more memory than this host supports).
We haven't found a way to detect when we hit the memory limit in cases like this, the host just kills the CMSB process and you get an error.
So the work-arounds for now if you have a host with a lower memory limit are:
- Ask your host to increase your memory limit
- Limit the max upload size to 1 meg
- Turn off all thumbnailing (which requires loading images)
- Switch hosts
Hope that helps! Let me know if anyone has any other questions about this.
Dave Edis - Senior Developer
interactivetools.com
interactivetools.com