annehill

Perfect, thanks!

Thanks for that, Angelo! I understand the drawbacks of the podPress stats, I just wouldn’t want them to go away during an upgrade.

The demo video Shawn linked to shows the functionality of the PowerPress professional stats, but I have yet to find a quick run-down of what the basic stats include.

I’ve seen that link, but there is no way to see what stats you get until you sign up for a free account. I’d rather know ahead of time.

Thanks. As a follow-up, here is what I currently see for each podcast episode using PodPress stats:

Feed (raw numbers, % of total), Download (raw numbers, % of total), Play (raw numbers, % of total), and Total.

How does this compare with the PowerPress basic stats services?

Fantastic–it works! Thanks so much.

Sure, thanks for that. Here’s the link:

https://pastebin.com/gZrxGYQR

Update: I thought maybe one of the plugins had an update that would correct this problem, so this morning I ran the automatic updater. No change. I then deactivated all plugins except Akismet—still no change. I changed themes, but the back-end continued to be this strange, stripped-down, unusable display. I did the automatic re-install of WordPress from the updates page—and the problem persists.

My friend is using TheCotton theme. The only thing I can think of after this is doing a re-install of wordpress via FTP. Any thoughts?

After reading all comments on the linked thread, I decided that maybe the issue was not resolved by upgrading to 2.3.2, but by the infected posts being more than 10 posts previous–in other words, they weren’t being brought up when loading the main blog page. Sure enough, doing a search through monthly archives brought up one post from October and one from November which had the “traffic stats” code injected in them. Deleted the code, and all will hopefully be well.

I upgraded to 2.3.2 and immediately the problem went away. I agree with you, it seems to be the code injection problem that you linked to. So I will mark this thread resolved, and refer people to the larger discussion.

Oh yeah, I just tried re-installing wp 2.3.1 in case one of the main files was altered in some way. There was no change to the problem.

Huh, maybe it depends on what subject matter you blog about. My blog is not a tech-oriented one, and I get linked to by a lot of academic bloggers, essayists, etc. Google hasn’t picked up any of them. As soon as I installed the plugin today, Technorati showed me about 30 new incoming links, none of them spam. Oh well.

Ah yes, a comma cleared that sentence right up. Thanks, I may switch back to Technorati using the plugin. But Google must not know about lots of blogs for them to not pick up any links since September!

I assume there was a reason that wp 2.3 switched to google blog search–possibly owing to dissatisfaction with Technorati ranking etc. I just wonder when google will be up to par with what Technorati routinely picked up.

Sorry, but I can’t understand what you just wrote. Do you mind rephrasing?

Well, if the codex had all I’d ever want to know about permalinks, I don’t think I’d be posting anything here. I have posted pretty specific information here, have asked my isp support folks to check into whether they have things blocked on their Apache server, but so far no one has responded with anything definitive.

In the interest of getting the best response possible to my situation, I have my blog hosted on my ISP which had me place the .htaccess file in the main website directory rather than the blog subdirectory, for security reasons. (I don’t know the explanation, but it involved a cgi file as well, I just followed their suggestions.) Anyway, all was running fine in the last version of wp.

After upgrading to 2.0 (following all the back up instructions, etc.) I decided to change the permalink option from the default structure to the one that organizes them by year, month, and day.

Now when I try to access a month’s worth of archives, I get the following:

>The requested URL /gcblog/2005/10/ was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.<

No one can post comments either, or they’ll get a similar message:

>The requested URL /gcblog/2006/01/07/bloggers-lament/ was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.<

I have also found that wp creates an .htaccess file in the main blog directory after I do something like try to change the permalink structure back to where it used to be, or to go into the comments while logged in. Then the site is totally down, and I get a message like the following:

>Warning: main(/nfs/www/WWW_pages/annehill/gnosiscafe.com/gcblog/wp-config.php): failed to open stream: Permission denied in /nfs/www/WWW_pages/annehill/gnosiscafe.com/gcblog/wp-blog-header.php on line 12<

Can someone please tell me something to try that might get things working again?

Thanks very much.