Navigation
This is archived content. Visit our new forum.
  • Author
    Posts
  • #56171

    Deborah P
    Participant

    Hi everyone,

    I have been coming across the following error message today:
    (The website is http://www.test.moneycoachinginstitute.com)

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 46 bytes) in /home/mci2009/public_html/test.moneycoachinginstitute.com/wp-includes/plugin.php on line 856

    It happens when I want to add another menu item to my navbar and hit ‘save menu’.
    I also earlier had the customizer load a blank page with the menu only on the side – but it seemed to resolve itself, its working again now.

    Since then, I read the forums and updated the X theme to 2.0 via ftp.

    I uploaded my old customizations, and when I tried to re-assign the primary menu – this error message came up, though the menu loads in the customizer ok:

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 80 bytes) in /home/mci2009/public_html/test.moneycoachinginstitute.com/wp-includes/plugin.php on line 401

    I installed the TCP!memory plugin – its telling me that memory is definately over the 32 MB limit (about 50-60MB) and the number of database queries ranges from 12-52.

    I contacted the host (hurricane electric) and asked if there was anything they could do re. memory on their end. They asked the following, which I don’t know how to answer, does this make sense to anyone?

    Do the forums mention anything regarding the use of caching plugins? WordPress by default tends to rely heavily on the database to store even the basic data. Some of the repetitious queries to this data can be cached using various different caching plugins such as W3TC and WP SuperCache.
    More information:
    http://codex.wordpress.org/WordPress_Optimization/Caching

    So in summary, my question is why is the site running into memory issues. Is it related at all to the Visual Composer issue mentioned in other topics? What can I specifically ask the host? Can I just change php memory setting myself? What is the root cause of this issue?

    Thanks,
    Cara

    #56410

    Christian
    Moderator

    Hey Cara,

    Memory issues are dependent on web hosts because they differ in setup. Please follow the recommended settings outlined in our Solutions to Potential Setup Issues in our Knowledge Base. You may also contact your web host to increase the memory for you.

    Thanks.

    #271133

    grantfeldman
    Participant

    Hi there,

    I am getting the exact same error message when I try to update X Theme.

    I have had my website running on the same settings for over 6 months and I have never seen this message before. Definitely not a memory issue as I have already ruled this out with my IT guy (heaps of memory left). I have also cleared all browsing data, cache etc. and I still get the same error:

    http://prntscr.com/745nqb

    Any other suggestions for a fix to this? Any help is appreciated 🙂 Thx

    #271246

    Prasant Rai
    Moderator

    Hello There,

    In that case would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

    – Link to your site
    – WordPress Admin username / password
    – FTP credentials

    Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

    Thanks.

    #271299

    grantfeldman
    Participant
    This reply has been marked as private.
    #271457

    Christopher
    Moderator

    Hi there,

    I wasn’t able to connect through FTP account, please check this link and make sure you have already tried provided solutions :

    http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    Thanks.

    #272189

    grantfeldman
    Participant

    Hi there,

    i updated the memory as per screen shot… same error.

    http://prntscr.com/74mq3t

    Could it possibly be another issue? I would be interested to see how Cara managed to resolve the issue… ?

    #272351

    Paul R
    Moderator

    Hi,

    I tried logging in to ftp to check but couldn’t login.

    Can you try adding the code below in your wp-config.php file located at the root directory of your site.

    
    define( 'WP_MEMORY_LIMIT', '256M' );
    define( 'WP_MAX_MEMORY_LIMIT', '512M' );
    

    You can add it after define('WP_DEBUG', false);

    Hope that helps.

    #273115

    grantfeldman
    Participant

    I’m so sorry guys, but I keep getting the same error:

    The update process is starting. This process may take a while on some hosts, so please be patient.

    Enabling Maintenance mode…

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 65488 bytes) in C:\inetpub\wwwroot\linkfit.net.www\wp-admin\includes\file.php on line 159

    I’m stumped… any other suggestions?

    #273247

    Rue Nel
    Moderator

    Hello There,

    Please double check the ftp details. We can not access your server using the given access information. Once we can log in, we can check your settings and fix it for you.

    Thank you.

    #274743

    grantfeldman
    Participant
    This reply has been marked as private.
    #274793

    Friech
    Moderator
    This reply has been marked as private.
    #275598

    grantfeldman
    Participant

    Hi – any news on this issue?

    #275634

    Rad
    Moderator

    Hi there,

    Oh, you can’t access private reply since this is not your thread. I’ll just re-paste it here excluding the screenshot.

    ———–

    Sorry I tried but still couldn’t connect. (Screenshot Here)

    Can you try adding the code below in your wp-config.php file located at the root directory of your site.

    define( 'WP_MEMORY_LIMIT', '256M' );
    define( 'WP_MAX_MEMORY_LIMIT', '512M' );

    You can add it after define(‘WP_DEBUG’, false);

    Thanks!

    ———–

    If you wish to continue our discussion in private. Then please start a new thread while linking here.

    Thanks!

    #289348

    grantfeldman
    Participant
    This reply has been marked as private.