My website also went down today due to a slimstst error. Had to get the hosting company to deactivate plugin to bring site back up.
They quoted the following error line in the programming as being at fault.
UTC] PHP Fatal error: Call to undefined function download_url() in /home4/ahighpho/public_html/wp-content/plugins/wp-slimstat/wp-slimstat.php on line 1188
Strange it should happen sometime after installing the latest version. Hope this info helps you to correct this.
I wonder if I have lost all logs because of this ?
Regards
Thread Starter
yk11
(@yk11)
You should not lose anything due to the error. SlimStats’s logs are in the database, so they are not deleted due to a simple error.
If you replace the line with the code I included the error should go away.
Thank you, guys. We are looking into the issue. Sorry for the inconvenience:( And no, no existing data is lost because of this bug. You can also manually download that file, unzip it and upload it to wp-content/uploads/wp-slimstat where the existing one is.
Thread Starter
yk11
(@yk11)
May I suggest adding an admin option to specify an absolute path to the file? This would allow sharing a single file instance across multiple wordpress installs.
Just to add to the discussion.
My site went “down” the other day. No page would be displayed. After sometime diagnosing the problem, we eventually found Slimstat to be the cause.
I disable the plugin and all was well. I found this post and implemented yk11’s fix, re-enabled Slimstat and were back up. However I am receiving an alert bar regarding a location based service from Maxmind. I clicked the link to enable but received another alert saying it couldn’t unzip a file. I am guessing this has to do with permissions but I am not sure what level permissions need to be enabled and to which directory.
Other than that, thanks for the fix and love the plug-in.
We’re working on a fix, thank you for pointing this out.
Same problem here. Please hurry 😉
Thanks Arno
Slimstat 3.9.9 should fix this problem.
Thanks camu! For me this works now. Since in your comment you’ve mentioned it happened only to a few users: Only when I was not logged in to my site the error happened. Also I’m running iThemes security. Maybe this helps …
Thanks for the fix and cheers, Arno
Thanks Arno. We are still trying to replicate the issue. IThemes doesn’t trigger the problem in our case.
Everyone, can you please list what plugins you are using, even by sending us a private support request?
Thank you
Camu
