I upgraded to v2.2 of Socialized This yesterday. Today I realized that a post I published this morning didn't get pushed out to twitter. Investigating the Advanced Settings, I saw that my OAuth Consumer Key and Consumer Secret fields were now blank (and that there is now a field called @Anywhere API Key, which I have no idea what to do with).
Figuring I'd start from scratch, I revoked access to my old Socialize This app in Twitter. Back in the WP admin, I deleted the old twitter configuration in the plugin's Settings. I then followed the steps of your OAuth tutorial video to redo it; however, the dev.twitter.com "create an app" section has changed a lot. I did my best and ended up with new OAuth consumer key and secret codes, etc. Beneath the field to put in your callback URL in the new dev.twitter interface, there's now explanatory text that says
Where should we return after successfully authenticating? For @Anywhere applications, only the domain specified in the callback will be used. OAuth 1.0a applications should explicitly specify their oauth_callback URL on the request token step, regardless of the value given here. To restrict your application from using callbacks, leave this field blank.
No idea what any of that means. I put in my blog's home URL as the callback URL.
I went back and finished putting in the OAuth keys and re-connecting my blog to twitter in the Socialize This settings. I customized the Twitter New Post update template to say
Cheek and Bluster: %permalink%
The test tweet went through OK, and the widgets showed up correctly in my blog. Unfortunately, when I clicked on the twitter icon to tweet my new post, the resulting pop-up window to send the tweet said
Currently Reading http://cheekandbluster.com/wordpress
The same thing happened when I clicked to Facebook icon.I've kept the plugin activated, but disabled all the social widgets since they're not working right. Need help - what should I do now?