Hi Camu,
I think I didn't get my last message in the right category...
I have moved my site to a new server, and now when Slimstat is activated the site takes many minutes to load! I can barely access the admin area, so it is not feasible to make changes to the configuration through the control panel.
When I check my Apache error log I see this:
[Fri Apr 22 10:41:11 2011] [error] [client 209.116.60.130] PHP Warning: fsockopen() [function.fsockopen]: unable to connect to updates.browserproject.com:80 (Connection timed out) in /home/icp/public_html/wp-content/plugins/wp-slimstat/browscap.php on line 589
[Fri Apr 22 10:41:11 2011] [error] [client 209.116.60.130] PHP Warning: file_put_contents(/home/icp/public_html/wp-content/plugins/wp-slimstat/cache/cache.php) [function.file-put-contents]: failed to open stream: Permission denied in /home/icp/public_html/wp-content/plugins/wp-slimstat/browscap.php on line 366
[Fri Apr 22 10:41:11 2011] [error] [client 209.116.60.130] PHP Warning: browscap::require(/home/icp/public_html/wp-content/plugins/wp-slimstat/cache/cache.php) [function.browscap-require]: failed to open stream: No such file or directory in /home/icp/public_html/wp-content/plugins/wp-slimstat/browscap.php on line 376
I have made my /plugins/wp-slimstat/cache/ dir publicly writeable. It seems that my server is hanging on fsockopen. Could it be a firewall problem? Help! My client REALLY misses slimstat!
Saill
http://wordpress.org/extend/plugins/wp-slimstat/
I wonder if it could be SELinux? The new server is CentOS, and looks like SELinux is enabled.
Let me see if I can turn it off...
Fixed it by commenting out a couple elseif's in browsecap.php to force it to use curl!
[Code moderated as per the Forum Rules. Please use the pastebin]
Woohoo! So happy to have slimstat back!
Saill
The easy fix is to disable the AUTOUPDATE option in the corresponding panel in WP SlimStat. My plugin is trying to contact the server to download a newer version of the browsers' definition file, but the server is down or your server doesn't allow fsockopen.
No need to edit browscap.php, as this issue will reappear as soon you upgrade WP SlimStat to the new version.
BTW, make sure you have a file called cache.php inside the cache folder of my plugin, that's very important!
Camu
Ah - good point about upgrading. As long as I was seeing the error I couldn't access the control panel because the site wasn't loading.
Now AUTOUPDATE is disabled, and cache.php is where it should be, so all is well!
Saill
Good point, maybe I should set the autoupdate to 'false' by default, so that it does not cause problems. Then users who want it, will be able to change it to true. Thank you for your feedback!
Camu
:)
Thank YOU for slimstat!
Saill
I hope you will be positively impressed with the new version coming out (hopefully) this week :)
Camu
Oooo, how exciting! Looking forward to it!
Saill
Your feedback will be really appreciated :)
As always, I will do my best to break it. :)
Saill
LOL, then maybe I should send you a preview version before I release it to the public ;)
So, do you like the new version?
:)
I LOVE the new version. Especially "Spy View".
Had a tiny problem with the install - for some reason the cache dir became unwritable which caused the site to hang. Alarming at first, but easy to fix once I checked the Apache error log.
Maybe my new CentOS server has some weird permissions rules or something.
Saill
That's something beyond my control :) Anyway, I'm glad you like it!
Camu
My client likes it a lot too. She was very distressed when SlimStat was disabled for a couple days.
LOL! Well, now she will be able to track commenters and have much more information about each single visit. And more is coming!
Camu
PS: voting for my plugin is a nice way to thank me :)
