mard

Thanks, ItalyExpat. I’ll do that.

I found the offending plugin. It’s “jetpack by WordPress.com”. When this is deactivated I can display long posts of well over 100 words which would not display when “jetpack by WordPress.com” was activated.

Now when I again activate this plugin I get an error message that I cannot connect to wordpress.com. But I have not lost the ability to display long posts.

So, there’s still something wrong. But in any case, on www.ads-software.com and I can display long posts.

Thank you for the suggestions.

I performed Step 1 and found that the long post was then displayed. So, one of my plugins is causing the problem. I’ve now disable and reenabled four of the plugins but have not found the culprit yet. I’ll continue with this.

Thank you again.

I think I’ve got it now. I went carefully through them all and found lots of them that were not yet verified with the present version, and some were really old ones that were essentially useless. So, now I think all is OK. Whew…. unless….. no no forget that!

Thank you very much for your patient counsel!

OK OK I see what I did! I forgot to activate the plugins!

Now as I activate them one by one everything is OK until I get up to the plugins that begin with “w”. It looks like two or three of them are causing the problem. Right now I’ve had to rename wordpresscom-stats-helper, wp-db-backup, and wp-postviews.

I’ll have to work more on this but I’m taking a break now.

This morning, instead of doing what you recommended first, James, namely to try deactivating plugins and switch themes, I tried your 1. and 2. above. I was able to do 1. OK but was not allowed to modify the .htaccess file. And I still got the Fatal error when I tried to access wp-admin.

So, I went away, visited my friend, had lunch and a walk on the beach with her here on the rugged coast of Maine. I worried that I’d have to contact my blog’s host.

Now I come back and find no more fatal errors! Everything seems to be working! I did notice an access to my plugins at 8:24 this morning. Anyway, it appears somebody fixed it! Many many thanks!

But I’ll give it a little more time before I change the topic to “resolved”. Maybe I’m hallucinating or something?

Now when I try to log in I always get:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /home/mard/public_html/blog/wp-admin/includes/theme.php on line 457

No mention of memory size anywhere near that line.

I did it all, after downloading Cyberduck, and was able to log in to my blog, but then after the Update Complete message I got the following:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /home/mard/public_html/blog/wp-admin/includes/theme.php on line 371

I took a look at theme.php line 371 but couldn’t make much sense out of it. I notice the number of bytes, 67108864, is the same as what I originally got after I was automatically updated.

Thank you for that. That will take me awhile and I’ll try to be careful. It’s been a long time since I’ve done any serious work with WordPress. So I’ll be cautious.

I tried each of those suggestions, i.e., renaming plugins to plugins.hold (and back) and tarski to tarski.hold (and back) but neither produced a change. I still get this message:

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/mard/public_html/blog/wp-includes/default-constants.php on line 23

Thanks for these suggestions, James. I’ll try them out. Thank you.

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.

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?

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

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.