Tweets not updating

Hi Michael,

You can use any of the SessionPod twitter ‘Following’ accounts or here’s a sample below. Also, you could try using a list I created from your previous suggestion called ‘splist’ which contains 89 of SessionPod’s 106 followers.

Thanks Michael.

Michael Flatley @michaelflatley
Ceol Tracks @CeolTracks
Portherhead @portherhead
Torcán Trad Band @TorcanBand
Bosca Ceoil TG4 @BoscaCeoilTG4
Discover Ireland @GoToIrelandGB
TG4 @TG4TV
Raidió na Gaeltachta @RTERnaG
Cobblestone Dublin @CobblestoneDub
TradConnect @TradConnect

Cheers Michael,
//Rob

Hi again Michael,

SessionPod has sent a new tweet today, but unfortunately it is not appearing under the sessionpod site screen name rule (unless I clear tweets cache manually – but I’ve left it uncleared for now for you to see)

Under the test site I created a single search rule for one twitter account. Tweets appeared only when I setup the rule and applied in the sidebar widget, but unfortunately do not update. Sorry Michael.

//Rob

Hi Rob,

The fetched tweets of the rules with some of their screen names including SessionPod are updated on my end.

It could be something to do with the max allowed packet option of MySQL. Can you send me your server system information? You can do that by going to Dashboard -> Fetch Tweets -> Contact and send the report via the contact form. It will attach your server information along with the messages.

Hi Michael,

Well, that’s great news…and I also noticed that tweets on the test site (search rule for a single twitter account) is updating fine. So you’re right, it must be something to do with the live site. I sent you the report as you requested and some additional info’ from the ISP as a comment that I’m sure you will understand better than me!

Thanks again for your patience with me Michael.

Best regards,
//Rob

Hi Rob,

That’s something new to hear. Your rule of the search tweet type gets updated but not timeline. It could be due to the limit of the PHP max execution time set on your server.

By the way, I haven’t received your report by email. It may have failed. The email report of the plugin may not be working on your server either.

I’ve uploaded a plugin called Server Information (Download) that lets you retrieve server information. So can you try that? And submit the info via the Contact form of my site.

1. Install and activate the Sever Information plugin.
2. Go to Dashboard -> Tools -> Server Information.
3. There, you have a form field named System Information. Copy that text and send it to me.

The plugin has an email functionality but probably it won’t work on your server as the used code is basically the same as the one used in Fetch Tweets.

Hi Michael,

Thanks. Unfortunately, it looks like you’re also right about the email report of the plugin not working on the server – the report email failed. But I did manage to send you some info via your contact form. I hope it’s what you were looking for. Let me know if you didn’t get it. Thanks again for your patience and time Michael…

…and Happy Christmas!!!

//Rob

HI Rob,

The information you sent via the contact form helps. Thanks.

Still there are some missing information I need regarding the MySQL settings of max packet size.

You mentioned in email that the Server Information field is empty so I’ve updated the Server Information plugin on GitHub. Download: https://github.com/michaeluno/server-information/archive/1.1.0b.zip (Make sure to uninstall the existent Server Information plugin.)

That development version has several divided text areas. I need the information of the MySQL section. Also, the email functionality may work in this version as there was a small bug. So please try sending an email via the plugin as well.

Merry Christmas to you too!

Hi Michael,

Thanks for the updated plugin. The plugin installed no problem, but when I go to Server Information all the fields (Client, WordPress, PHP, etc) are blank. But the plugin email did work ?? and I’ve sent you the result via your contact page.

Thanks again Michael.

//Rob

Hi Rob,

It is strange that all the fields are empty.

I received your email, which did not help much as the server information report was empty.

