NextGEN Gallery 2.1.7 Causes White Screen

I have the same issue as above ^^. I just rolled back to whatever version was previously installed (took the plugin folder out of a backup) but it still white screens. The error log is coming back with:

[17-Aug-2015 23:20:37 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in /home/user30242/public_html/wp-includes/class.wp-dependencies.php on line 230

@ryan360 – Although I suspect a PHP Memory Limit issue, please start your own topic so we can try to help you with your specific issue on your specific site.

See https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

Thanks!

– Cais.

@johnrmath – The error message you are indicating points to the WordPress uninstall routine not working correctly, you will most likely have to manually delete the plugin folder from your site so you can re-install NextGEN Gallery.

This may also be pointing to a corrupted NextGEN Gallery installation to begin with and you might consider re-installing the current version of NextGEN Gallery while all other plugins are deactivated as a troubleshooting test as well.

– Cais.

We tried your each step of your solution and we still have the problem. Right now we have everything else working on the site, except for NextGEN 2.1.7. We really need our galleries, since we are an online art gallery. Thanks.

I just had BlueHost restore the NextGEN Gallery Plugin back to August 1, 2015 and when activated the Plugin still causes the white screen.

Are there any other files that should also be restored which would take care of this issue?

@johnrmath – Are there any other error messages appearing on the screen or recent entries in your error_logs?

– Cais.

My web designer was just able to correct the issue but we are using NextGEN 2.0.79 to run the galleries. Thanks for you help.

@johnrmath – Does the issue return if you use the latest release of NextGEN Gallery? That would be the key to get sorted out.

– Cais.

Jeez, it just cost me several hundred dollars to get this fixed. I cannot take a chance on that happening again.

@johnrmath – I’m not sure why it would cost you anything to get an issue fixed unless it was some sort of customization you paid for.

If it was a modification to our plugin’s core code then it might be useful to share that so we can review if it can or should be integrated into future releases.

Thanks!

– Cais.

There’s definitely something wrong still. Johnrmath, can you please post some information as to what you had to do to fix it?

@ryan360 – contact me through https://www.lightspacetime.com and I will put you directly with my designer and you can deal directly with him. Thanks.

johnrmath

@johnrmath – Thanks for following up on this.

– Cais.