Posted 3 years ago #
Crash of admin board with the message :
Fatal error: Call to undefined function stats_get_option() in /home/www/e3293f6b6fd56ffe639916ddb6170e39/web/blog/wp-content/plugins/official-statcounter-plugin-for-wordpress/StatCounter-Wordpress-Plugin.php on line 37
Had to trash the statcounter plugin folder
http://wordpress.org/extend/plugins/official-statcounter-plugin-for-wordpress/
Posted 3 years ago #
Same error for me, I had to remove it via my FTP program.
Posted 3 years ago #
please help me! I think I am having the same problem too. after I click 'update automatically' at the statcounter plugin update notification, I realized my wp-admin goes blank! please tell me what to do?
do I have to go to my CPanel and delete the plugin folder from there? will it work? I'm a beginner, please do help!
thanks.
Posted 3 years ago #
I tried uninstalling it, it doesnt worked
I had to recover the site from database backup...if there is no help for this available I just hope you guys got backups ready...
Posted 3 years ago #
You can recover the wp-admin dashboard by deleting the statcounter plugin folder (with your FTP application). There will be no damage.
There is an error line 37 in the php file, has to be fixed.
Posted 3 years ago #
THANK YOU to those who suggested removing Official Statcounter via the FTP plugin-that worked for me. What a horrible experience--sorry I'll never re-install this ever ever ever.
Posted 3 years ago #
It's quite an easy fix actually. Open up the StatCounter-Wordpress-Plugin.php in an text editor and navigate to line 37 which should look like the following:
if ( stats_get_option('blog_id') ) {
Change that to say:
if ( get_option('blog_id') ) {
Save it, and re-upload and activate it, and walla - all working :)
Posted 3 years ago #
thanks a lot for your php mastering ;-)
Posted 3 years ago #
Thanks for the fix. I would have never figured it out in a million years.
Posted 3 years ago #
In fact, I think it is not necessary to install this plugin. I would rather use the official statcounter.com site to track the stat. You can track all your sites over there.
Posted 3 years ago #
In order for Statcounter to be able to know when your website(s) and its pages have been accessed, it needs to knw the id of your statcounter account, which can be done two ways: sticking the "install code" the statcounter.com website gives you into the HTML of your website (technically PHP for wordpress blogs), or by using this plugin.
I would opt for the plugin, just making sure that line 37 is edited to the fix mention above :)
Posted 3 years ago #
I tried deleting StatCounter-Wordpress-Plugin.php from wp-content/plugins/ as well as downloaded the update and changed line 37 as mentioned above, and I still get the error... Please help!
Posted 3 years ago #
I'd like to rescind my previous comment. I had updated then uploaded the statcounter plugin to the wrong area. The fix works as stated! Thank you, Swalchy! Shame on statcounter.
Posted 3 years ago #
I got the plugin from StatCounter and installed it. It was working fine. Then wp told me I should update the plugin. And now I can't get into my admin area. So, where do I go to fix or delete the update and get rid of the message when I try to get in. One of my other blogs was also affected. And I didn't even try to update that one. How do I fix it if I can't get into my admin area? I'm a newbie, so I need step by step, if you could.
Posted 3 years ago #
Swalchy's suggestion above to edit line 37 in the php file worked. Made the edit in the zip file and then uploaded and installed. Back in bizness!
"It's quite an easy fix actually. Open up the StatCounter-Wordpress-Plugin.php in an text editor and navigate to line 37 which should look like the following:
if ( stats_get_option('blog_id') ) {
Change that to say:
if ( get_option('blog_id') ) {
Save it, and re-upload and activate it, and walla - all working :)"
Thanks for the tip! I suppose you could just edit the file in the FTP uploader and not bother with the delete and reupload.
Posted 3 years ago #
Hi Guys,
Apologies for any inconvenience caused with this latest update.
This bug only occurs under certain conditions and it went unnoticed before we released it.
The advice on how to fix it is spot on and we've already applied and sent the fix to wordpress. It should be available to download from wordpress shortly.
This topic has been closed to new replies.
