Downloading install package from http://downloads.wordpress.org/plugin/addthis.1.6.6.zip…

Warning: touch() [function.touch]: SAFE MODE Restriction in effect. The script whose uid is 587 is not allowed to access /tmp owned by uid 0 in /long-path/wp-admin/includes/file.php on line 199

Download failed. Could not create Temporary file.

What to Do?

After some searching I found a simple solution: Just create a new temporary folder in your web root (often called public_html) folder and point WordPress to this new folder.

How Do I Change the /tmp Folder Then?

That’s Easy!

Just add the following line to your wp-config.php

define('WP_TEMP_DIR','/your_path/public_html/tmp');

And make sure to use the name of the folder where WordPress is installed or the root html folder. And also make sure you have created the tmp folder and chmod it to 777 before adding the define to wp-config.php

This is all there is to do, enjoy!

The stress of upgrading

Finally after a couple of hours of work all four of my blogs have been upgraded to WordPress 3.0 and if feels good!

Here’s what you need to watch out for when upgrading:

Automatic Upgrade Glitches

The automatic upgrade feature of WordPress does not work if your web host is running PHP in safe mode, you’ll get this error:

Warning: touch() [function.touch]: SAFE MODE Restriction in effect. The script whose uid is 587 is not allowed to access /tmp owned by uid 0 in /home/sbyholm/domains/simonbyholm.com/public_html/wp-admin/includes/file.php  on line 184

Download failed.: Could not create Temporary file

Installation Failed

This issue is easily solved though. The problem is that WordPress can’t write to the /tmp folder because of the safe mode restrictions. The solution is to make a new /tmp folder inside you wp folder and make that writable.

• Create a new folder /tmp inside you current blog folder
• Chmod the folder to 777 using either your control panel or FTP
• Add a line to wp-config.php telling wordpress where the new /tmp is located

define('WP_TEMP_DIR','/full/path/to/tmp');

After doing this you can run the automatic upgrade inside the WordPress dashboard of your blog

Plugins Not Working

On one of my blogs I had several SEO and other plugins running and this brought some problems when upgrading.

After upgrading WordPress from 2.2.2 to 3.0 and upgrading all plugins using the automatic update after upgrading wordpress… some of the plugins was showing up as both the old version (which was running) and the new version which was disabled.

I had to manually click deactivate, delete on the old plugin versions and then activate the new versions.

Another thing with the plugins was that many of the wasn’t visible after the upgrade but required that I go into the admin panel and drag some widgets onto the blog to see them again.

Theme Troubles

I just had to forget about using the old default theme, it threw errors in the single post view. I switched to the new Twenty Ten which is really nice looking but where I’ll have to adjust the margins to some of the images in my posts. The margins in Twenty Ten is just too narrow.

Strangely the homemade themes I have hacked from the old default theme continue to work with WordPress 3.0 and still looks as ugly as ever

Why You Should Upgrade to WordPress 3.0

I like the look and feel of WordPress 3.0 and it’s probably a good idea to upgrade your blogs as soon as possible. Especially if you use the old default theme the new Twenty Ten is a lot more inviting and readable.

Just remember to backup your database and your site before the upgrade!

And if you didn’t notice this blog is now running WordPress 3.0, I think you have to look at the dashboard to see the difference the theme looks the same to me.