lmashton

This is not specific to 40andholding and it is not resolved. It is appearing on multiple sites of mine as well, and none of them have the same theme.

And when I did a search on “yoastmark”, all sorts of search results appeared with the same “yoastmark” in these people’s blog images, too. It’s a problem.

I like the Yoast plugin, but I’m at the point of having to stop using it because it’s causing such a huge problem with my images. And yes, the problem goes away when the Yoast plugin is not active.

The problem is now resolved. Here’s what happened for others who come after me.

This problem was *not* caused by any themes or plugins. I had deactivated ALL plugins except Jetpack and changed the theme to twentytwelve and twentyten (I tried both) and Jetpack still did not connect to wordpress.com. That’s the state of my wordpress installation when I ran all those tests above.

As Karen pointed out, there was whitespace before the “XML-RPC server accepts POST requests only.” when I ran https://lmashton.com/xmlrpc.php.

So I went through the article Karen linked to https://codex.www.ads-software.com/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

That article said to:
Check that the very first characters are <?php
Check that the very last characters are ?>

So there should be no spaces, tabs, or empty lines before or after those characters. I had three empty lines at the very end of the file after the last ?>. I deleted those empty lines and tried connecting Jetpack again to wordpress.com (with my theme and plugins activated). It now works.

Karen, thank you for linking to that article. I spent quite a bit of time yesterday hunting for information on how to resolve this issue and that article never showed up in any results nor was the space issue in the file hinted at in anything I read.

Done. My apologies for posting in the wrong place.

I had the same problem as everyone else above, basically, in combination with all the custom fields I’d created disappear, and 32 new blank ones created. What a mess.

On my blogs (three, by the way), without the bit.ly plugin, no URL at all was given in the tweet, long version or short, so I had zero luck with getting anything resembling any kind of URL on any tweet.

For the record, the behavior I mentioned in previous tweets was identical on all three blogs.

My username and API key were correctly entered. That was double and triple-checked. Twitter Tools didn’t post a URL with the tweet regardless of whether or not the bit.ly plugin was activated and set up. It didn’t work no matter what I tried.

That makes it a bug.

Happened to me as well. I left a comment on the developer’s site informing him of the bug, but his only response was to try to sell me technical support services.

I’ve since switched to other plugins.