<div style=”background-color: #E3F0F2; border: 1px solid #222222; padding: 5px 0px 5px 10px;”>

via Colored Text Widgets for your WordPress Sidebar Part 1.

The instructions at the following blog solves the issue.

Cannot load adsense-deluxe.php fix

• It has a good graphical user interface.
• Does not require .htaacess file editing
• Very good documentation

Get it

Issue:

• At some point after upgrading to 2.6 I noticed that users that submitted comments were getting a blank page ending with normalstuff/wp-comments-post.php.
• However, I could comment on the same post without any issue while logged in as an admin.
• The problem only happened on older post, post created a couple of versions prior the 2.6 upgrade. Post created following the 2.6 upgrade worked both as the admin and the user.

Resolution:

• The wp-comments-post.php document contained a blank line after the closing php tags “?>” (around line #85). This causes issues in PHP at times. I removed the blank space, tested posting comments to at least 3 post that had failed prior and the issue appears to be resolved.

Note: According to the Author, this plug-in sends a 503 service unavailable for feeds and trackbacks stating that the service will be available in X. X is set by the admin. WordPress endorses this plug-in.

http://sw-guide.de/wordpress/plugins/maintenance-mode/

Updated 7/8/2009

The following plugins can also be used to perform this task:

• WordPress Lock out Plugin
• WordPress Password Plugin

New versions, upgrades, updates, releases, disasters or any other name you can think of to describe changes to a software application that you use, often cause problems for you, the end user. We will refer to this event as an upgrade for this article.

One of the things that you can do to prevent this is to prepare for your upgrade. This is when you, the application user, do all of the things that you complain that the software manufacturer did not do. PREPARE!

Obviously there are times that you do not have control over these upgrades or you are not given significant notification or information (cough, WINDOWS) to PREPARE.

Here is a generic list of steps that can be used to prepare for upgrades. Obviously , there will be exceptions but this list will help.

1. Modifications/Plug-ins/customizations/- If your application is using any additional modules or items that are not a part of the application during the initial installation. Make sure you check to see if the developers support modifications under the new upgrade before hand. Be sure to look deep since often over time we forget that some of this modules did not come with the application.
2. Backups - If your application, no matter what it is, stores data remotely or locally on your PC. Use back features if available. If not make backup copies of these files. If you are not sure what files, ask the ISP(if remote), manufacturer or developer.
3. Testing - In some situations you may be able to install the new upgrade without over writing your current version. If this is the case, you should install the upgrade and configure the application (adding modules) until you get it the way the you want it. You should use the new application for a minimum of 30 days. That will give you time to test many scenarios that you will likely not test in a few hours following the upgrade. If all is well with your upgrade then you can either continue to use the new install and archive the old (Just in case over time you find an issue and need to rollback to the old version) OR simply complete the upgrade of your original application and delete the test version.

Again this list is generic and can be used for any application. Now for the WordPress version of this list. Some users have not had good experiences with the WordPress 2.3 upgrade.

WordPress Upgrade preparation list

1. Modifications/Plug-ins/customizations/ – Plug-ins that do not work with 2.3
2. Backups and Testing - Excellent article on 5 steps to upgrade WordPress. Contains backup plug-ins and great testing procedures.

A complete WordPress 2.3 upgrade Preperation post

• “My Blog Post Title” code =

  • <title><?php wp_title(''); ?><?php if(wp_title(' ', false)) { echo ' | '; } ?>

  • <?// php bloginfo('name'); ?></title>

• “My Blog Post Title >> Blog Name” code=

  • <title><?php wp_title(''); ?><?php if(wp_title(' ', false)) { echo ' >> '; } ?>

  • <?php bloginfo('name'); ?></title>

• “My Blog Post Title by Blog Name” code =

  • <title><?php wp_title(''); ?><?php if(wp_title(' ', false)) { echo ' by '; } ?>

  • <?php bloginfo('name'); ?></title>

All of these options will display only the Blog name on pages where there is no Title (i.e. The home page) This portion of the code cares for that <?php if(wp_title(' ', false)) { echo ' | '; } ?>

All of these options are possible by adding the code displayed above to your template Header.php file. All of the code beneath each example (between the title tag) should be placed together.

For more information and details see www.ardamis.com