WordPress.org

Ready to get started?Download WordPress

Forums

Job Manager
[resolved] Fatal Error: Allowed memory size... (5 posts)

  1. definition
    Member
    Posted 3 years ago #

    Please help!
    All of the applications suddenly disappeared from the Applications List in my admin and it states the following error:

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 77 bytes) in /home2/homestg0/public_html/wp-includes/meta.php on line 197

    I went to that line in the meta.php file to see if I could adjust or increase the memory size, but didn't see anything to adjust there. I was using version 7.7 of Job Manager when it happened. I updated to 7.13 and error is still there. Do you have any suggestions on how to fix this?

  2. Gary Pendergast
    Member
    Plugin Author

    Posted 3 years ago #

    In order to fix this, you'll need to increase the PHP memory limit. The easiest way to do this is to add the following line to your .htaccess file:

    php_value memory_limit 128M

    Alternative methods are to add this to your wp-config.php:

    ini_set( 'memory_limit', '128M' );

    Or this to your php.ini:

    memory_limit = 128M

    (This last one will need an Apache restart.)

    If you are unable to do any of these, you will need to contact your host to increase your PHP memory limit for you.

  3. definition
    Member
    Posted 3 years ago #

    You're awesome!

    It works! Back to normal. Thanks!

  4. fox7
    Member
    Posted 3 years ago #

    We have some big problems with memory and this plugin.

    We've tried wp-config and php.ini, unfortunately we can not edit .htaccess.

    Once we activate this plugin, the whole site goes down.

    What makes this plugin so memory intensive?

  5. itsbarry
    Member
    Posted 3 years ago #

    Hello, just bumping to report that the 2nd method worked for my install on a shared server at bluehost.com.

    Editing .htaccess didn't seem to do anything, but editing wp-config.php did the trick. I suspect this will survive subsequent WP core updates.

    I suspect bluehost would have edited php.ini and rebooted apache for me but I didn't feel like asking them before trying to repair things myself.

    good luck everyone

    Barry

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic