WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] White screen due to jetpack (6 posts)

  1. oldmankit
    Member
    Posted 2 years ago #

    Hi,

    I have just spent over one hour troubleshooting my very first "white screen of death". I feel quite proud.

    I tried several things and in the end deactivated all plugins (by renaming the plugin folder), then installing them one at a time to see which was the culprit. It was jetpack. When I clicked 'activate' I got this error:

    Plugin could not be activated because it triggered a fatal error.

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in ..../oldmankit/wp-content/plugins/jetpack/modules/contact-form/admin.php on line 219

    I don't really know what to do about this other than not use jetpack.

    I wonder if other people have the same problem. I tried adding this line to wp-config.php, but it doesn't seem to help:

    define('WP_MEMORY_LIMIT', '64M');

    Anyway, I don't really want to increase my memory limit if I don't have to.

  2. oldmankit
    Member
    Posted 2 years ago #

    I found the same error when I tried to re-activate W3 Total Cache.

    I want to use that one, so any help troubleshooting this is much appreciated!

  3. oldmankit
    Member
    Posted 2 years ago #

    I am going to open a new thread with a more appropriate title.

  4. Really, do not do that please. We close duplicates when we find them and the title isn't that bad ("White screen" is the clue).

    Memory usage is tricky. On my multisite installation my memory limit is set to 80M and that works for me. Some themes and plugins are needlessly memory intensive and push your installation over the limit.

    Bump up your memory temporarily and give this plugin a look. It's helped other people identify the memory hog on their WordPress.

    http://wordpress.org/extend/plugins/memory-viewer/

    If it does help you identify the plugin you can contact the developer and see if it can be trimmed.

    Edit: also look to bump up your memory in php.ini too.

  5. oldmankit
    Member
    Posted 2 years ago #

    Problem was solved by increasing memory to 64 MB.

  6. oldmankit
    Member
    Posted 2 years ago #

    @Jan, thanks for explaining, and for the tips. I will try that plugin.

Topic Closed

This topic has been closed to new replies.

About this Topic