Sep 24

WordPress 2.3 is out

Just before going to bed, I turned on my computer to check my emails and to check my blog stats, which is my daily routine before the day is out. I noticed that WordPress 2.3 is released. This version is named “Dexter” for the great tenor saxophonist Dexter Gordon. I am very excited about this new version, and cannot wait to upgrade my current version. Unfortunately, it’s about mid-night now, and I should be in bed and am afraid that I have to wait until tomorrow when I get to my office to do the upgrade.

Thanks WP folks for your hard work and the greatest blogging software.

Update:

I upgraded my blog to WordPress 2.3, and as usual the upgrade process was very easy and smooth. There are many new features in WP 2.3, and Aaron Brazell blogged on 10 Things You Need to Know About WordPress 2.3, it is very helpful.

I did encounter a bug in 2.3: it keeps giving me an error like this:

ERROR; WordPress requires Cookies but your browser does not support them or they are blocked.

The workaround is to comment out line 24, 313, and 314 in wp-login.php file. WordPress developers fixed this bug and will release 2.3.1 soon with some other bug fixes.

[ratings]

Sep 08

Error message: Object reference not set to an instance of an object

If you use the TableAdapter Configuration Wizard in Visual Studio 2005 to create a strong-typed dataset (as described in Scott Mitchell’s ASP.NET 2.0 Data Access Tutorial – Creating a Data Access Layer), you will be asked if you would like to save the database connection string in the configuration file. If you choose to save it, it will be placed in the <connectionStrings> section.

Save the Connection String to <code>Web.config</code>

But what if you want to change the name of the saved connection string later? It is kinda tricky. If you manually change the name in the configuration file, you will find that every time you save a file, you will get an error message: object reference not set to an instance of an object. It is because when you manually change the name of the connection string in the configuration file, Visual Studio 2005 designer does not know the change, so it still uses the old name to retrieve the connection string and causes the error. So to avoid this error, you should change the name of the connection string in the designer, not in the configuration file.

[ratings]