November 28th, 2008
by
admin
WordPress 2.7 is not here yet (2.65 is out with some security enhancements, but we haven’t made it that last five hundredths of a version point to 2.7 yet.
Matt Mullenweg does give a nice lecture and a bit of a demonstration in what will be coming in WordPress 2.7. This is probably more of a way to wrap your mind around the ‘why’ of the upgrade than get some good visuals of the upgrade itself, but that should be helpful too!
So for all of you WordPress users that are hooked on an older version of WordPress, you might be in for another ride or at least a ride through WordPress 1.5 detox or something (they have detox for everything else from sex addictions, to drug and alcohol to Orovo detox, why not a WordPress 1.5 detox??????)
Personally, I’m looking forward to the future capability of editing a post inline. I don’t think its going to make it into 2.7, but when that day comes, I think WordPress will make an evolutionary step in terms of collaboration both for publishers but even office workers looking to document knowledge with others on their teams and in their groups.
November 9th, 2008
by
Brett Bumeter
For those of you that are anticipating the goodies and goods in WordPress update 2.7, we still have a couple weeks to go. As I write this, tomorrow is the 10th of November, the original date that 2.7 was supposed to be released.
That date was pushed back as the teams wanted and received more time to test things.
This is likely going to be a pretty serious update so the more time spent testing is definitely to be expected and to be happy about.
Truth be told, I probably won’t be able to get around to doing anything serious with 2.7 until after the Christmas holidays anyway. So developers and testers, take all the time you need. 
Its likely to be a lean christmas here as we head heavily into a recession. So from that perspective any ‘free’ thing is actually going to be much more anticipated and more useful than giving someone a toy or watch that probably is as good as a knock offs or replica watches shipped across on the same boat.
If you have the time this Christmas, Give the Gift of a WordPress Install or a WordPress Upgrade to someone you love!
Here’s some key articles as posted from Lorelle’s WordPress blog:
March 7th, 2008
by
Brett Bumeter
Here’s a really scary scenario. You wake up one morning and check your WordPress blog and something doesn’t look right. You login and can’t quite place it but something is missing.
You go to write an article, and after finishing the write up you try and select a category and that’s when you notice it. The categories are gone! They’ve disappeared like a Chinese accountant performing an audit. Where did they go?
Well, this is a known and unanswered WordPress error.
Now, when I saw this error myself on my blog, I first checked my WordPress version. I was working on 2.3.2 and 2.3.3 was available. My first move was to upgrade to 2.3.3, with a manual ftp upload (I didn’t want to trust Fantastico when I was troubleshooting.) That didn’t work unfortunately.
Then I came across this article about the database for WordPress being out of date, in addition to or as an alternative to the actual files.
Remember WordPress is a program -> Files that manage the content stored in your MySQL database, which also needs to be upgraded from time to time.
Just add /wp-admin/upgrade.php to the end of your domain to check and see if your database can be upgraded.
That same article however mentioned that the WordPress files in 2.3.2 were in (translated into layman terms) a ‘little screwy’.
I found a suggested fix that made sense. However, when I tried to get into MySQL and update the field below, I was unable to make any changes on the fields (MySQL error 17 ).
I run a dedicated server, and after wracking my brain, took the drastic step of restarting MySQL on my server. After I did that, my categories on my blog were back!
The fix below still made sense. MySQL may have stalled due to memory issues, so I still wanted to try and upgrade at least one site just to test it to see if it might help.
So I tried this fix
The Fix is a two part process. You have to fool your WordPress program into thinking that the Database is out of date, so that it can then run the upgrade program and update the database.
Sometimes apparently the database upgrade will run, not complete itself, but change the value in your database telling you that your database is up to date. It then will not upgrade when you hit the button, so you have to reset the field value in the DB so that it will run again.
The field can be found under the table name -> yourdbname_options and then go to field db_version. Mine was set at 6124 (latest for 2.3.2) and so I reset it to 5183.
To write over the field in the database (something I had never done before)
The upgrade did run this time, but for me I received a couple errors when tables could not be upgraded. I got the sense that in that previous article describing the fix, that person may truly have had the issue of a db upgrade that stalled out, but in my case that was not the problem.
Therefore, I’d recommend that if anyone runs into this problem, call your ISP to restart your mysql server first. Then if you still have a problem, you might consider changing values in MySQL, which is rarely something anyone recommends. Short of that try and avoid over stressing, drinking yourself silly and getting funneled through drug treatment centers. This problem may be easier to fix than it appears if you just ask for a little help.
Note. If your host is a real pain to work with, my apologies for the hold time you may have to endure.
