Milan Dinić

Although I don’t know is this cause in other cases, I’ve found a bug that is preventing fetching of tweets in my case.

Problem is that Twitter Tools doesn’t have it’s own cron job, and is instead relying on Social’s cron job, which in turn doesn’t run always but only when option to automatically fetch new comments is selected in Social. (see Social::check_system_cron() and Social_Controller_Settings::action_index())

This means that if you have choose not to fetch comments (like I did, since I use Social only for Twitter Tools), tweets will never be automatically fetched.

Solution is to have built in cron job for Twitter Tools that will run always when plugin is active.

Google+ doesn’t have open API that enables posting from third party tools so I think that it’s not possible to implement this.

(Note: I’m not affiliated with plugin’s developers)

I’ve just migrated one multisite installation and it worked except for tables $wpdb->blogs and $wpdb->site (plus one usermeta field) where URLs didn’t have protocol and since this plugin searches for whole URL those fields weren’t changed.

So, value in those fields was example.com but setup suggests URL http://example.com which means that plugin won’t even look at those fields since they don’t match search criteria.

I suggest that plugin takes into account domain name and not just whole URL since this will affect fields that don’t use protocol for any type of installation, not just multisite.

Removing protocol from setup form isn’t best idea since someone might want to change protocol of the URL, from HTTP to HTTPS or vice versa.