My dilemma now is whether I should stop using this WordPress Plugin or just delete the data before so as not to occupy too much space of my database. I am not very particular about statistics but once in a while it just makes me smile looking at the data. Although I am not a Statistics freak, I am also using WordPress.com Stats and Google Analytics. I like both WordPress.com Stats and Google Analytics but Counterize II has features which I like too which I did not find at Google Analytics nor WordPress.com Stats. Maybe I have not fully explored WordPress.com Stats and Google Analytics yet as I do not often check my statistics anyway.

While writing this, I thought, ok, I will give it a try one more time. I will check WordPress.com Stats and Google Analytics thoroughly first. If I think it is time to let go of the Counterize II WordPress Statistics Plugin, then I will just let it go.

And oh, I am hoping that one of these days, that people who developed WordPress.com Stats would try to get hold of the Counterize II Plugin developer and maybe come up of an idea of combining the other features of Counterize II with WordPress.com Stats.

Wouldn’t it be great?

Related links: Counterize II WordPress Plugin, WordPress.com Stats, Google Analytics

Well, upgrading the blog and the sites went fine. I just followed my 10 Steps to upgrading WordPress.

I noticed something though at the Plugins section regarding Widgets before I upgraded the blog and sites using WordPress 2.5 and even after upgrading to WordPress 2.5.1. Did you notice those remarks stating that a plugin has a new version available? Well, the link of the supposed new version of the Widget mentioned does not match to the particular Widget being used.

Let me illustrate it…

First Example:

There is a new version of Simple Recent Comments Widget available. Download version 1.2.1.20070210b here or upgrade automatically.

This text “Download version 1.2.1.20070210b here” is being linked to the Sidebar Widgets page in WordPress.org (as of this writing, the version is 1.2.1.20070210b as it may change later on) and not to the Simple Recent Comments Widget page (if there is any as I did not find the page when I search WordPress.org for it).

Second Example:

There is a new version of WP-PostViews Widget available. Download version 2.20 here or upgrade automatically.

This text “Download version 2.20 here” is being linked to WP-DBManager page in WordPress.org (as of this writing, the version is 2.20 as it may change later on) and not to the WP-PostViews Widget page in WordPress.org (as of this writing, the version is 1.20 as it may change later on). I am actually using the simple WP-PostViews (current version 1.20) and not WP-PostViews Widget.

Then I saw a discussion about WP-PostViews Widget at the Wordpress Forum, and Lester Chan (GaMerZ), the WP-PostViews and WP-DBManager Plugins developer, have explained why. Kindly click “wp-dbmanager is showing as an upgrade for wp-postViews Widget” for information.

Well, we’ll just have to bear with it, sooner or later, they’ll find the solutions for it. Creating Plugins for WordPress is voluntary and we should be grateful that we are benefiting from each developer’s work.

Kudos to the WordPress Plugins Developers!

I experimented on Pandan.ph though, and it has to do with WordPress Stats Plugin. I did not deactivate the WordPress Stats Plugin so I do not have to write the API Key again. To note, once you deactivate the WordPress Stats Plugin and activate it again, it will always ask for the API Key unlike the Akismet Plugin. The Akismet Plugin, once deactivated and activated, the API Key do not have to be supplied again.

Anyway, what happened? I was not able to access the dashboard at all. So, I deleted the WordPress Stats Plugin at the control panel as I know it was probably the cause. But it remained the same, I was not able to access the dashboard. So I deleted all the Plugins at the control panel as well, not at the Plugins menu. You can delete the Plugins via FTP too. Then uploaded the Plugins, activated them, and everything went fine.

Then I upgraded two (2) more sites on Monday, Pandan.gov.ph News and Pagtatap.org, and yesterday, LADiosolibrary.org, and everything went fine as well.

With Weggis.net, I upgraded it using the one-click upgrade by the web host and so far, everything went well too. Of course, I deactivated all the Plugins first, and only activated them afterwards.

Before that, I tested both WordPress 2.5 Release Candidate 1 and WordPress 2.5 Release Candidate 2 but did not write anything about it right away. I had issues with the built-in gallery then. I wanted to write about it but decided to wait for the official WordPress 2.5 release. I was relieved because what I wanted to do with the gallery can actually be done with the official release. I did not see those features of the built-in gallery at the Release Candidates 1 and 2. I probably overlooked those features but I will not discuss that further as it will only make this entry long. I’m still testing the gallery up to now anyway. I’m trying to explore what more could it do.

Anyway, as I have said in my last entry, I would take note of the database changes but the database did not really change that much, no additional tables at all, except for some which I’m not going to reiterate as you can read about it at the Weblog Tools Collection, 2.3 to 2.5 Database Changes.

I also said that the changes were not just minor changes. Indeed, it was not, WordPress 2.5 had a lot of major improvements. Let me say it, improvements. I will also not write about it as Matt Mullenweg wrote so extensively about it at the WordPress Development Blog, WordPress 2.5.

Regarding the WordPress Plugins I am using, I will also not write them here, just browse my past blog entries to know the Plugins that I have in my sites. One thing though, I no longer use the Filosofo Home-Page Control Plugin WordPress since using WordPress 2.3. Regarding Upgrading WordPress process, I just did the same, just like what I wrote in my past blog entries too, similar to Upgrading WordPress Extended.

I’m getting used to WordPress 2.5, and I’m liking it. Way to go WordPress People! Thanks to all of you!

By just reading what Matt posted a few hours ago, 2.5 Sneak Peek (a sneak peek at the WordPress 2.5 Release Candidate 1), it seems like a lot of changes have been made at the administration side, at the dashboard, navigation, write and manage screens. As I see it, I do not think that they are just minor changes.

Just to quote Matt, 2.5 Sneak Peek:

A customizable dashboard, multi-file upload, built-in galleries, one-click plugin upgrades, tag management, built-in Gravatars, full text feeds, and faster load times sound interesting? Then WordPress 2.5 might be the release for you. It’s been in the oven for a while, and we’re finally ready to open the doors a bit to give you a taste.

Let us see if it is to my liking. I have been waiting for the new built-in galleries. I did not want to use any image or photo plugins so I just used the pages for photo albums instead of the post as I use category and date features to archive the news articles and blog entries, and I do not want that with the photo galleries.

Let us tackle more about it later once I already tested it. I will especially pay attention to the database as I do not like the way files are being saved at the database at the past WordPress versions. In my opinion, if it could be done, pages and posts should not be on the same table. The images or photos as attachments should not be on the same table too with the pages and posts. Links, tags and categories should also be on separate tables.

Anyway, as I have said, let us discuss this further later. I will have to download it now and test it in my local computer.

Read 2.5 Sneak Peek at WordPress.org Blog for more information, and link to the zip file if you want to download it.

YES, it is recommended to upgrade if you have your registration enabled and you have any other users aside from you. If not, you can leave it as it is, as it won’t really affect your site. If you still worry, you can just upload the fixed version of xmlrpc.php.

When I read about this security release, I just uploaded the fixed version of xmlrpc.php. But I kept on reading this text “A new version of WordPress is available! Please update now.” every time I logged in. So after 13 days I finally gave in. I upgraded all the 8 sites.

There’s a way, of course, if you don’t want to read that message anymore. All you have to do is upload the version.php file under the wp-includes folder. But I’m not comfortable doing it that way, so I upgraded the sites just like I normally do.

And NO, you don’t have to upgrade if your registration is disabled and you’re the only one who has access to your blog or site. Regarding the other minor bug fixes, if those few minor bugs do not also affect your site, then there’s really no need to upgrade. When I read what they fixed, the problems were at the version 2.2, 2.3 and 2.3.1. If you upgraded to WordPress 2.3.2 already, and you encountered no problem at all, then you have the option not to upgrade.

But if you haven’t upgraded to WordPress 2.3.2 yet, then you might be affected, so I suggest that you should upgrade to WordPress 2.3.3. That’s for your own security too. Remember before you upgrade, always backup your files and database.

Note from Sofie: This is just my opinion. It is always your decision whether to upgrade or not.

There was no problem at all. I just followed my own 10 steps when I upgraded to WordPress 2.3.1 from WordPress 2.3. WordPress 2.3.2 is a bug-fix release just like WordPress 2.3.1. You are advised to upgrade immediately as the prior release can be used to expose your draft posts. It also suppresses some error messages that can give away information about your database table structure and limits. For more information, please read the entire blog entry at WordPress.org Blog about WordPress 2.3.2.

The good news is, the Counterize II WordPress Plugin that I deactivated in some sites is now doing fine, not anymore in conflict with google search, so I activated it again in all the other sites. I didn’t do anything at all, it was just fixed when I used the latest version of Counterize II WordPress Plugin, version 2.12.3.

I use the same Wordpress Plugins and you can read about them when I upgraded to WordPress 2.1 Ella.

You can download the new release WordPress 2.3.2 at WordPress.org.

It took me at least one and a half months to finish the site but in reality it was only two weeks as I was not working on it everyday. For me, it’s good to work on a project not on a daily basis so I will be able to think of something else that would be good for the site upon checking on it again.

The new web design was officially online on November 19, 2007 although the website has been online for probably three and a half years now.

I am always in contact with the founder of the Library and I thought of helping them as I am one of those very proud Pandananons, proud for having this one of a kind library in the Philippines, which is especially located in Pandan, Antique, the town where I grew up.

The Leocadio Alonsagay Dioso Memorial Public Library, located in Barangay Baybay, Pandan, Antique, Philippines, is the only full-service library in the area and the only one serving as an official access point for the Philippine Electronic Library “e-Lib” Project, for advanced researchers.

The Dioso Library was inaugurated on April 2, 2004, and has operated continuously since then, opening its doors to the public six days a week.

I upgraded the sites Sehdi.com, SofieHofmann.com Blog, Pandan.ph, Tugbong.pandan.ph, Pagtatap.org, Pandan.gov.ph News, and Weggis.net.

Every time I upgraded, I also wrote some details on how did I do it. So here it goes again.

My 10 steps to upgrading WordPress:

First, I downloaded the latest WordPress release in my hard disk. I downloaded it from the download page of WordPress.

Second, I extracted/unzipped the new files in my hard disk. With this, I was able to check the site locally because I installed IIS in my hard disk.

Third, I made a back-up of my database in my hard disk. I just accessed phpmyadmin online and then exported the whole database.

Fourth, I copied the old files to another folder, and also to my hard disk. If anything happens during the upgrade and the pages are not showing up properly, I can always revert to the old files.

Fifth, I changed the content of the index file at the root or at the folder where the Wordpress was installed. I did it using the web control panel, sometimes via FTP. The message goes like this, “Sorry, I’m upgrading the site right now. Please come back after a few minutes.” With this, visitors will know that nothing is wrong with the site or else visitors might get the internal server error message.

Sixth, I deactivated all the WordPress Plugins. This is just to avoid any pages not showing up properly in case the plugin is not compatible with the latest release of WordPress. I logged-in first of course at the admin page.

Seventh, I deleted the files except the index.php file, wp-content folder and config.php file. I deleted the files using the web control panel, it’s easier because if I do it via FTP, I just can’t delete the folder. I have to delete the contents of the subfolder first, if there’s any, then the contents of the folder, and then the folder.

Some notes though, I just visited the site of WordPress and read that there was no need for me to delete the files anymore. I could have just uploaded the files and the old files will be replaced. Copying the entire folder will overwrite the old files.

Eight, I uploaded the entire folder of the extracted files even including the wp-content folder via FTP. There were no plugins yet, except Akismet being always part of the release, at the wp-content folder of the new extracted release version, so no plugins have been replaced other than Akismet.

Take note, be very careful when deleting or overwriting files, read the details at the codex of WordPress on Upgrading WordPress. I noticed that they have rewritten the content here. So kindly check it out. I didn’t read it before I upgraded the sites to WordPress 2.3.1.

Ninth, I replaced the index file with the original content. With this, the pages will again show up properly.

<?php define(’WP_USE_THEMES’, true);
require(’./wp-blog-header.php’);
?>

Tenth, lastly, I checked the pages, and reactivated the plugins one at a time.

I didn’t have any problem with the upgrade and with the plugins. Everything just went smooth. You can read this entry, Upgraded to WordPress 2.1 Ella, to know what WordPress Plugins have I been using. I still use the same plugins. Check each site for new versions.

Anyway, if you notice at the Plugins section, there should be a message there if the plugin you use have a new version. Also, once you logged-in to your admin, there will also be a message that you are using an old version of WordPress and that you can download the latest version from the website of WordPress.

Actually, it took me 10 days only not the whole month to do the revision as I didn’t do it continuously. Well, 10 days is also quite long just to do a WordPress theme but I always would like my theme to be neat and nice according to my taste, if not perfect. I worked on it, only if I have time. I make sure that I will be able to concentrate on it.

I couldn’t anymore keep track how many times did I redesign Sehdi.com when I was not using WordPress yet. But this is the first time, that I redesigned it ever since I use WordPress as CMS for this site. When I converted the whole site in December 2006 to use WordPress, not only the blog, I just adapted the old design of this site.

The first WordPress theme was a two-column theme with 750px fixed width to make it still easier for those who are also still using 800×600 screen resolution.

The second WordPress theme is a fluid three-column theme. It still looks good at 800×600 screen resolution but the width will not expand if the user has bigger than 1024×768 screen resolution. The second sidebar adjusts if the user opted for a screen resolution to be even smaller than the old standard 800×600 screen resolution. I configured it that way as the second sidebar contains ads only aside from the random web design images which can be accessed at the first sidebar.

Regarding colors, I like the colors of the old WordPress theme, so I didn’t really change the colors.