Site changes

As you can obviously see, I have changed a few things around here. Let me introduce these one by one.

  • New theme. This is the most obvious change. The old one with white background and blue header started to get on my nerves. I also needed a theme which had support for navigation bar (more on this in a second). I liked the color scheme and how things were organized. I also put my ugly face in the header image. With all the blogs on the web using just a handful of themes I thought there should be a better indication that you are in a right place.
  • Navigation bar. Links to other sections of this site, like my Photoblog and Family Tree are back once again. There will now always be in the navigation bar, which is currently located at the top of each page. Search is there too.
  • Posts per page. Until now I used to have a fixed number of posts per page. It was like 10 or 15. I have decided to try a different approach. Now all posts from the last three days are displayed (RSS feed is not affected and still show the last 10 posts). Let me know what you think about this mode.

I am also still fixing small bits here and there that appeared after all my migrations. If you notice any weird behaviour – let me know.

Migrated to WordPress

I have finally managed to migrated to WordPress. Database statistics inform me that:

There are currently 1,884 posts and 479 comments, contained within 22 categories.

As of now I am still fixing minor glitches here and there, but major things work. Just to let you know what is broken:

  • Permanent links. They are not working yet at all. Fixed.
  • Old links. None of the old links are working. Partially fixed. All of them won’t work anyway. Let me know if you find anything that I missed.
  • Users. I haven’t created any except for amdin account and myself. Feel free to register though. Not a bug. My brother managed to register all by himself, thus there is no problem.
  • Thumbnails. Some pictures come out in their original size and thus really mess up the look and feel. I will attend to this problem shortly. Too much editing required. Only new posts will have proper thumbnailing. And those that I will fix manually. Please complain.
  • Google Ads. I don’t yet have it installed. I will fix the temlate very soon. Fixed. Google Ads will now appear only on full item pages. This should improve the click-through ratio due to better ad suggestions. Keep clicking.
  • Blogroll. WordPress has an excellent tool for maintaining a blogroll, but it is not very useful to me, since I have mine at BlogLines. I’ll fix the exporting script shotly. Fixed.

If you are subscribed to the RSS feed, please change the address of feed in your preferences to this RSS feed.

Wind of change or switching blogging software

It is spring again, and I am getting carried away by that wind of change that gets me every year. Once again, I am not satisfied with my website and I am ready to have some action in order to fix it.

After using Nucleus CMS for more slightly more than a year I got fed up with it. It seems that it is too flexible and modular for me.

Changing looks and feels by editing templates, skins, and files with stylesheets and blocks of sidebars is way too much. I would rather prefer less flexibility and more centralization. As things are, I always forget where I have to go to edit the output. There is also another issue with most of the stuff stored in the database instead of regular files. Plugins need to be reinstalled every time I edit them. This is not something that I am willing to do anymore.

Also having a huge pile of functionality in plugins rather than in the core has its drawbacks. Plugins are written by “other” people. Meaning that there is less quality control applied to plugins. And that there is version dependancy between plugins and the core software. This brings a lot of problems when upgrading the core. And I don’t want to fix the same problems over and over again.

Yet another issue I have with the user interface. The system is flexible and powerful, but the interface is by far from the well designed. As an example, consider settings. There are global settings for Nucleus installation, blog specific settings, user specific settings and plugin specific settings. All of these are all over the place and one has to remember what is where. Or browse through all of them. I don’t like it.

On top of my complaints toward Nucleus, I have a really pleasant experience with WordPress. User interface is clean and really thought-through. All the functionality that most people will use is in the core. Plugins are taking care of all the rest. It also features a better post editor, pinging tools, user management, and anti-spam utilities. There are also great improvements in the file uploading (thumbnailing, commenting, checking for dublicates and renaming).

Overall, WordPress seems like a much better system at the moment. In fact it seems so good that I can’t stand the fact of not using it. Thus, I will be switching to WordPress 1.5 in the next few days. It will take me some time to move all the posts from the last four years of my blogging. When it will be done, I will correct the obvious problems and will switch it to production.

One of the shortcomings that I can forsee from the change would be the links to posts. I have made a mistake with the structure of the permalinks. I will have to pay for it now. This will cause me a slight reduction in search engine and bookmark positions, but I am willing to do it anyway. If I got there once, I can get there again.

On the bright side, I will (finally!) fully standard compliant blog. Currently, there are still some problems with MS Internet Explorer and Konqueror. These should be fixed with the migration. I will also remove Google Ads from all pages of the blog and will leave it only for large articles, like “Vim for Perl developers” and “Practical RPM”. Maybe somewhere else too. But it will surely be gone from the main page.

So, please stay with me, while I pass this stage. I will keep you updated. You too please let me know of any misbehaviour that you might notice.

Upgrade of Nucleus CMS to version 3.2

I have just upgraded the site to Nucleus CMS version 3.2. I have also installed a few plugins. I am trying to get used to new post editor, so, please stay with me. Also let me know of any malfunctions that you can find. I looked around and checked and couldn’t find anything wrong, apart for the standard bugs caused by my customizations (permanent links, image popups and page encoding) and I have already fixed those.

Nucleus bits

In my recent bit on blogging software I mentioned a few shortcomings of Nucleus CMS.

I am missing a better WYSIWYG post editor, sub-categories for posts and multipaged posts.

I was suspecting that these needs might have been solved with plugins. I didn’t check the availability of these plugins and that makes me feel guilty and curious at the same time. I have browsed through the plugin list and found out that everything can be, indeed, fixed. Thus, here is a todo list for my next maintenance window for this site.

  • Upgrade Nucleus CMS installation from version 3.15 to version 3.20 (or whatever version will be the latest by that time). Some plugins that I am planning to install require version to be equal or greater than 3.20. Plus, of course, I don’t want to be running old bugs when I can have a selection of new ones.
  • Install NP_WYSIWYG_RTE.php plugin. It provides a better post editor.
  • Install NP_PingPong.php plugin. I have only weblogs.com pinged automatically now. Technorati is done manually by me and only when I don’t feel too lazy to click on the browser button. With this plugin everything will be pinged automatically, which is a good thing.
  • Install NP_PageBreak.php plugin. This will allow me to break long posts into multiple pages. “Vim for Perl Developers” is the first candidate.
  • Install NP_MultipleCategories.php plugin. Cross-posting articles in multiple categories improves navigation and searching for specific post. This is something I often miss.
  • Install NP_Captcha.php plugin. One of the most effective SPAM fighting mechanism for web forms is asking a user to read some string from the image and write it down in the form field. This plugin provides just that.

Probably I will find another one or two plugins to install that will improve the experience with this site.