Posted 3 months ago #
After using the auto-update from within my wordpress admin - http://www.airandaqua.com/blogs Now when I click on "stats" in admin I get either Error 500 or else a note that says "You do not have sufficient permissions to access this page." !?
Anyone know how I could possibly fix this? Thanks!
Posted 3 months ago #
I'm having a similar problem. I didn't use auto-update, though, and I haven't got the 500 error.
Also, when I check my stats at WordPress.com, they report no hits since the upgrade. (The server logs report just as many as usual.)
Posted 3 months ago #
*bump*
Some kind of bug?
Posted 3 months ago #
As a side note, I tried to delete the plugin from plugins page and was just going to reinstall but it will not delete.
I deactivated and then reactivated, re-entered my API key and am still having the same problem!
Posted 3 months ago #
2.8.4 doesn't work.. no stats at all.
google analytics working just fine and showing traffic
tags# wordpress.com stats
Posted 3 months ago #
bump
Doesn't work for me either, on a new 2.8.4 blog. Visits but no stats.
Posted 3 months ago #
*bump* come on people!?
Posted 3 months ago #
as a side note, sociable plugin is not working with this version either... Had a feeling I should have waited to upgrade lol
Well, a day after installation it's begun to work for me in 2.8.4 (WordPress Stats).
Posted 3 months ago #
Weird... is there any where I can go to have someone from Wordpress take a look at my site and get some help on this? Or maybe a pro who would be willing to help?
Posted 3 months ago #
I upgraded to 2.8.4 a week or so ago, and the stats worked fine. But yesterday, they went from an average 8500 down to 11 with no referrals recorded. Today they are at a whopping 2.
My server tells me that my hits are still at 8455 for yesterday and are currently at 2274 this morning, so it isn't a case of lost traffic.
The stats seem to be working fine on my other blogs with the same configurations and plugins. None of that has changed.
2.8.4 does not work. When I tried to activate the plugin I have got an error message "wp_includes/pluginer.php Headers cannot be modified" etc.
This plugin needs to be updated.
Posted 3 months ago #
I am not sure it is WP 2.8.4 that is causing this. I have some other blogs running the same configuration and stats are working fine on them.
Posted 2 months ago #
Okay, I solved the problem.
Make sure you have <?php wp_footer(); ?> just before your </body> tag. Somehow mine got stripped out (probably when I added something the other day)
But I am back up and running again.
Posted 2 months ago #
Good advice, DJAllyn, but I've got <?php wp_footer(); ?> in there just before the </body> tag.
Incidentally, I've since installed a 2.8.3 version, just to see, and stats are still not working. So you're onto something with it not being WP 2.8.4.
Posted 2 months ago #
Me, too: same error as DJAllyn above. Had tens of thousands, down to a handful today.
DJAllyn, where do I find this <?php wp_footer(); ?> code?
Posted 2 months ago #
Ah, I see where <?php wp_footer(); ?> was. It’s in the footer.php file for our template, and you are right, this was missing after an edit that happened to take place, coincidentally, just before our 2.8.4 upgrade. Will see how it goes.
Posted 2 months ago #
My upgrade make Manage Surveys unreachable with the "You do not have sufficient permissions to access this page." error.
Tried the <?php wp_footer(); ?> fix but did nothing to improve the situation.
Insolently, the upgrade it self does not appear to be the problem. I just put up a log with 2.8.4 right off the bat and it will not allow me to access Manage Surveys either.
Posted 2 months ago #
<?php wp_footer(); ?>
worked for me - thx.
Posted 2 weeks ago #
yes <?php wp_footer(); ?> was also my problem, somehow during a website design update I erased it... :) thank you all, greetings from Lisbon.
Posted 2 weeks ago #
WP 285, stats 154: after entering the API key I get
Error from last API Key attempt:
transport error - HTTP status code was not 200
Before the update to 285 everything worked just fine...
You must log in to post.
