Title: Fatal error given by automatic update
Last modified: August 24, 2016

---

# Fatal error given by automatic update

 *  [mard](https://wordpress.org/support/users/mard/)
 * (@mard)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/)
 * I got an email from WordPress saying my blog had been updated automatically. 
   However, when I attempt to log in I get the following:
 * Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate
   7680 bytes) in /home/mard/public_html/blog/wp-admin/includes/deprecated.php on
   line 1131

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056175)
 * – first, try [increasing memory ](http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP)
   available for php.
 * – if the issue still persists, try troubleshooting steps suggested here: [https://wordpress.org/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5](https://wordpress.org/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5)
 *  Thread Starter [mard](https://wordpress.org/support/users/mard/)
 * (@mard)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056343)
 * I increased the memory by writing in new numbers. And yet, no matter what I do,
   even when I put the original numbers back in, I always get a parse error like
   the following:
 * Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/mard/
   public_html/blog/wp-includes/default-constants.php on line 23
 * The line number 23 at the end changes depending on the values but always points
   to a line where I inserted a new number, even when I put the original number 
   back in.
 * I foolishly did not save the original version of the file. So, clearly I’m not
   editing right or something. Have no idea at this point.
 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056344)
 * Have you attempted troubleshooting steps suggested here: [https://wordpress.org/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5](https://wordpress.org/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5)
 *  Thread Starter [mard](https://wordpress.org/support/users/mard/)
 * (@mard)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056514)
 * Yes, I’ve read the troubleshooting steps suggested.
 * But the parse error I’m getting does not go away.
 * As I said, I did not save the original version of default-constants.php so I 
   can’t see what change I made. To me, the file looks exactly the same because 
   I did replace the original memory numbers after I experimented with changing 
   them.
 * Is it possible for me to obtain the correct — before any memory changes — version
   of default-constants.php? I would at least like to duplicate the original Fatal
   error I got so I could start again from scratch!
 * Thank you for any possible help.
 * Link to site: [http://www.mcseavey.org/blog](http://www.mcseavey.org/blog)
 *  Thread Starter [mard](https://wordpress.org/support/users/mard/)
 * (@mard)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056548)
 * if ( !defined(‘WP_MEMORY_LIMIT’) ) {
    if( is_multisite() ) { define(‘WP_MEMORY_LIMIT’,‘
   64M’); } else { define(‘WP_MEMORY_LIMIT’, ‘40M’); } }
 * Where is the parse error in the above?
 * Anybody at all? Anybody at all?
 *  Thread Starter [mard](https://wordpress.org/support/users/mard/)
 * (@mard)
 * [11 years ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056552)
 * I guess I’m not getting any responses here. Thanks to Tara for at least giving
   me a suggestion. Perhaps I’d better repost this on Requests and Feedback?
 * I feel kind of crestfallen that I was notified of an automatic update to 4.1.3
   only to find that I was automatically updated into a fatal error and then to 
   a non-obvious parse error when I changed memory sizes and then reverted to the
   original sizes. See above comment. Crazy.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Fatal error given by automatic update’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 6 replies
 * 2 participants
 * Last reply from: [mard](https://wordpress.org/support/users/mard/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/fatal-error-given-by-automatic-update/#post-6056552)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics