gwalter
Forum Replies Created
-
Forum: Plugins
In reply to: [Plugin: WordPress.com Stats] Dead since 2.7 upgradeI realize this thread is a bit old, and we’re now up to v.2.8.x, but I was able to follow @derice’s advice above – unfortunately, I still got error messages.
Frustrated. Fortunately I have Google and Woopra stats – but I would sure like to incorporatethe two years of data from my wp.com hosted blog.
@gwalter
http;//daddytude.comForum: Plugins
In reply to: Stats Plugin Rejecting PasswordI checked for the footer code – it was there, but slightly out of place. Moved it and tried again.
My problem is slightly different.
1. When I first added the stats plugin, I messed up and “added” a new blog instead of merging with my previous wp.com hosted blog.
2. At a friend’s suggestion, I deactivated and started over – but this just took me back to my previous stats – unmerged. So I uninstalled, deleted all the files, and started over. This ended up creating three instances of http:www.daddytude.com (hidden) on my wp.com blog management page.
3. I contacted support and had them remove those. They did. Now, I get this message:
Error from last API Key attempt:
The owner of that API Key (c**********s) is not on the access list for this blog (9928232). To be added to the access list, you must contact support.
What now Batman?
Forum: Plugins
In reply to: WordPress.com Stats stopped working (shows no traffic data) after 2.7 upgradeI checked for the footer code – it was there, but slightly out of place. Moved it and tried again.
My problem is slightly different.
1. When I first added the stats plugin, I messed up and “added” a new blog instead of merging with my previous wp.com hosted blog.
2. At a friend’s suggestion, I deactivated and started over – but this just took me back to my previous stats – unmerged. So I uninstalled, deleted all the files, and started over. This ended up creating three instances of http:www.daddytude.com (hidden) on my wp.com blog management page.
3. I contacted support and had them remove those. They did. Now, I get this message:
Error from last API Key attempt:
The owner of that API Key (c**********s) is not on the access list for this blog (9928232). To be added to the access list, you must contact support.
What now Batman?