Tag: upgrade

WordPress 3.0 and flush_rewrite_rules

I thought I would document this experience I had when upgrading some sites to WordPress 3.0.

After WordPress 3.0 came out I took some time to upgrade blogs I manage and was impressed how well the upgrades fared. No issues, fair warnings and ultimately upgraded sites. However, on one of my development sites, after the upgrade, I noted an error about “error re-declaring the function flush_rewrite_rules()”. I knew, for this site in particular, that I had written some custom code to rewrite the urls and in this case I had innocently included a function called “flush_rewrite_rules()”. Coincidentally, in WordPress 3.0 a new core function has been created called “flush_rewrite_rules()” and because that now exists my function is interfering with this and required fixing. The fix, in this case was to rename my custom function and test and I thought nothing more of it. (I know – I should have participated in the beta test).

I didn’t think anything of it after that until I was asked to assist with another clients site. This time the client had innocently upgraded their site to WordPress 3.0 and encountered a white screen with the long PHP error referencing “error re-declaring the function  flush_rewrite_rules()”. The difference this time was that it was in a plugin causing the issue and as such the site was rendered inaccessible.

For this client I connected via FTP and downloaded the plugin code, searched for the function named  “flush_rewrite_rules()” (along with any references to it) and renamed it through the code. After uploading the change the site was restored back to normal.

A simple fix for this site but also a simple lesson in heeding the warnings / suggestions given by the WordPress upgrade tool when upgrading to WordPress 3.0

WordPress 2.9.1 update

This point release is now available for download from wordpress.org. This point release was the result of lots of feedback from the WordPress community relating to the curl / PHP / webhost issues as well as problems with post scheduling (a feature I’m sure many use) and pingbacks (used to share your posts).

I used Tools, Upgrade to quickly, easily and painlessly upgrade my site.

I’m confident we have a stable version of WordPress and am looking forward to the end of the first quarter 2010 for WordPress 3.0 🙂

WordPress 2.9.1

No sooner than WordPress 2.9 was released, an updated point release was announced to resolve issues on some versions of PHP’s curl extension. Bizarre. I mean who would’ve thought after all the beta testing and release candidates that this kind of issue would only show up once released to the public. Hence WordPress 2.9.1 was born just days after the WordPress 2.9 release. Continue reading

WordPress 2.9 Upgrade

The latest version of WordPress, 2.9, has just been released.

Upgrading was really quite easy. I logged into my WordPress dashboard and saw the message saying that WordPress 2.9 is available, click here to upgrade. So, I did. The upgrade screen reminded me to backup my database, a sensible suggestion, so I quickly clicked through to my favourite backup tool and made backup. I returned to Tools, upgrade and clicked on “Upgrade Automatically”. Within seconds the upgrade process had downloaded the update, uncompressed and installed it. Continue reading

Keeping WordPress secure

Over the past few months we’ve seen multitude of point releases of WordPress. We’re all in favour of new features and performance improvements but sometimes we overlook the important security aspects these updates bring. Recently WordPress was the subject of an attack by a worm that had a negative impact on the performance and security of the software. (More details here). Continue reading

WordPress FTP Connection Information

Have you been working with the latest version of WordPress – 2.8 through 2.8.2 – and found you can’t update a plugin or in some cases update WordPress using the “Update Automatically” functionality? This easy or auto upgrade functionality is a great addition to WordPress and it was a little disappointing to encounter this issue. Continue reading