Sorry, no Tweets were found.

Hi ActuallyAKA,

We are very sorry that you had problems using the plugin. We have been working very hard to fix the character encoding issues that people have been experiencing. This was causing the Tweet data to be corrupted resulting in the plugin thinking it could not find any Tweets.

The latest version (0.7.3) should fix this, and if not I have made a debug version of the plugin which will send me the Tweet data so that I can identify what has caused it to become corrupted and fix it quickly. So if version 0.7.3 does not work you can download the debug version here:

Kebo Twitter Feed – Debug Version

We hope that you will give us a chance to show you how hassle-free and easy to use this plugin can be.

P.S. We all love that Kebo means Buffalo in Indonesian, thank you SO much for letting us know. Powered by Kebo now has a new meaning for all of us, haha!

Hi Peter,

Thank you very much for your response. I see, so it’s all happened because of character encoding issues.

I updated to latest version but got another error

Fatal error: Cannot unset string offsets in /public_html/blog/wp-content/plugins/kebo-twitter-feed/inc/widget.php on line 60

Here’s the link of my blog to help you find the problem:
https://blog.anthonykusuma.com

I hope you could help me. Thanks a lot! ??

Hi ActuallyAKA,

I am very sorry I missed this and it has taken me so long to respond. I am also dissapointed that my attempt to change your opinion about the plugin caused you more problems.

I have updated the plugin (0.7.6) and changed the way we deal with the ‘expiry’ time at the end of the array of Tweets, which we were unsetting which caused your error.

If you have any more problems please let me know and I will deal with them as soon as I can.

Hi Peter,

It’s okay. Please don’t be that sorry. ??

I updated to latest version and got another error:

The Tweet data is not in the expected format.

Do you have any idea about this error? Looking forward for your help. Thanks a lot, Peter! ??

Me either. The tweets data is not in the expected format.

Hi ActuallyAKA (and D Nan),

This error means that something caused the Tweet data to be corrupted while being processed by WordPress. This is usually caused by charater encoding issues.

I have identified the cause of the problem in D Nan’s tweets and I am looking through yours. Once I have identified both I will get both cases fixed and push out an update and post back here to explain what caused the problem.

Hi ActuallyAKA,

I have worked on this all today and it appears to have been caused by Unicode characters at the beginning of Tweets. While they appear as a single character they exist in this format ‘\u203d’. I use data from twitter to work out where hashtags and mentions were positioned inside the Tweet text. This counted each Unicode character as 1, but for me it was actually 6 characters. This caused me to wrongly replace text which resulted in corrupting the Tweet data.

I have created a test version for this fix, which you can download here. This may well fix the issue and, if not, will email me the content of your Tweet data so that I can easily identify the exact cause.

Thank you for all your patience, it is very important to us that using this plugin is a seamless and hassle-free experience to everyone. Your feedback and help is invaluable in reaching that target.

I have just had some help troubleshooting with another user, where a specific character was causing problems. However, this same problem did not happen on my test systems, which means there may be a PHP version specific (or another variable) issue.

He solved the issue by deleting the specific Tweet causing the problem, but I am continuing to work on why and how that character caused problems, so that I can fix it for all users.

Hi Peter,

Thank you so much for your effort. I really appreciate that. ??

I downloaded the zip file but still face the unexpected format issue. ??

for your additional information, my PHP version is 5.3.27

Thank you! ??

Hi ActuallyAKA,

I have finally tracked down the issue and am working on an update right now (it will be 0.9.x) once it is really. I just wanted to let you know, apologise and explain what happened.

WordPress uses the serialize and unserialize functions, to format data in a text string, before saving data to the database. However these functions do not handle Unicode characters. I was wrongly under the impress that WordPress used the json_encode and json_decode functions, which do correctly handle Unicode characters.

My recent patches were infact not working, but for most people this was hidden. The plugin not having correctly saved the data, was fetching the Tweet data from Twitter before rendering the page. For some, still unknown, reason some sites (like yours) while not correctly saving the data in the database, were still having a half serialized return from the database, which was causing the “Sorry, no Tweets found.” and “Tweet data is not in the expected format.” error messages.

I believe that by me doing the serializing with json_encode before sending the data to the database and then unserializing myself when fetching it using json_decode, that I can successfully store the Tweet data for everyone no matter what is in the content.

I should have a patch out later tonight and now I can consistently reproduce the error I am very confident that this fixes the problem.

The update for 0.9.2 is out now and I am very confident it will resolve the issue you had.

The problem was that WordPress serializes data into a single text string to store in the database. The default serialize and unserialze functions were not correctly dealing with the Unicode characters and were leaving half serialized data in the database.

Now came the big problem, depending on the PHP version fetching the Tweet data either returned ‘null’ and the plugin refreshed the Tweets before loading the page (which essentially hid the problem) or returned a half serialized string, which could not be used to output Tweets (and triggered the error you got).

I resolve this by managing the serialization myself using json_encode and json_decode, which cope with the Unicode characters. I am genuinely sorry to all our users who have been effected by our handling Unicode characters badly.

I hope you will give us another try, but if not, thank you very much for all your time (and for giving us a second chance).

Hi Peter,

Sorry for this late reply! Now the plugin is working like a charm! ??
Thank you very much for your efforts! ??

can I change the stars btw? ??

Hi ActuallyAKA,

I am so thrilled it is working for you now. I am very dissapointed that it took me so long to track down and solve the problem. You were incredibly patient with me while I attempted to solve the problems, far more patient than I could have ever expected. Thank you for your support.