10th May 2007
What we call walking or hillwalking in the U.K. goes under the banners of hiking, tramping and yomping in other parts of the world. One term that we share with other parts is backpacking and this is much bigger in the U.S. than it is in the U.K. My hillwalking blog has come to the attention of members of the hillwalking and backpacking community and WordPress’s logging of who visited my blog has alerted me to this and allowed to find other similar blogs.
Why have I mentioned this here? The reason is that it has allowed me to see what blogging software others have been using. Blogger seems to be a very popular choice with a number using Windows Live Spaces, in the process making me aware that Microsoft has dipped its toes into the hosted blogs space. Other than this, I have also seen Typepad being used and one or two self-hosted operations to boot, mine included. Intriguingly, I have yet to encounter a fellow hillwalking fan in the U.K. using WordPress.com to host a hill blog, but I do know of a German backpacker having one. Video blogging is used by some, with the ever pervasive YouTube becoming a staple for this, at least for the ones that I have seen.
It’s an intriguing survey that leaves me to wonder how things develop…
24th March 2007
My Drupal investigation is currently in hiatus, but I did get to exploring the world of modules and adding to the standard ones supplied. Drupal doesn't have a WYSIWYG editor supplied in the standard package, so I went and added one that I have used elsewhere: FCKEditor. Setting wasn't much of a problem until I encountered the following error: Unknown element of UniversalKey panel. The solution to the problem is to remove the reference to UniversalKey from the configuration file fckeditor.config.js. Since it took a spot of finding, here it is for posterity and so that I'll find again...
18th March 2007
After reading an article in the latest issue of PC Plus, I got curious about the world of content management systems again. I went over to OpenSourceCMS to sample the CMS demos that they have got on there. Mambo and Joomla! (I wish they dropped that exclamation mark; it messes up automated grammar checking) are fully fledged CMS’s and look impressive too, though how they would fit into my online presence is something of an open question. Since I spied that PHP-Nuke uses themes, that is an attraction; I am already used to that mindset thanks to WordPress. While Drupal is seemingly less slick than the others, that could be an attraction in itself; it does offer themes but no rich text editing is available.
Though all of the above are built on top of PHP/MySQL, I ignored them for some reason when I last looked at open-source content management systems. That does seem a strange thing to do, but this was a while ago and the moderate cost of adding database functionality to my website was not something that I was willing to pay, though I have done so since for HennessyBlog.
Therefore, I ended up seeing what Plone (built on Zope and using the Python programming language) could do. What I was had in mind at the time was a replacement for Perl-powered photo gallery, and a CMS was never going to fit the bill; it still doesn’t. In any case, Plone left me with the impression that it was an all or nothing affair when I like coexistence of website components on a single server. Things may have changed since then, so giving it another go remains an option.
Now that I have decided to have a look at Drupal, the emphasis this time is not on using it as a photo gallery platform; if I wanted that, I’d go with the API for something like Flickr or Zooomr. This time, the emphasis on using a CMS to manage the visitor information directories on my website. It does coexist with the other website components, including WordPress and the aforementioned bespoke built photo gallery. Interestingly, Drupal does offer blogging functionality if I wanted it.
Set up involved a spot of work with MySQL before moving onto other things:
mysql -u adminuserid -p /* logging in*/
create database drupal; /*creating new database*/
grant ALL on drupal.* to adminuser identified by “**********”; /* granting access to new database */
quit; /* exiting */
Because it is easier to see what’s going on (not wrong, hopefully), I prefer command line working with MySQL. For some reason, Drupal comes only in tar.gz archives, so I extracted this into the web server directory and opened up the site in Firefox. Installation only requires the set-up of database access and is soon completed. A few things turned up in the status report that needed attention: cron, this can be run manually; activation of PHP Unicode and GD library (PHP’s gd_info function is a real help in testing this) extensions, editing of php.ini to remove commenting semicolons activated them and restarting Apache made them available; having a place to store uploads, the directory called files got created.
Since then, I have set about bending it to my will, not always an easy thing to do with software. The first thing to do was to give it a static home page. By default, Drupal places tasters for any nominated pages and stories on its home page and shows configuration instructions until you allow some content to filter through. However, adding the Front Page module allows you to override this behaviour and have something more static. It was an entry on Kehan’s Blog that set me heading in the right direction.
The next steps were to persuade the thing to allow external links to exist in menus (though patches exist, I have yet to learn how to apply them other than finding the nefarious piece of code and replacing, a considerable challenge that makes me wonder if there is not a better way to do it: with a module, perhaps?) and carry on the theme editing until it ties in with the rest of my site. Then, I’ll make the decision whether to replace my current workflow (Perl-powered pre-processing of XML into PHP/XHTML using XSLT and the Saxon parser followed by FTP upload to the web server) with this one. The automation of the former argues in its favour. We’ll see how things pan out…
7th March 2007
My other blog is experiencing what feels like a deluge of comment spam. All that I can say is thank goodness for Askimet. And that is with visitors having to subscribe in order to post comments. It seems that a way has been found around that. I did have a spurious user with obdolbin.com as their website address and got rid of them but the flow still continues. Blogger does seem to have a way around this: entering the letters from an image to stop bots from doing their thing. Maybe we'll see WordPress doing the same?
Update: It seems that the torrent has now slowed to a trickle. Maybe getting rid of the spurious user has worked after all and it just took a while for the effect to kick in.
24th February 2007
Solo Technology has posted about a nice extra available in the Visual Editor in WordPress 2.1. Hit ALT+SHIFT+V in Firefox and ALT+V in IE, gets you an extra row of buttons adding more editing options. He is currently trying to add a button to the main bar for doing the toggling.
P.S. While on the subject of blog post management, I have been playing around with w.bloggar, and I have to say that it works well; with a spot of persuasion, it even edits WordPress blog pages. The only things attempting to spoil the experience are the odd instances where odd characters get added to blog posts or characters in posts get misinterpreted. I'll try to add more in time.
1st February 2007
Though it seems strange to say it, I am making good use of Word’s blogging capabilities. Having had WordPress.com’s blog editor mangle one of my posts – incidentally while using Opera as my browser - is the cause of this turn of events.
When setting up new accounts, there are a number of presets available to be used to work with major blogging providers such as Blogger, WordPress, and Typepad. This is not all, though, as it is possible to hook up to other blogs in a more generic fashion. In fact, I have able to hook up to my other WordPress-powered blog; hosted on the same server as my personal website and with all the associated programming and scripting handled by myself. Where you have a number of accounts set up in the application, a drop-down menu appears in the post so that you can select the account to be used.
Speaking of dropdown menus embedded in the post, you can add categories to a post from the blog server’s own collection, and you can have more than one in any post. This feature is a boon, as is the ability to edit posts that are already on there, yet Word only seems to show a subset of all the posts on the server, about 20 I think, rather than each one. Another caveat is that you need to use a separate window for each post, or you’ll end up overwriting posts in error. Whether this is a result of RSS feed settings or is intrinsic to Word itself remains something that I have yet to discern. As it is Word, formatting, insertion of objects such as hyperlinks and images is very much part of the package. That said, uploading images via this route was not something that I tested until I was writing this post, but it seems to work well.
Apart from the irritations discussed above, I did find Word crashing a few times, but no data got lost thanks to its seemingly excellent file recovery capabilities, a definite counterpoint to some of my experiences with Word’s file recovery feature in previous versions. Eventually, the Office Diagnostics tools kicked in to see if all was well and, after carrying out both hardware (memory, hard drive, etc.) and software checks, an installation repair was performed. Let’s see if this resolves the issue. Even so, the crash repair and diagnostics were not something that I had seen to the same extent in previous versions of Office, and they did look pretty impressive.
In summary, Word does seem to be a good blogging tool, but I wouldn’t use it on its own because of its inability to download a full list of posts for editing. A blog’s own interface will remain necessary for that. Also, Word is far from being the only “offline” blog editor out there, and I am tempted to have a look at the likes of BlogJet and w.bloggar.
28th January 2007
I have had a look at how the posts from this blog are listed on Technorati and most if not all the titles are coming through as "Permalink". I was going to try WordPress.com support, but they are off for the weekend. A trip to the WordPress.com forums was then in order and a few helpful folk put me right on this one: apparently Technorati uses the permalink titles when extracting post summaries from WordPress.com blogs and in the Andreas04 theme that I am using, these are all hard-coded as "Permalink". I have left the theme's author in on this and going to try WordPress.com feedback tomorrow. In technical terms and from what I can see, the fix needed is as follows: change title="Permalink" totitle="Permanent Link: " in the single.php, page.php and index.php files in the theme.