Q.
Quote:
Originally Posted by Chuck S  Local value 72mb means you have not edited the file correctly or your server does not support ini_set overrides |
I've spoken with our host (Westhost), and they DO support ini_set services.
In my php.ini file, I have put the following
memory_limit = 96M ; Maximum amount of memory a script may consume (128MB)
In my pp-inc.php file, I have put the following
error_reporting(E_ALL & ~E_NOTICE & ~8192);
ini_set("memory_limit", "72M");
define('PP_SCRIPT', 'PP_Pro');
Q.
Quote:
Originally Posted by Chuck S You would need to have your host give you the path to mogrify and enter that in your config settings then switch global options to imagemagick and try. |
My host just gave me the path to mogrify which is
/usr/bin/mogrify
I checked in PhotoPost Admin Configuration Administration
and my Path for MOGRIFY executable is already
/usr/bin/mogrify
Q.
Quote:
Originally Posted by Chuck S So after clearing your uploads directory are you able to say upload a small image as a test. |
A single file using the Flash uploader works fine.
Seven files using the Flash uploader crashed the site (although the seven images are now sitting in my uploads folder now)