MomDad

Which Sitemap plugin did you opt for? Previously, I was using the tried and true “Google XML Sitemaps”, but I’m up for a change if you recommend a different one.

I’m going to make the switch away from Yoast today, and maybe revisit it a few months down the road when (hopefully) some of the major issues have been resolved.

Gosh, that’s embarrassing. My apologies for the false alarm, Joe — that was indeed the reason why.

Before upgrading to 2.4.5, I had moved the existing wp-to-twitter dir elsewhere as a backup, manually uploaded 2.4.5, and neglected to change its ownership.

Thanks for the rescue!

Ok, I’ve just gone through the process 3 times, each time manually editing the db and plugin files to mask it as 2.4.6 and prompt for upgrade to 2.4.7. Apache error logging with LogLevel set to “warn” catches nothing out of the ordinary during the upgrade process. In WP admin, the upgrade output is as follows:

Downloading update from https://downloads.www.ads-software.com/plugin/wp-to-twitter.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the plugin…
Could not remove the old plugin.
Plugin update failed.
Return to Plugins page

After each of the 3 run-throughs, the only file left in the directory is wp-to-twitter/js/jquery.charcount.js

Is it possible that the cleanup/removal routine of the old version is not actually removing the .js file and the js sub-dir as intended, and thus can’t delete the main wp-to-twitter plugin dir?

For certain privacy/anonymity reasons, I’d prefer not to submit a support request as-is, but I’ll gladly send you an anonymized copy of it if you can provide me with an email address to send it to.

It has only happened with WP to Twitter. I’ve gone through a multitude of other plugin updates between the last time it happened and this time, and all those worked without a hitch. I can’t say with any certainty that it’s not a conflict with another plugin, but that in itself would be a bit strange too to have a conflict like that during the upgrade process.

Since I no longer have a copy of 2.4.6, I’ll manually edit the plugin version in the db and the plugin files and force it to prompt again for upgrade. I’ll enable logging and see what, if anything, it spits out this time during the process.

So your posts are showing up and searchable by title in Google now after switching plugins, Jay?

Judging by the frequency of his posts here, it appears Joost doesn’t check these support forums all that often, so I’m figuring the likelihood of this and many of the other important issues getting looked into anytime soon is pretty slim.

Is the News Sitemap actually working for people? It refuses to include posts that I mark for inclusion as noted here.

Jay, if you wouldn’t mind, could you please report back here whether your posts start getting picked up again and are searchable by their titles?

I’m going to give it another week, and if I can’t track down the root cause of it by then, I’ll be switching to an alternative plugin as well.

I’m experiencing this same issue, and have yet to find a solution. I’ve gone through all of Yoast SEO’s settings, and everything appears to be in order. Before switching over to WordPress SEO by Yoast, all posts were being picked up by Google, and they’d always come up as the first Google result when searching their post titles. After switching to Yoast, none of them show up in a search, even though the sitemap does include them, and I can see in GWT that Googlebot is having no trouble with the sitemap.

I’m puzzled, frustrated, and so close to switching back to my old plugin instead of Yoast, which I’d really rather not do if there’s a way to resolve it.

I stand corrected! Very nice, thank you!

Just came here to post almost the same message.

On the demo site, it only appears to work on the “Register” and “Sign in” links in the header bar, but the same links in the Meta widget in the sidebar just go to the normal WP registration & sign in pages.

Hopefully that gets corrected in the next version, as it’s only 50% useful at the moment.

Also, the ability to have custom themes would be a nice feature addition — much in the same way that the very similar SimpleModal Login plugin offers.

Thanks so much for incorporating this feature into v2.4.5 — it works perfectly!

I noticed one minor typo in wp-to-twitter-manager.php, it’s missing the 2nd “#” after “modified”:

<li><?php _e("<code>#modified</code>: the post modified date", 'wp-to-twitter'); ?></li>

That did the trick — it works a treat now! ??

Thanks for the speedy fix, Mika, and for all your other great plugins — I’m a big fan.

Sorry, that should be “posts are programmatically updated” — didn’t catch the mistakes until after my allotted edit time was up.

I’m not sure that I explained it as well as I could, so to further what I said above, I should note that WP-to-Twitter is fine up until the point where there is a second update to the post. The initial post with the template as “New post: #title# #url#” is fine, the first update, using the default template is “Post updated: #title# #url#” is also fine. It’s at that point where things go awry if you have additional updates. If the post is updated yet again, and WP-to-Twitter is triggered, it attempts to tweet it with the same “Post updated: #title# #url#” template. Since it’s using the same format, there is nothing to uniquely separate the latest update from the previous as far as the tweet content itself is concerned, and Twitter ignores it as a duplicate. By adding in a #modified# tag — Post updated [#modified#]: #title# #url# — we have a new unique tweet in Twitter’s eyes, and it allows the tweet to go through.

That’s great news! I’m glad you liked the idea and that you’ve incorporated it in your latest build. I just saw the notification in WP that there was a new version available :D. Sure, “MomDad” and a link to my WordPress profile is fine.

One other idea I had that I toyed with the thought of adding in was an option to also do geo-location lookup on the IPs and display the IP’s country of origin in brackets after. I know there are some free/open-source geo-location lookup services/APIs out there, but haven’t dug any further into the idea. Usually for the top offending IPs, I’ll cut-n-paste and do a manual lookup at https://ip-address-lookup-v4.com for example. Having it do automated lookups would be handy, although it may add quite a bit of overhead if you have hundreds or thousands of IPs in the spam list, so I don’t know how practical that’d really be. Just an idea though ??

Thanks again — you made my day!

Works great! Thanks for so quickly resolving this, Paul.