So, I started searching on the Internet how to solve my problem. And finally I found that there are some bugs in WordPress 2.9. They are:

Bug tersebut adalah:

• Major bug was simply dismissed
• A related critical bug was only partially fixed)
• A last critical bug (and its child bug) crept in at the last moment

As a result of this:

• RSS widgets are completely broken on servers that are missing both of iconv and multi-byte string functions;
• The curl transport is broken on some servers with an outdated library. This breaks the WP cron, and with it future posting, pings, etc.

Not all sites are affected, of course. Most aren’t, in fact. But for those few who are, the situation is frustrating.

To solve this problem, you need to follow this steps:

1. Download this patch (from semiologic.com):

WordPress 2.9 Patch

2. Extract all files (class-simplepie.php, default-widgets.php, http.php) to wp-includes directory. Replace the old files with the patch files.

3. Done…

Good luck… :)

Related posts:

1. WordPress Error After Automatic Upgrading
2. WordPress Error: open_basedir restriction in effect
3. WordPress 2.8 Review

Warning: is_dir() [function.is-dir]: open_basedir restriction in effect.
File(/) is not within the allowed path(s):
(/home/MY_ACCOUNT:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:
/usr/local/php4/lib/php:/tmp) in /home/MY_ACCOUNT/wp-includes/functions.php
on line 1942

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect.
File(/) is not within the allowed path(s):
(/home/MY_ACCOUNT:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:
/usr/local/php4/lib/php:/tmp) in /home/MY_ACCOUNT/wp-includes/functions.php
on line 1933

Warning: is_dir() [function.is-dir]: open_basedir restriction in effect.
File(/) is not within the allowed path(s):
(/home/MY_ACCOUNT:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:
/usr/local/php4/lib/php:/tmp) in /home/MY_ACCOUNT/wp-includes/functions.php
on line 1942

FYI, I created my blog using wordpress. It’s the best blog engine ever.. :) After asking some questions to uncle Google, I found that some people have asked the same questions. But they don’t get the solution yet. I started thinking, then I decided to check the database. I looked into tables wp_options (For example I use the default prefix “wp_”, table prefix depends on wordpress configuration). I scanned one-by-one, and I found something suspicious in column option_name = ‘upload_path’. The value of column option_value = ‘/home/MY_ACCOUNT/wp-content/uploads’. After comparing with column option_value from the “healthy” blog, I changed the value to ‘wp-content/uploads’.

Back to my favorite browser…, then I pressed F5. Tadaaaa… error in my photography blog disappeared… :)

Related posts:

1. WordPress Error After Automatic Upgrading
2. Fixing WordPress 2.9 Upgrade Error

Briefly unavailable for scheduled maintenance. Check back in a minute.

Got that message? And you can’t view your blog neither login to admin area? And now you wish you didn’t click automatic upgrade link? No need to worry, we will fix it.

Before we fix it, we shoud know what is going on? WordPress, like other systems, is not perfect. Eventough it has automatic upgrade, it doesn’t mean your wordpress installation will always successfully upgraded using automatic upgrade. That’s why we should back up our blog before upgrading it. So, why that message appear? Does it mean our installation failed? Maybe. WordPress creates a file named .maintenance before upgrading process. Just in case there are visitors accessing your blog during upgrading process, they will see “Briefly unavailable for scheduled maintenance. Check back in a minute.” message instead of your under-upgrading blog. Somehow, I don’t know exactly why, the file .maintenance is not deleted by WordPress. If this thing happens, you will see maintenance message.

So, how to fix it? It’s a piece of cake. Login to your web host using CPanel or SSH, remove the .maintenance file. You can find that file in your WordPress installation directory (the directory that has wp-admin directory – not inside wp-admin directory). After you do it, refresh your blog. We hope your blog will be back… :)

Question: I can’t see .maintenance file
Answer: Yes, it’s a hidden file. If you are using SSH try ls -a command. If you use CPanel, don’t forget to check show hidden files while opening your installation directory using file manager.

Related posts:

1. Fixing WordPress 2.9 Upgrade Error
2. WordPress Error: open_basedir restriction in effect
3. WordPress.org Releases 2.8 Beta 1