Blank white screens in both Publish and Edit sections, already increased PHP memory to 24M

Edit Subject

24MB is still not all that much... try 64.

Could be a Windows thing; I’ve never tested FF on Windows.

I had them raise the memory to 32M but he says he won't go any higher because he thinks it will impact the server performance. The screens are still not loading. I have the site working on my Mac laptop using only 24M of memory. I hate Windows...

No issues for me using Windows XP and Windows 7 with FieldFrame.

I'm having this problem (blank white screen when trying to Publish or Edit) when using the nGen File Field. The other fields work just fine (checkbox, radio, multiselect, tinymce 2, etc). But if the nGen Field Field is associated with the weblog, then I get the blank white screen when trying to Publish or Edit that weblog. (This occurs with and without Gypsy)

Any ideas?

I've had the same issue but not consistently. I used FieldFrame (FF Matrix) and nGen File Field in two weblogs without problem. On the third weblog I used the same setup, went to publish and I get a plain white screen.

I managed to get around this by completely deleting the custom field group and any associated entries, then re-creating the custom field group and fields. going to the publish this time worked. This happened again on the fourth weblog I setup too. Still not sure why but the same process got it working again in the end. Bit of a bind though.

Incidentally trying it _without_ FF Matrix and just nGen File Field produced the same white screen on its own as did using FieldFrame (FF Matrix) on its own so I'm not sure which extension the problem lies with.

I'm running the latest version of EE (1.6.7), Mac OS X 10.5.7, with a MAMP Pro setup.

Any further ideas on what could be causing this?

I have the same issue and set up as typo.

Running 128mb php memory

I had this problem when I had nGen's Publish Tweeks enabled. I disabled it and then FF Matrix w/ nGen's File worked fine.

Doesn't make sense to me why this solved the problem, but its what worked for me.

I just overcame this problem - maybe you have the same issue as I did. I kept getting an error in ft.ngen_file_field on line 842 [$im = imagecreatefromjpeg($file);]. If you were using an old version of Ngen File and then upgraded to the newest version, it tries to create new thumbnails of all the images in your upload directory at once (so you can use the new thumbnail preview feature when choosing 'Use an existing file'). I was maxing out on memory trying to create thumbnails of 100+ images at once. I upped the memory limit on the server to accommodate all of the processing memory the thumbnail generation required. After the thumbnails were created, I dropped the memory back down. Now, new thumbnails are created when the entry is saved and only a small amount of memory is used. Hopefully this will help some people :)

Update: narrowed the issue down to the nGen File Field, which turned off reinstates both Publish & Edit actions. Have contacted the developer for further assistance...

Is there a method to debug the extension with such an issue?

Confession: the reason for nGen Field to cause the white screen was the limited PHP memory on my local machine. I am running MAMP and MAMP Pro and it turns out that each uses their own - at different location - php.ini file.

Lesson learned is to double check your phpinfo if your modifications have been accepted!

Thanks to all & Fred Boyle (nGen) for your assistance.

Confession: the reason for nGen Field to cause the white screen was the limited PHP memory on my local machine. I am running MAMP and MAMP Pro and it turns out that each uses their own - at different location - php.ini file.

Lesson learned is to double check your phpinfo if your modifications have been accepted!

Thanks to all & Fred Boyle (nGen) for your assistance.

Confession: the reason for nGen Field to cause the white screen was the limited PHP memory on my local machine. I am running MAMP and MAMP Pro and it turns out that each uses their own - at different location - php.ini file.

Lesson learned is to double check your phpinfo if your modifications have been accepted!

Thanks to all & Fred Boyle (nGen) for your assistance.

Confession: the reason for nGen Field to cause the white screen was the limited PHP memory on my local machine. I am running MAMP and MAMP Pro and it turns out that each uses their own - at different location - php.ini file.

Lesson learned is to double check your phpinfo if your modifications have been accepted!

Thanks to all & Fred Boyle (nGen) for your assistance.

For folks with this problem...white screens are quite arbitrary, so make sure and enable php errors while you are developing/debugging.

Try adding the following to the index.php file in your system file to see PHP errors on screen (instead of white blank) in the admin area, similarly, add this to index.php of your site root to see errors on the live site. (I just leave this line in both files and comment it out when I'm not debugging/troubleshooting). Don't forget about enabling PHP errors in php.ini and there are some debugging features within EE you can turn on as well.

//ini_set('display_errors', 1);

I ran into a file size upload limit problem (which has nothing at all to do with Field Frame) because my staff were trying to attached 5MB+ files to articles (for download). I had to up memory limit from 32mb to 64mb on server (php.ini). If it is not an ngen file field thumbnail batching issue and If you don't have a private or virtual server to yourself you may have to face the reality that http != ftp and turn to FTP uploading of large files.

I had to insert this line in my .htaccess file to fix the memory problems:
RLimitMem 128000000

It may also help to read my post here about image sizes http://expressionengine.com/forums/viewthread/110252/P540/#696440

This happens to me whenever I forget to set the file upload directory with the nGen File Field.

Hi I had this problem but was able to temporarily up my memory limit to 255MB.
I then went and tried to publish the effected sections and they appeared okay.
This seemed to clear the problem and I then lowered the memory limit back down to 100MB.

We are having this problem also. I realize this is a 2 year old thread but it doesn't seem like there was ever a viable solution. We have already had the host up the php memory. We are running EE 1.7.1 with Matrix 1.5 and nGen .9

I have had the same issue. We had to release 2048M memory but even then, the front end crashes in almost every browser. This is a Matrix field of 7 columns, 4 of which are Playa fields. We have about 220 rows.

Is there any solution to this? It seems not.