popstat

Again, all this came and went months ago, so it’s moot. But:

– At the time of the original post, I wasn’t sure whether or not it was a 1.2 issue. By the time I determined it wasn’t, I’d given up on getting any response here, since there was none forthcoming (aside from the upgrade advice).

– I wouldn’t call 50% a “common” solution. That means half the people who upgrade as a potential solution do so needlessly. And contrary to the lingo here, upgrading is not a simple process for many, due to customization a lot of us perform. My upgrade from 1.2 to 1.5 was, as I predicted, rocky. Which was why I avoided it at first.

– Since, again, the problem referenced here turned out to not be a version issue, I don’t see why support for obsolete versions of WP even enters this discussion.

This is all I’ve got to say on the subject here. If each .x upgrade signals the end of support expections for prior versions, fine; I’ll keep it in mind in the future.

Thanks…I guess I don’t want to rely on FeedGator, any more than I’d rely on any third-party component that produces reader-accessible content on my site. There’s always the fear that it’ll malfunction, etc. and unduly inconvenience subscribers (which is why I never used BlogRolling on my old Blogger blog, and similar).

But in the absence of another tool strictly for my own tracking, maybe I’ll look deeper into FeedBurner.

Several months later, this is moot, as I’ve since upgraded to 1.5.x… But I can tell you that running 1.2 was absolutely not the problem in this case. So, as I said, this was a non-response case.

Sorry, I don’t buy that. I see a lot of instance where people here use “just upgrade” as a stock response, used solely to add one’s two cents, when that’s not related to the problem at hand (i.e. layout things etc.). I realize you run the risk of being left behind by sticking with a prior version; on the other hand, I see no reason to continually upgrade just for the sake of it, when any problems that crop up aren’t related to version number (and in fact, when upgrading brings on more headaches than it solves).

For me, the point is moot, as I’m now running a fairly up-to-date version (1.5.1.3). But upgrading is definitely not the cure-all.

Not sure what you mean by an inability to link to them; in any case, that’s not my concern (I have the individual comment permalinks set as anchors that link to single-page posts, like this).

I guess I’m concerned about leaving myself exposed to the “Spam Comments Appear Immediately” attack. Having the popup ID clearly expressed on the index page seems to leave a vulnerability. Or am I off-base on that?

Thanks for the responses on those two most recent requests.

I’d count this one: https://www.ads-software.com/support/topic/37718 as a non-response, since I don’t consider “just upgrade” (or similar quickie-but-shallow advice) to be particularly helpful. I also had enough non-responses under a previous login name that pretty much built up to this.

But you see that it took this rant post to get any action here. Got to be an easier way.

Depending on how you want to set it up, the Paginate plugin might give you what you want:

https://www.scriptygoddess.com/archives/2004/05/23/wppaginate/

Example of it in action:

https://www.populationstatistic.com/archives/category/pop-culture/

Damn, I’d better slow down my daily blogging before I hit that threshold…

But seriously, that is a concern, especially with load time. Big reason I chose WP over MT is the dynamic page creation, eliminating the load/rebuilds found in MT blogs.

There are some of us who actually appreciated the ability to selectively tick that checkbox for pingbacking in 1.2… As far as I’m concerned, removing it was a mistake for 1.5.xxx. I’m disappointed that it appears pingbacks is falling by the wayside in WP for no other reason than disinterest by the developers.

Yeah, the pingback output was pretty ugly; but I found that to be a plus, because they were very easy to visually identify when scanning through comments. Plus, I rigged them to include the pinging post’s title (here’s an example).

Now, to avoid the hassle of changing the Options on a per-post basis, I just resort to trackbacks for intra-blog linking (which I do a lot, and can’t imagine not taking advantage of). It does the job, but it involves an extra step I wish wasn’t ncessary.

Not sure if this is exactly what you’re looking for, but Scriptygoddess’ Paginate plugin provides for page numbers:

https://www.scriptygoddess.com/archives/2004/05/23/wppaginate/

You can see it in action on my site, for instance:

https://www.populationstatistic.com/archives/category/pop-culture/

Must be something that afflicts certain databases, or something. I’ve had that problem starting with 1.2, and it doesn’t seem to have been solved with 1.5. In fact, I’ve had to resort to using HaloScan (which I used when I had a BlogSpot blog) to send manual trackbacks in such cases.

Is that really the case? I’ve tried that in the past, and it absolutely did not work. Neither did pingbacking this way.

Someone else might be able to give a fuller answer, but basically: WordPress isn’t dependent upon your personal computer’s OS. Since it runs on your server, it doesn’t matter if you use Windows, Linux, Mac OS or whatever.

From personal experience: I update my blog from home (Windows) and work (OSX). No difference at all; the only minor wrinkles involve different browsers and versions of browsers, but nothing that impedes you from doing what you want.

Hmm, my bad… the zip file I downloaded through Mozilla kept coming up as a corrupted file, but downloading it through IE pulled it in clean. Go figure.

I don’t have WinRAR, don’t want it. Maybe someone can actually fix the zip file instead??