Wordpress Version 2.0.3 Review

WordPress, the premier free, open source blogging utility origin, has undergone several improvements in their lives. Today is one of the most popular blogging tools on the internet, is easy to use, powerful and versatile. It also has a very active base of qualified users who are willing to improve the product and to help those who have not tried before.

Although version 1.5 Strayhorn is a favorite of many, is not as stable and as safe as the new version 2.0.3. The best part of the new version is the safety review, the new "nonce" key of security reduces the chances of that a malicious hacker to find a way into your admin panel. Besides the security fix, however, several minor bugs have been squashed with this version. Despite a major upgrade to 2.1 is due out soon, the 2.0.3 is something you definitely should download and install if only for security patches, that were actually ported from major update files.

In addition to installing 2.0.3, you must be aware that some errors were found, and install a plugin is needed to repair the errors. If you modify any of the files that this patch fixes plugin, you must be to merge the changes with the files new or make the changes manually once again. You can find these issues by running a diff to find changes, if the only changes we find are yours, then you're fine, and otherwise have to manually merge the new files.

The short list of what WordPress 2.0.3 fixes include:

• Improved performance of small
• Movable Type / Typepad importer fix
• Enclosure (podcasting) fix
• Increase security mentioned above (nonces)

One of the mistakes most upset with 2.0.3 also sent. It gives you an "Are you sure?" dialog when editing comments, and add a backslash before each quotation mark in the entry you are editing. Be sure to download the patch.

What about the security problem?

The security problem seems minor, but the WordPress team before setting becomes important. It is a mistake that takes advantage download the cookie when you register with WordPress. The cookie in question prevents someone unauthorized access to your admin panel. He is tied to your user account, and verify that you are the authorized account manager that is working on.

The bug is being fixed is one that takes advantage of a sociological trick. If someone creates a link or form pointing to your WordPress admin account, which might possibly be able to trick you into clicking the link. In the If the one here, you delete a post. This sounds much smaller and highly unlikely, but a small crack in the door can be exploited later by a dedicated hacker. And this is also the type of error that a few years ago, allowed a hacker to access databases from Microsoft, where they stole parts of Longhorn and other codes. So yes, you do need to take seriously.

WordPress has ensured that you are safe from this type of piracy through a utility called HTTP Referer. However, this utility has some issues. For example, JavaScript in Internet Explorer, can be spoofed. In addition, certain firewalls and proxies may delete information that is supposed to perform, leaving some people unable to use WordPress admin their accounts of how they are supposed to be able to.

Now, instead of the HTTP Referer, a nonce is used, which is a number used once. It's like a password that changes every twelve hours, and is valid for twenty four hours. The nonce is unique to the particular WordPress installation uses the WordPress user logged in, the action, the subject of the action, and time 24 hours of action. When you change any of these, the nonce is no longer valid. All plugin authors have to ensure the nonce is added to their forms and other interactive capabilities that may be affected.

Update WordPress 2.0.2 to 2.0.3

As with any upgrade, the first thing to do is a copy of safety of all: the files of the directory of WordPress, the plugin database with all the changes, and all the data being added should be supported too. Moreover, might be a good idea to make a second backup of all your WordPress directory just in case something goes wrong with your installation.

Now remove the wp-admin track. Also remove the wp-includes, except for translation and language files or directories that may have been added, add these files to the backup file you created earlier. Finally, delete all files of WordPress, which is installed with the exception of file title = "http://wp-config.ph"> http://wp-config.ph p.

You are now ready to begin installation. Download and unzip the 2.0.3 version as a separate installation directory. You want to ensure that it can handle files and directories to copy. Now install the new wp-admin and wp-includes directories.

Install the rest of the files directory, with the exception of the p http://wp-config-sample.ph file.

Now enter the admin panel. You should see the following message: "Your database is not updated. Please update. Follow the link below to update the database, and follow the instructions there. Now remove the files and wp-admin/install.php wp-admin/upgrade.php. Download the plugin fix add and activate it. Replace the backup files where they need to be and making comparisons, if you have modified any of the above files. This should take care everything.

For geeks, there is also an upgrade package that includes only the change files. Look for changes under Diff (2.0.2> 2.0.3). It consists of a zip file is much faster to install, but you must be sure you can handle before use.

About the Author

http://www.theinternetone.net

Firefox tip — Make web pages load quicker. (Read description for more information)