• This is a bit of a wierd/complex one, so please bear with me.

    I have been using WordPress as a plugin into my own CMS for quite some time, I don’t use WordPress directly, but rather filter it through my CMS as some sort of plugin.

    I have had a lot of headaches with using WordPress this way in the past, mainly because how badly (sorry to say so), many of the internal functions in WordPress are written, they often print directly to the screen, some functions have an option to return values which is good, but many of the internal functions don’t and only print directly to the screen. This is a real nuisance, because you then have to either hack the WordPress code to bits, or extract these functions into a seperate .PHP file and fix them yourself to return a value. I did the last option, because it would make it at least a bit easier when upgrading.

    I have been using WordPress this way since version 1.5 as far as I remember, and every time a new release comes out, I have to manually go over all my functions again, and compare them with the new code, a real nightmare to go through an upgrade this way, but I have successfully done it a few times, right upto version 2.0.11

    I cannot upgrade beyond this version, as the WordPress code seems to have changed too dramatically, I tried a few times, but just got stuck with more headaches.

    Ok so, back to where I was, so I am successfully running a few old sites on Ubuntu Edgy using WordPress 2.0.11 running through my CMS. I will eventually replace them with Django sites, but I am not ready for this yet, so the WordPress versions must remain running for now.

    Lately, I have been getting ready setting up a new test server running Ubuntu Hardy, I know Hardy is not officially out yet, but I am preparing early.

    Hardy is running MySQL 5.0.51 I believe. I did a MySQL dump and restore of the old database, copied my site over, got everything running fine, except posts are showing back to front. i.e. 2005 shows first, then 2006, then 2007, etc…

    I checked the contents of the database table, and everything is intact there.

    I also manually inserted some checking code in wp-includes/classes.php to dump the query variable on the screen so I can see, and order is set to ASC there.

    I am clueless, I don’t know if the error is MySQL in Hardy, or if I need to switch to WordPress 2.3 (which is going to be a real mission). Any workarounds would be helpful too, I don’t mind hacking WordPress a bit as a workaround, I am not ready to put my new Django site up yet, and need to find a solution to this bug, and keep the WordPress based version going for a little longer.

    I believe it’s a bug in MySQL, but I could be wrong.

Viewing 3 replies - 1 through 3 (of 3 total)
  • This thread is stickied on the front page — is it related to your problem?

    Thread Starter robvdl

    (@robvdl)

    Yes that seems to be it, thanks for letting me know about this issue… I now know it’s MySQL (as I suspected), and will try to see if a new version of MySQL can still be pushed before Hardy’s release date.

    I am going to be reading up on this thread now, thanks.

    Thread Starter robvdl

    (@robvdl)

    When you say a version higher than 5.0.51 do you mean 5.0.51a? because that is the latest version available on the mysql website.

    If 5.0.51a fixes this, I really do hope UBuntu Hardy upgrade to this version before it gets released.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Posts show backwards’ is closed to new replies.