A bunch of folks in the WordPress support forums appear to be having trouble with Twitter Tools with WordPress 2.9. It works as expected in my testing, the WordPress HelpCenter hasn’t been able to reproduce this either, and the works/broken voting on the plugin page is fairly evenly split.
I’d love to gather some explicit bug reports (this thing breaks here, this code on line X appears to fail, works with all other plugins turned off but not with plugin Y enabled as well, etc.) and/oor access (both WP admin and file editing) to an environment where this is 
breaking 
consistently with WP 2.9 and previously worked with WP 2.8.x.
If you use Twitter Tools, could you take a moment to vote if it works for you with WordPress 2.9?1
Thanks in advance.
UPDATE: Interesting – when I posted this the vote was 12 working vs. 17 broken. The current vote is now 31 working to 20 broken. So far since I posted this another 22 votes have been cast and 19 of them indicate it is working. This seems to be far from a widespread issue, which probably helps explain why no one I know can reproduce it.
- I realize that this type of call to action will by nature result in more unhapy voters (more “broken” votes) than otherwise – this is the nature of such things. [back]
This post is part of the project: Twitter Tools. View the project timeline for more context on this post.
Is this perhaps another symptom of the same issue as the “infamous” 2.9 CURL bug?
http://wordpress.org[...]-9-1-beta-1/
http://core.trac.wor[...]ticket/11505
Could be – I’m honestly rather unclear about the actual symptoms of the “problems” being experienced.
Hi Alex, Twitter Tools seems to work fine here, and I’ve voted at WordPress Extend to indicate so.
However, I’ve had two minor duplicate-daily-digest issues yesterday and the day before (but not today).
Works for me.
However, I know what might be the culprit.
You’re including the JSON class in the twitter tools file. WordPress 2.9 actually has that class built into it now. However, the class only actually gets loaded by WordPress if the version of PHP itself lacks the built-in json_encode and json_decode support. In that case, WP loads up the class and creates functions to emulate those classes.
This could create a situation where anybody running on an older PHP 4 would have problems but people on a newer PHP 5 would not.
Best bet for 2.9 and up: Stop using your own JSON library code. Just call json_encode and json_decode for your json needs. WordPress has you covered with the compatibility layer.
I have that wrapped in a class_exists check and I’m not calling the native json_* functions, so I don’t see why this would necessarily cause a problem, though I can see a few situations where it could.
I hate doing version checks, but I guess I could add that to try to avoid potential conflicts.
Hi, Alex. I am having a minor issue with Twitter Tools since upgrading. Mostly, I’ve ignored it, but it might be an issue for other people.
No matter what I choose and save for “Exclude @reply tweets in your sidebar, digests and created blog posts?”, my @replies show up anyway. At least, they do in my sidebar. I don’t have my tweets conglomerated into digests and posts.
I currently run the latest build of WordPress, though I’ve been having this problem since 2.9.0.
Sorry. I voted broken. Here’s what happens.
Every new post, I hit ‘publish’ and get the failed message. Go to posts where it is a draft and hit ‘publish’ and then it publishes. Deactivated plugin and tested and published immediately.
If I can provide assistance, please let me know. I’ll offer what I can.
Patrick
I think the problem is something involving the autosave and the new post page.
When I have a post and it autosaved, when I go to save draft or publish, I get the error. When I go to edit the post, I can edit it and it posts immediately.
When I changed the code and turned autosave off, it worked just fine.
Now that I have updated to 2.9.1, the autosave is back on and have the same problem. When I deactivate Twitter Tools, it works just fine.
Hope that helps and let me know if you need anything else.
If it’s not working for you, it would be useful to get more information about your environment. Please install the WordPress HelpCenter plugin and use the link in the HelpCenter tab to send your profile to our HelpCenter staff.
http://wordpress.org[...]phelpcenter/
With the token created for us we will then be able to see the information on the System Profile page without needing to log into your WP admin.
If we can see any consistencies between configurations where this is not working, that may help us try to reproduce the problem some appear to be seeing.
I’ve only observed 2 “bugs” from using it on my site (2.9):
#1 The last weekly digest was duplicated (prior to 2.9 this was being generated fine)
#2 the bit.ly plugin didn’t generate a link at all (only just tried it out and have turned it off again)
I’ll look at submitting the profile for you to have a look at in the hopes it will help diagnose what’s going on. I know these things can be a nightmare to diagnose…
Paul
I had a problem with Twitter Tools when I used the new video embed feature in WordPress 2.9.
But after upgrading to WordPress 2.9.1 earlier today, everything seems to be working fine.
Nigel
Hi Alex TT2.0 and WP2.9 as well as WP2.9.1 does not work for me to (Twitter Authentication-Error).
Somewhere I read about issues regarding the twitter-password. Mine contains Upper, lower, numeric and special characters plus it’s >8 chars.
I just uploaded my System-Profile using the WP HelpCenterPlugin.
Hope that helps.
For me, it’s not a WP 2.9 issue.
Some time during the previous WP release (2.8.6?) Twitter Tools stopped posting my weekly Tweet digests back to my blog.
Prior to that it would occasionally post 6 identical weekly digests of my tweets. But then it just gave up bothering to post the weekly digest at all, and I’m now doing it manually.
It’s stilll fine at tweeting my new posts to Twitter.
Haley, Paul Campbell, Karsten and Philip – please contact the WordPress HelpCenter, our team should be able to work with you to resolve your issues.
For me, it works the same on 2.9 as it did on 2.8. Sometimes it posts duplicate (or more) digests, but it was doing that already.
My problem is the same as Philip’s – since some time during the WordPress 2.8 series, twitter tools stopped posting weekly digests.
When I tried to reset the installation by clearing out the twitter tools options from the database and reinstalling the plugin, I got weekly digests to work once, but then it stopped again.
I suspect that this is due to some interaction with another plugin, because I have another blog running the same verson in which weekly digest posts work.
I’m having the exact same issue that Patrick D describes above.
Unfortunately “me too” comments when I’ve already stated that all attempts to reproduce this issue have failed are not particularly constructive.
Perhaps you could send in a system profile to assist in debugging as recommended above.
Thanks.
OK, I’ve sent in the system profile.
I upgraded a WordPress blog to 1.9.1 running Twitter tools 2.0 and got the posting error others have described.
I noticed other similar installations of mine on other servers were working fine. So, I moved the blog with the posting error to one of these other servers and the problem was fixed.
It was a straight rsync of all the files. MySQL version changed, web server changed from nginx-fastcgi-php to apache-fastcgi-php, but I think the most significant change was the version of php, 5.1.2 (on Ubuntu Dapper) to 5.2.4 (on Ubuntu Hardy).
Hope this helps (I tried registering for the wordpress help center but never received my password email).
I am having issues but I don’t know if it’s the same thing. When I upgraded to 2.9, every time I would post a new blog entry it would fail and I would have to edit and publish it using the autosaved version. Disabling twitter tools fixed it.
That part is the same as the others but what isn’t the same is that now every time I try to enable Twitter tools, my entire site crashes. The error I get is this:
Fatal error: Cannot redeclare aktt_widget() (previously declared in /home/content/j/l/a/jlacroix1982/html/itnewstoday/wp-content/plugins/twitter-tools/twitter-tools.php:921) in /home/content/j/l/a/jlacroix1982/html/itnewstoday/wp-content/plugins/twitter-tools/twitter-tools.php on line 921
This is horrible for me because twitter-tools became such a crucial part of what I do. I have it all turned off now but would like to use it again eventually.
That error sounds really strange, you might want to consider contacting the HelpCenter for troubleshooting on that one.
http://wphelpcenter.com
Thank you. I may do that but not for a while because I don’t have any money to pay for service. (I am not currently making any money on my site at this time).
I got an email back from the HelpCenter that said “We believe we have identified a bug in
the plugin and are working on a fix.”
[…] on the feedback from my previous post, I think I know what the issue may be between Twitter Tools 2.0 and WordPress […]
[…] C: wait…Related articles by Zemanta10 Simple Ways To Boost Your Blog in 2010 (bloggingot.com)Twitter Tools and WordPress 2.9 – Working or Not? (alexking.org)How To: Promote Your Twitter Profile with TwitterCounter (wpjedi.com)You might enjoy […]