Three dot oh dot one
Bug fixes to make you smile
Update your WordPress

This maintenance release addresses about 50 minor issues. The testing many of you contributed prior to the release of 3.0 helped make it one of the best and most stable releases we’ve had.

Download 3.0.1 or update automatically from the Dashboard > Updates menu in your site’s admin area.

Note: If you downloaded 3.0.1 in the first 20 minutes of release (before 2200 UTC), you’ll want to reinstall it, which you can do right from your Updates screen. Our bad.

Source: WordPress.org

In this article I am going to tell you how you can enable the Network settings option to enable multi-site feature in WordPress 3.0.

Step 1: Go to the wordpress root directory and open wp-config.php file.
Step 2: Add the following code and save the file
define('WP_ALLOW_MULTISITE', true);
Step 3: Go to your WordPress Dashboard and now you can see “Network” added in your Tools options. This mean you have successfully enable multiple site Network option in WordPress 3.0
Step 4: To add Click on Network under Tools Options and fill in the details and install it

For a more comprehensive look at everything that has improved in 3.0 check out 3.0′s Codex page or the long list of issues in Trac. (We’re trying to keep these announcement posts shorter.) Whew! That’s a lot packed into one release. I can’t think of a better way to kick off the 3.X cycle we’ll be in for the next two and a half years.

The Future

Normally this is where I’d say we’re about to start work on 3.1, but we’re actually not. We’re going to take a release cycle off to focus on all of the things around WordPress. The growth of the community has been breathtaking, including over 10.3 million downloads of version 2.9, but so much of our effort has been focused on the core software it hasn’t left much time for anything else. Over the next three months we’re going to split into ninja/pirate teams focused on different areas of the around-WordPress experience, including the showcase, Codex, forums, profiles, update and compatibility APIs, theme directory, plugin directory, mailing lists, core plugins, wordcamp.org… the possibilities are endless. The goal of the teams isn’t going to be to make things perfect all at once, just better than they are today. We think this investment of time will give us a much stronger infrastructure to grow WordPress.org for the many tens of millions of users that will join us during the 3.X release cycle.

It Takes a Village

I’m proud to acknowledge the contributions of the following 218 people to the 3.0 release cycle. These are the folks that make WordPress what it is, whose collaboration and hard work enable us to build something greater than the sum of our parts. In alphabetical order, of course.

Download WordPress 3.0 RC3

• Custom menus are finished! Yay!
• Multi-site is all set.
• The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.
• There are a ton of changes, so plugin authors, please test your plugins now, so that if there is a compatibility issue, we can figure it out before the final release.
• Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
• There are a couple of known issues.

If you are testing the RC and come across a bug, you can:

• Report it on the wp-testers mailing list
• Join the dev chat and tell us live at irc.freenode.net #wordpress-dev
• File a bug ticket on the WordPress Trac

We hope you enjoy playing with the 3.0 RC as much as we’ve enjoyed making it for you. Enjoy!

Download WordPress 3.0 RC1

Source: Jane Wells in WordPress.org

Gmail 502 Server Error

Today when I try to check my gmail from FireFox, I encounter 502 Server Error. But when I try different browser like Internet Explorer 8, I was able to check it smoothly. So, there is problem in Firefox and gmail.

Further after that I realized that if you clear your Firefox browser cache and cookies than you will be able to check your email even from FF.

Following the successful post-WordCamp San Francisco code sprint, they release the second beta of WordPress 3.0 which is ready for download.

Things to test:

• Revised menu user interface
• Changes to the WordPress exporter and importer to make it more flexible

Already have a test install that you want to switch over to the beta? Try the beta tester plugin.

Testers, don’t forget to use the wp-testers mailing list to discuss bugs you encounter.

There are a number of new features, enhancements, and code updates, so if you’re interested, download the beta and report any bugs that you find.

Check out the WordPress Version 3.0 enhancements and fixes. Please note, things could change before final release: Click Here

<body <?php body_class(); ?>>

What body_class() Generates

The body_class() function is quite similar to post_class() function that was introduced in WordPress 2.7. The only differences are the classes it generates. The body_class() function will generate the classes mostly based on where your viewer is on your site.

Following in example of the class that is generated through body_class() function when your visitor come to your site
In Hompage: <body class="home blog">
In Interviews Category: <body class="archive category category-interviews">
In About us Page: <body class="page page-id-2">
In Post: <body class="single postid-36">
In 404 Error Page: <body class="error404">

But the then it will add extra class logged-in if your visitors are logged in your site.

To add to more: The body_class() may include one or more of the following values for the class attribute.

• rtl
• home
• blog
• archive
• date
• search
• paged
• attachment
• error404
• single postid-(id)
• attachmentid-(id)
• attachment-(mime-type)
• author
• author-(user_nicename)
• category
• category-(slug)
• tag
• tag-(slug)
• page-parent
• page-child parent-pageid-(id)
• page-template page-template-(template file name)
• search-results
• search-no-results
• logged-in
• paged-(page number)
• single-paged-(page number)
• page-paged-(page number)
• category-paged-(page number)
• tag-paged-(page number)
• date-paged-(page number)
• author-paged-(page number)
• search-paged-(page number)

You can also extend the body call with the use of Hook in your Function.php file in your theme. The following in the example that you can use it is function.php file
add_filter('body_class','my_body_classes');
function my_body_classes($classes) {
if (is_single()) {
if (in_category('News')) {
$classes[] = 'category-news';
} else if (in_category('Travel & Nepal')) {
$classes[] = 'category-travel-nepal';
} else if (in_category('Interviews')) {
$classes[] = 'category-interviews';
} else if (in_category('How To')) {
$classes[] = 'category-how-to';
}
}
return $classes;
}

What I did in the above hook is that I forced body_class() function to add the category name in which the post belongs while viewing the post. Now, when you will view your post you will see the category name in which it belongs: Following are the example:
In Post which belongs to News category: <body class="single postid-36 category-news">