Fatal error given by automatic update

– first, try increasing memory available for php.

– if the issue still persists, try troubleshooting steps suggested here: https://www.ads-software.com/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5

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.

Have you attempted troubleshooting steps suggested here: https://www.ads-software.com/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5

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: https://www.mcseavey.org/blog

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?

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.