Simon Wheatley

Have you authenticated with Twitter? There should be a prompt in the admin area of WordPress.

I can see two issues currently. The first is that the Google Contacts class sets const NAME = 'google-contacts';, but then uses a URL parameter for service of just google. I changed this on lines 165 and 179, see: https://github.com/cftp/keyring/commit/854022000fac7241024af6b47a2d4287bd012de0

Then I hit a thornier issue, which I’m not sure how to fix. The state parameter is missing from the GET parameters, so the validation in verify_token fails. I’m not sure whether this parameter should be set by Google or in the return URL we specify when setting up the service. Any suggestions, @beaulebens?

(@ozke – see message above)

@mattregister – Can you please check if the latest version from Github works for you? https://github.com/cftp/twitter-tracker/archive/master.zip

Thank you.

Changes:

• BUGFIX: Fix name clash by renaming a class (hopefully the last one)
• ENHANCEMENT: Show message in search widget when no tweets are found
• ENHANCEMENT: Add tt_no_tweets filter to tailor “no tweets” message

@peterdwdc – thanks.

(My email is simonw and my domain is codeforthepeople.com.)

People still getting the 500 error, please try the following:

If you have access to the error logs on your server, please trigger the error and then send the logs to me so I can see what’s going wrong. If you don’t know if you have access, please trigger the error, note the time and date, then write to your web host requesting the PHP error logs for that time.

If you are able to, please go through the following procedure:

1. Switch to a default WordPress theme (TwentyTen, TwentyEleven, TwentyTwelve) – do you still get the error?
2. Deactivate all other plugins – do you still get the error?
3. Reactivate your plugins one by one – which one triggers the error? Make a note, deactivate the other plugin, then continue on reactivating to check it’s just the one plugin clashing. Let me know which plugins are clashing.

Which page are you getting the error on? Is it just the authorisation page?

@timdudley76 – What plugins are active on the site where you have the problem which are not active on the site where you don’t have the problem? What themes are you running on both sites?

Thanks all.

I think this is one of my favourite things to forget to do too, so I entirely sympathise. ??

Could you paste some example common Swedish hash tags which use the special characters that I can use for testing, please?

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.

You’ll need to remove your code for dealing with Emoji before upgrading.

I’ve released a new version which you can update to through WordPress, version 3.3.3. Please let me know any issues.

Fixes the Twitter API issues, and adds options for dealing with Emoji.