Hi JPSKILLZ,
I see which part of the code is causing a problem. I just need to confirm why a problem is being caused. I will implement a fix and push an update out shortly.
OK Great! Please let me know once you do?
I have just pushed out version 0.5.6!
This should remove the potential for the plugin causing a fatal error. It was calling ‘unset($tweets[‘expiry’]);’, when the contents of $tweets was a string. I have made sure it only calls unset when $tweets[‘expiry’] exists.
However, it does not explain why the contents of the variable ($tweets) was not as expected. If you notice anything else odd/wrong with the behavior of the plugin I would appreciate any feedback/information you can supply.
Okay. It is now telling me this:
Fatal error: Cannot unset string offsets in D:\Hosting\11636073\html\wp-content\plugins\kebo-twitter-feed\inc\get_tweets.php on line 70
Okay,
I am going to remove the unset code in the next update to avoid the fatal error. I will post back once it is live.
Okay. Let me know please?
The next update is live. This should solve that particular error, but it may show us more problems. Let me know how it goes.
Oh sorry man! Working on some other edits, one sec…
Okay! We’re making progress. It says “Sorry, No Tweets were found.”
No problem at all.
Okay, this would suggest there is a problem fetching the Tweet data. Which is strange for this to happen after it has been working.
If you go to the plugin options page is anything listed in the error log at the bottom?
If there is nothing in the error log, would you be able to let me know the screen_name of the account?
Also, if you don’t mind a bit of dirty troubleshooting, would you be able to run the following code somewhere (any template file) and send the output to [email protected]?
<?php
$tweets = kebo_twitter_get_tweets();
print_r($tweets);
?>
This will let me see what is currently being stored/returned by the plugin.
It’s not showing any error messages. The screen name is @MiCorazonCanta. Not sure where to run the code? Do you mean in the CSS Editor?
Don’t worry about the code, it’s dangerous playing with PHP if you aren’t comfortable with it. That’s no problem.
Okay, so no error’s is a good sign. It catches WP errors making the request and Twitter API errors.
I will watch the console for a little while and make sure that requests are going through for that account name. Ill post back again soon with what I find.
Is this on a production server, or running in a local development environment at the moment?
I haven’t seen any requests yet, if it is not already, would you be able to set it to refresh every 1 minute in the options page, and then occasionally refresh the site so it is making calls please?
