I will investigate this asap, thanks.
I just tested on PHP 5.4.1 and did not notice an issue, I’ll have to check in 5.4 later. You are on 5.4.0 correct? And you’ve definitely narrowed it down to SMW?
Hi there!
No, actually the server is on PHP 5.4.12. Sorry, should have been more specific. So far 2 plugins have caused (different) issues. Yours and Google Analyticator. Yours on the front end, GA in the backend. Both work OK on my PHP 5.3.x localhost.
Same thing here.
PHP 5.4.12 giving Error 500 on the front end when the plugin is activated.
@pixelyzed,
What hosting do you use? Seems like it’s not a problem with PHP 5.4
I have also had to disable Social Media Widget on my website http://www.virology.ws as I was receiving 500 server errors. My site runs PHP 5.2.x. Disabling Social Media Widget took care of the issue.
Problems after update shown here:
Warning: Invalid argument supplied for foreach() in /home/thewebma/public_html/wp-content/plugins/social-media-widget/social-widget.php on line 463
Warning: in_array() expects parameter 2 to be array, null given in /home/thewebma/public_html/wp-content/plugins/social-media-widget/social-widget.php on line 467
I had this same problem on DreamHost, where I’m running PHP 5.3.5. Disabling the plugin or just the widget fixed the problem.
For those who received the 500 errors, are you able to check your error logs and send what it says?
@pixelyzed By any chance are you on Dreamhost as well?
My server’s logs had this to say (though I’m not well-versed in reading such files so hope I am copying the relevant data):
[Fri Mar 29 07:18:36 2013] [error] [client 218.30.103.148] (70007)The timeout specified has expired: Reading bucket failed (rcode=70007)
WordPress’s debug log said this:
[28-Mar-2013 14:42:41] PHP Notice: Undefined index: pinterest in /home/kgagne/mschallengeblog/wp-content/plugins/social-media-widget/social-widget.php on line 304
That error was then repeated for several other social media services (ie, Undefined index: aboutme
).
“PHP Notice” error level can’t bring site down. Or at least it should not.
Ken – Could you enable the plugin again for a second, and once you receive the 500 error, remember the time and check your server error logs and paste what you find here? I’m having trouble reproducing the error on my end and want to make sure I have the right error message.
Blink! I just reenabled the widget, thus bringing down my site. The timestamp on this error from my server log (not the WordPress debug log) matches the time of this experiment:
[Fri Mar 29 12:54:10 2013] [error] [client 18.189.88.75] (70007)The timeout specified has expired: Reading bucket failed (rcode=70007), referer: http://www.challengeblog.org/
[duplicate post, please ignore]
Do you use any page speed optimisers? Plugins or hosting options maybe?
Seems like this error comes from page speed apache module.