hwa2u.com

WordPress MU 1.2 just released not long ago, according to Donncha, most of the changes are bug fixes, but there are some security fix as well, so it’s advised that all the WordPress MU user upgrade to the latest version! And if you encounter any problems, please go to WordPress MU forum.

Apparently there are some problems with the theme in WordPress MU 1.2, but worry not! Because version 1.2.1 is here!! 😆 So if you upgrade from 1.2, all you have to do is just change the following files:

• wp-admin/themes.php
• htaccess.dist
• wp-includes/version.php
• wp-admin/admin-db.php
• wp-admin/themes.php
• wp-admin/wpmu-themes.php

Oh and don’t forget to go "Site Admin > Themes" and click save to update the theme list! 😉

It had been quite some time i didn’t write anything since the last WordPress update, which is WordPress 2.1.2, but today when i was trying to delete the spam comment, i found a bug that already been in WordPress for like don’t know since which version already.

Basically the bug will just interrupt you and say “You don’t have permission to do that.” when you are trying to delete a comment or adding/removing a category, then of course you can’t delete the comment and do anything with category.

However i can still delete the comment in mass edit mode without any problem, i’m guessing that this must have some issues with AJAX or something, because when in mass edit mode it doesn’t deal with AJAX and everything is working fine.

There already been quite many report regarding this matter, and i hope that the WordPress team will solve this problem as soon as possible.

Upon i upgraded my WordPress to version 2.1, i encountered a few time where my WordPress theme reset to default, the one by binarybonsai.

At first i thought it’s a bug in WordPress 2.1 so i went to the support forum and try to find post with similar problem, if this really a bug then it should be a lot of people talking and complaining about it but strangely not, So i dug even deeper and found this, a post by Scott Burkett explaining what cause the problem.

Apparently most of them who face this trouble has this plugin installed, WP-Mobile by Alex King, don’t get me wrong it’s not the plugin fault, the plugin works great and do what it suppose to do, but it’s the user who didn’t read the instructions well, that’s me. 😳

While most WordPress plugins will require only the user to upload all the related files into the wp-content/plugins folder, but WP-Mobile require you to upload some other file to the wp-content/themes folder.

Anyway here’s what Scott Burkett explain about the problem:

It turns out that I had not properly followed the instructions provided by Alex in the plugin archive. Instead of following the instructions, and copying the files into the places he specified, I just unzipped them into the plugins directory and activated it. That was the whole problem – I needed to copy his “wp-mobile” theme over into the wp-content/themes directory. WordPress was trying to find it, and couldn’t, so it reverted automatically back to the default theme.

So next time read the README file carefully, and make sure you understand it! Imagine that if i report this to WordPress as a bug. 😯

Today WordPress just released it latest version, WordPress 2.0.7, this release is mainly focus on security fix in a PHP bug, the FeedBurner issue in WordPress 2.0.6 also solved in this version. Other changes are:

• Security fix for wp_unregister_GLOBALS() to work around the zend_hash_del_key_or_index bug in PHP 4 versions less than 4.4.3 and PHP 5 versions less than 5.1.4 with register_globals set to “On.”
• Feeds now properly serve 304 Not Modified headers instead of mismatched 200/304 headers (a.k.a. the FeedBurner bug).
• Backport of another 304 Not Modified fix from WordPress 2.1
• Deleting WordPress Pages no longer gives an “Are You Sure?” prompt.
• After deleting a WordPress Page, you are now properly redirected to the Edit Pages screen.
• Sending an image at original size in Internet Explorer no longer adds an incorrect “height” attribute.

You can download the latest version of WordPress at here, or head over to Mark’s blog to get the necessary upgrade file if you are upgrading from WordPress 2.0.6.

Mark also mention in WordPress development blog that the next major release of WordPress (WordPress 2.1) will be out soon by the end of this month.

Other than that bbPress 0.75 also released today, same like WordPress 2.0.7 one of the major fix is the PHP bug. To download latest version of bbPress please go here.

Just updated my WordPress to the latest version, WordPress 2.0.6, and also applied the FeedBurner fix, where sometime FeedBurner will return an error telling that you have invalid xml, or an error message like below:

Your server disconnected us before sending the full source feed content. If your blogging platform is TextPattern, this is a known bug, and a fix can be found here: http://forum.textpattern.com/viewtopic.php?id=11247

Here’s an explanation from NeoSmart:

Explanation

FeedBurner uses something called “Conditional Get requests” to ask your server whether or not the page has changed since the last it viewed it, in order to save you some bandwidth. Depending on how popular your site is, FeedBurner may hit up your feed up to hundreds of times a day, so this is a really good idea! Unfortunately, in WordPress 2.0.6, your site doesn’t respond in a way that FeedBurner recognizes. The 304 headers it sends back to let it know that the content hasn’t changed are malformed and corrupt – and FeedBurner has no idea what they mean.

To fix this problems is easy, all you have to just open up your functions.php inside your wp-includes folder, go to line 2231, 2233 and 2234 and comment out this three lines, like below:

That should fix your feed problem, there are a few more solutions from Mark Jaquith and NeoSmart, head over to their blog and find the one suit you most! 🙂

WordPress 2.0.5 released three days ago, while most of the WordPress user are now writing their blog with peace of mind, some of them are having the server 500 error. According to Mark Jaquith, it’s due to the bug that was reported for WordPress 2.1.

Fixing this error is some what easy, for it’s fixable just by installing a plugin, below are the step to fix this error.

1. Download this plugin.
2. Upload it to your WordPress plugins folder.
3. Activate the plugin.

However if you get an error message after logging in to your admin panel and cannot click the Plugins tab, just type “{WPDIR}/wp-admin/plugins.php” into your address bar and press enter, and this should fix the problem.