Posted 4 years ago #
Help,
Out of the blue my blog, http://www.coletti.co.uk , has started a weird ordering of posts. The oldest seems to be coming up first. I've checked the date and time stamp of every post in the manage -> posts section of the admin and all date/time stamps are fine.
Also I can see no option that I might have ticked that says 'reverse the order'.
I reverted back to the WP classic theme and it didn't help at all.
I'm using WP 2.0.7.
Can anyone help?
Paul
Posted 4 years ago #
OK, it's actually ordering my posts by 'Post ID' which is also known as the Post Slug in the WP admin interface, i.e. the post with ID 7 is first, then ID 8 is next and so on up into the hundreds.
I've no idea why it has started doing this because it used to display in time stamp order with the most recent first...this is the normal default WP behaviour.
I could manually go through every post on my site and set the ID to match the timestamp but that woould take fuh-eva.
Again, I've checked my timestamps . . they're cool as.
Is there anyone from WP actually watching these forums?
Just a pointer in the right direction would be appreciated.
Posted 4 years ago #
Ok, more info, it is actually ordering by the WP post ID and _NOT_ the slug as I just mentioned. I incorrectly thought they were one and the same.
I just created this post:
I gave it a slug of 5 which is a lower number than the currently incorrectly top posted article on my site with a slug of 7.
As you can see it has a post ID of 188 which is the highest post ID on my site and therefore the last post to be displayed. It should be the first post to be displayed . . . it would have been the first post to be displayed had I written it about two weeks ago. Have I passed some threshold that has triggered this?
You'll notice also that an entry for this post does appear in the 'recently written' section on the left hand column of my site. So is this a theme problem...? I've tried two other themes and the same issue is there . .
Posted 4 years ago #
I've got the same problem (WP 1.5.3) .... haven't found any solution
Posted 4 years ago #
Ok, this happened to me as well. As far as I can tell all we did was upgrade MySQL to version 5.
Does anyone have any idea how to fix this?
Posted 4 years ago #
My problem isn't related to an MySQL-upgrade ... still looking for the solution
Posted 4 years ago #
Alex,
I don't really think ours is either, especially when I have other WordPress installs working just fine.
Cheers,
Posted 4 years ago #
Well, it doesn't look like anyone from WP is gonna admit to this so for what it's worth I upgraded the whole shebang to WP 2.3.2 (it took me fuh-eva because I couldn’t get FTP past the firewall so had to manually upload the files using a web-based explorer tool . . eugh!) and the problem described above is now gone . . . now if only I could fix that right-sidebar display problem I have ;)
Posted 4 years ago #
I have the same problem. The order of my posts was suddenly reversed a couple of weeks ago.
Can anyone explain to a none too up-with-this person like myself how I upgrade to WP 2.3.2 as described in the last post? A friend of mine set up my blog for me so I've just been adding my fascinating posts to something that i did not create myself.
It feels like I'm supposed to be upgrading a website - which is a confusing thought...
Posted 4 years ago #
I forgot to say - is there any way round this without having to upgrade anything?
Posted 4 years ago #
Meesh, you should not have to upgrade your blog to 2.3.2 to get around this problem. If several people the world over suddenyl had this problem on (what appears to be) the exact same date then there is a possible problem with WP. Sadly, despite repeated attempts I've been unable to get anyone from WP to look at this post let alone fix it. If you want to undergo the upgrade process then the details are all here on the 2.3.2 download page. You need to be comfortable adding, deleting, creating subdirectoires using an FTP tool like SMARTftp and you also need to know how to access the admin tool for your MySQL database.
If you can do that then it's relatively painless.
Posted 4 years ago #
I'd like to add that upgrading to 2.3.2 seemed to fix the problem for me. Regardless why, it fixed it. WordPress' upgrade procedure is very easy and straight-forward (took no more than 5 minutes) so it was no sweat off my back.
Cheers guys,
This is not a new problem. People have been reporting it all over the place for months. A MySQL upgrade does seem to be a fairly common factor among the reported cases.
Regardless, upgrading to the latest WordPress has always appeared to fix it. Something with older versions of WP and newer versions of MySQL causes some kind of weirdness there.
It may be because some older versions of WordPress (around 1.5, maybe) did not explicitly specify the post-ordering, and so an upgrade of MySQL (and a reload of the tables) changed the row order in the database. Newer versions of WordPress always specify order of posts when they make their select statements.
Alternatively, running a repair on your database might rebuild the indexes and correct the problem. But really, if you're running an older WordPress, then your blog is vulnerable to intrusion. Older versions almost all have known security flaws. Upgrading is highly recommended.
Posted 4 years ago #
I am having the same problem, but I tried the upgrade and it did not work.
Posted 4 years ago #
Does this problem show up if you upgrade to 2.0.10?
Posted 4 years ago #
I started having the same problem 3 days ago-- just after my hosting service upgraded MySQL. I have upgraded to WordPress 2.3.2 to no avail.
I did have a little bit of success, by changing my reading options from the dashboard [dashboard-options-reading], to "show at most: x DAYS" vs. "x POSTS". Doing this at least shows the most recent posts, but they are still ordered oldest to newest.
still shopping for an answer, but these occasional glitches are a nice way to make us dive into wordpress and understand it a little better, aren't they? so easy to just take the software for granted
To follow up on this, there was a report that this problem is caused when hosts upgrade to MySQL version 5.0.51. The problem, a MySQL bug, is fixed in MySQL 5.0.52.
For more info see Peter Westwood's post on wp-hackers:
http://comox.textdrive.com/pipermail/wp-hackers/2008-January/017200.html
This topic has been closed to new replies.
