Support » Plugin: WordPress Gallery Plugin - NextGEN Gallery » Blank page (FF) / HTTP ERROR 500 (Chrome)

  • Resolved kraeMit


    I’m receiving this NextGen errors in my debug log:

    [24-May-2017 14:26:29 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 266319 bytes) in /is/htdocs/wp12700043_6ZW48X39ZF/www/ on line 142
    [24-May-2017 14:26:29 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

    If I deactivate the NextGen plugin (2.2.3) all runs well.

    The error occurs e.g. when I want to add a new product in WooCommerce (calls ./wp-admin/post-new.php?post_type=product), but logs indicates NetxGEN as error owner – what seems to be funny, because I don’t understand the connections beween this both different parts.

    NextGEN Gallery works so far, I can add pics and it shows my galleries.

    Can someone advice how I can debug deeper or what the reason may be?


    Best Regards

    • This topic was modified 3 years, 6 months ago by kraeMit.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author photocrati


    @kraemit – Generally messages like “PHP Fatal error: Allowed memory size …” point to the server PHP Memory Limit being not enough to handle the operations on the site.

    In this case, it appears you have a PHP Memory Limit of 128MB, I would recommend working with your web hosting service to have that increased … ask for at least 256MB (and also increase any other relevant limits that are normally set based on the PHP Memory Limit value).


    – Cais.

    Thanks for your support and your answer!
    You are right, my memory limit is 128MB. I’ve requested a change to my provider.

    What I don’t understand:

    The call which causes the error tries to add a WooCommerce product (–>./wp-admin/post-new.php?post_type=product). Why does the NextGEN Gallery plugin requests memory at thes point?
    From my point of yiew it is not called nor such an error should occur.

    Plugin Author photocrati


    @kraemit – Unknown, although there have been other unexplainable issues where WooCommerce was involved in the past. If the problem returns we would be happy to look further into it.

    Thanks for the update!

    – Cais.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Blank page (FF) / HTTP ERROR 500 (Chrome)’ is closed to new replies.