It would be a major pain to renumber IDs for whatever reason, and there would not be a lot of benefit in it anyway. So why bother?
The benefit would be the organization. Check that link. It does seem like there are a few out there that are interested in this.
Thanks for writing Otto
I realize that some people want it, what I’m trying to grasp is why. I don’t see how it would help with organization, since the ID number is only really used internally. It’s just a fixed number. Doesn’t matter what it is. They could be assigned wholly at random, and other than looking a bit odd on some screens, it wouldn’t make any difference.
My permalinks are as follows: domain.com/POSTID#
As I am sure others are. That’s why. Thanks for listening.
I for one, am interested. Sometimes imported posts aren’t loaded chronologically.
When I first imported posts from Blogger into WP back in the day (v1.2), a couple botched tries (along with Blogger’s lack of data like GMT post times) screwed up the numbering. My posts start somewhere around 1100, and if you follow the timestamps chronologically, the ids jump all over the place, sometimes increasing like they should, sometimes decreasing.
The reason for a fix is since most of WP (and author plugins) usually sort by postID, the chronology becomes screwy.
I eventually changed all of my permalinks to use the page slug to hide post ids, but it still doesn’t address the problem.
I’ve written a Ruby script that takes a WordPress eXtended RSS file and rewrites all of the post ids, comment ids, and parent ids. No need then to change the database, as the importer should (I assume) create the proper database entires using the post ids.
I’ll put it up once I work out some bugs.
