Uploading problems - blank screen, images in queue

[J.R. Rogers]

I had a user report a problem uploading and I looked in the upload directory. To my horror, a few dozen users have tried uploading photos over the past 15 days and they are not being processed. I tried uploading myself and when you click upload/submit, you just get a blank page. I've done the following:

• Upgraded to the latest version of PhotoPost PHP
• Verified that the permissions on the data and uploads directories were set properly (to 777) and that the permissions were applied to lower directories
• Rebooted / Restarted SQL and APACHE
• Checked PHP settings and verified that It's set to allow uploads up to 2MB
• Verified that GD is working
• Performed a YUM update on the server and updated several OS components, restarted server

Why the blank screen and images going unprocessed? I've confirmed that they make it into the upload directory properly, and then nothing. The images show to be in the users queue if the user tries to upload again. How can I force the queued images to process? What could be causing this problem? Is there any way to disable uploads and post a message about the problem until I can get it resolved? Please help! Thanks!

[Chuck S]

Common GD processor issue since it uses PHP memory. This should help

http://www.photopost.com/forum/showp...97&postcount=2

[DST Daddy]

had a user with similar issues just today!

Implemented the code

[J.R. Rogers]

Originally Posted by Chuck S

Common GD processor issue since it uses PHP memory. This should help

http://www.photopost.com/forum/showp...97&postcount=2

Content visible to verified customers only.

Thanks, Chuck. What exactly does this do? It looks like it overrides the PHP limit of 2MB for file uploads and increases the amount allowed to 60MB. What are the pitfalls of doing this so I understand the risks?

[Chuck S]

Nope it overrides the memory limit and gives more memory to PHP

Your PHP is choking cause GD2 is using all the memory

[J.R. Rogers]

Originally Posted by Chuck S

Nope it overrides the memory limit and gives more memory to PHP

Your PHP is choking cause GD2 is using all the memory

Ah. Thank you. That seems to have fixed the problem.

JR

[Freakpyromaniac]

I have the same problem butr can find the phrase that you are showing. This is my whole PP-inc.php file.

$contentmeta $nocachetag $headtags $javapopup $headslide $stylesheet $ajaxcode
"; if ( file_exists($newheader) ) { print $header; if ( $printheader == "yes" ) { @include( $newheader ); } } else { print $header; } } // // Now lets put them into the Who's Online table // if ( $Globals['onlinepal'] == "yes" || $Globals['displayonline'] == "yes" ) { update_whoonline( $thiscat ); // Cleanup old records (number of seconds) if ( THIS_SCRIPT == "ppindex" ) { $expire = time() - 600; $resultb = ppmysql_query("DELETE FROM {$Globals['pp_db_prefix']}iponline WHERE date < $expire", $link); } } // Does the admin need a reminder? if ( $Globals['ppboards'] == "closed" && $User['adminedit'] == 1 ) { echo "

Your boards are currently closed!
"; } // That's it! $Globals['printheader'] = "yes"; return; } function printfooter( $headers = "yes" ) { global $Globals, $User, $Style, $vbfooter, $ppstarttime; // Removing the line below constitutes a violation of your License Agreement // and will result in significant penalities if removed. print "
{$Globals['cright']}

"; // Set this to 1 if you want to see debug information (only prints for admins) // Set this to 2 is you want to print out queries and timing info $showsqldebug = 0; $ppendtime = microtime(); $starttime = explode(" ", $ppstarttime); $endtime = explode(" ", $ppendtime); $totaltime = $endtime[0] - $starttime[0] + $endtime[1] - $starttime[1]; $totaltime = number_format( $totaltime, 5 ); if ( $showsqldebug > 0 && $headers == "yes" ) { print "
Page generated in $totaltime seconds with {$Globals['number_queries']} queries
"; if ( $User['adminedit'] == 1 && $showsqldebug == 2 ) { for ($x = 0; $x < count($Globals['queries']); $x++ ) { print ($x+1). ": {$Globals['queries'][$x]} ({$Globals['timing'][$x]} sec)
"; } } print "
"; } if ( !empty($vbfooter) && $headers != "no" ) { print $vbfooter; } else { if ( $headers == "yes" && file_exists($Globals['footer']) ) { @include( $Globals['footer'] ); } } print "

[Chuck S]

You got to look up higher in the beginning of the pp-in.php file you will see the line noted about error_reporting

[KlausM]

I Did exactly like you wrote:

Content visible to verified customers only.

But I still get the same error??

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 2432 bytes) in /customers/godtfoto.dk/godtfoto.dk/httpd.www/image-inc.php on line 102

It´s very strange because you only have the problem with some pictures.
Right after i get the error I can upload several other pictures without any problems. But as soon I try to upload the first picture again I get the error again.
And I´m not the only one many of the members get this error with one or two pictures???

After you get the error you can see that you have a picture in queue.
And when you try to overide the normal upload procedure and choose to upload the picture you already have in the queue it sometimes says that everything went ok, but the picture are not showing up anywhere???

There must be a solution to this???

Maybe I could try to e-mail one of the pictures that make that error to you Chuck?

I already tried to save it again with a new name and even from differnet programs but nothing helps.

[Chuck S]

The error your noting says your PHP memory is only 16mb not 60 so this is your issue.

The solution other than giving gd2/PHP more memory is to install Imagemagick on your server which does not use PHP memory

[KlausM]

Originally Posted by Chuck S

The error your noting says your PHP memory is only 16mb not 60 so this is your issue.

The solution other than giving gd2/PHP more memory is to install Imagemagick on your server which does not use PHP memory

Yes I can see that but so can´t the line you said we should add be working.

[Chuck S]

Go to our requirements page download the phpinfo.zip file extract the phpinfo.php file and upload it to your photopost directory and place the link here to that file so we can see your php settings as your not doing something right here somewhere

[KlausM]

Okay Chuck here is the link:

http://www.godtfoto.dk/phpinfo.php

[Chuck S]

Yep just as I thought 16 MB so your not going the edit right it would appear in the proper file or something cause quite simple if the edit is done correct then your PHP memory would be 60M not 16M and your error notes it is still 16

So try reapplying the edit in pp-inc.php try making it a reasonable change like set it to 32M and you can check that it takes effect by viewing your PHP INFO in admin and it should read 32M

[KlausM]

Ok but you can see in my earlier answer that I have done exactly what you said, but ok I try again.

[KlausM]

Now I tried again with 32 Mb but it doesn´t change anything.

And you can see here that I have done it correct - also the first time.

So what is happening here?

Content visible to verified customers only.

[Chuck S]

What does your PHP INFO say in admin after you make the change? You did not answer my question

[KlausM]

Sorry it was the same 16 M

I can see now that my host are running PhP in Safe mode.

Maybe it is the problem???

[Chuck S]

Yes your host is doing 2 things. They are not allowing you to override PHP values and yes safe mode on is a big problem that needs to be off.

[KlausM]

Okay I just wrote to them if they will set it to off or if the could set the memory limit for me.

Thanks again Chuck
By the way what´s the time over there :-)
Here in Denmark it´s 4 in the night.