I’ve uploaded a development version 1.1.1b of the Server Information plugin. (Download: https://github.com/michaeluno/server-information/archive/1.1.1b.zip) This time, it displays information with a slightly different method. So can you try that? (You would need to uninstall and delete the existent Server Information plugin.)

What I like to know is the max packet size of MySQL of your server having a problem with Fetch Tweets. If you can know it without using that plugin, it is fine and you can just tell me it.

Hi Michael,

Thanks for coming back again so quickly. Yes, your new plugin looks very busy with information, so 1.1.1b is looking good. I copied the contents and submitted them via your contact page :). I hope it sheds some light.

Thanks Michael.

//Rob

Hi Rob,

The max packet size set on your sever looks fine.

Let’s check PHP errors on your test site then. You can enable error logging functionality by following the steps:

1. Open your wp-config.php in your WordPress installed directory.
2. Find a line staring with define('WP_DEBUUG'.

It should look like this

define('WP_DEBUUG', false);

3. Replace the line with

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define(　'WP_DEBUG_DISPLAY', false );

4. Save and close the file.

Checking Errors
1. Go to the page that shows tweets of Fetch Tweets and check if tweets are updated. If there is a problem with a plugin, errors should be logged in the log file at this point.
2. Open the directory .../wp-content/ and you should see a debug.log file. Open it and post the warning and errors.

You don’t have to do this on your production site as other plugins and the theme can also generate errors and warnings and the log gets mixed with those different programs. So it is better to do it on a test site.

Let me know the result.

Hi Michael,

I’m sorry to report but I think I may have another issue. I put the code into wp-config.php on the test site like you said, but no debug.log file appears under /wp-content/ (or anywhere else!). I double checked to make sure I was saving the wp-content.php file ok and I can see the enable error logging functionality code you said to put in are definitely there.

The only things I can see under /wp-content/ are four folders, plugins, themes, upgrade and uploads…no debug file ??

Am I missing something Michael? Maybe something else to turn on?

//Rob

Hi Rob,

Okay. Let’s try this.

In the step 3, Replace the line found in the step 2 with

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define(　'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

This is one of the examples introduced in this page.

Let me know how it goes.

By the way, regarding the plugin Server Information 1.1.1b, do you still see some blank fields (text areas)? If so, what are they?

Hi Michael,

I just tried that. It took a few minutes and then the debug.log file appeared under /wp-content/. Thanks Michael. By the way, I cleared the tweet cache on the test site before I took the contents of the debug.log file (see below)

[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27
[28-Dec-2014 11:22:36 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/library/admin-page-framework/server-information-admin-page-framework.min.php on line 27

Ok. I also put 1.1.1b on the test site. Below is list of unpopulated text areas…

WordPress
PHP
Plugin
Admin Page Framework

…all other text areas are busy with info’.

Michael, I noticed a /logs/ folder…in here there is a file called error.log. There’s a few entries but they all look the same (see below). Does this mean anything?

Web Server[2014-12-28 08:54:51] [core:error] [client 66.249.67.118:18189] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

//Rob

Hi Rob,

That helps.

I just tried that. It took a few minutes and then the debug.log file appeared under /wp-content/. Thanks Michael. By the way, I cleared the tweet cache on the test site before I took the contents of the debug.log file (see below)

[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50
[28-Dec-2014 11:22:33 UTC] PHP Notice: Undefined offset: 2 in /var/www/web/wp-content/plugins/server-information-1.1.1b/include/class/utility/ServerInformation_PHP.php on line 50

These are errors produced by the Server Information plugin. I’ve updated the plugin (1.1.1b02) so can you try that? You can get it with the same download posted above. And let me know if you still have blank fields.

Michael, I noticed a /logs/ folder…in here there is a file called error.log. There’s a few entries but they all look the same (see below). Does this mean anything?

Web Server[2014-12-28 08:54:51] [core:error] [client 66.249.67.118:18189] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

This seems to be a log of the Apache web server. You may ask your host about this error as I can only help with PHP scripts.

We want errors caused by Fetch Tweets so let’s wait for a while to see if new errors are logged.