Error message

  • Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in include_once() (line 1389 of /Library/Server/Web/Data/Sites/Documents/jonathansblog/includes/
  • Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in require_once() (line 341 of /Library/Server/Web/Data/Sites/Documents/jonathansblog/includes/

Warning message

The service having id "facebook_widget" is missing, reactivate its module or save again the list of services.

Usability again... this time, with tagging content


Tom Smith accurately points out the usability gaff in being able to tag content 'on the fly' when creating the page using most blog or content management tools. This blog is powered by Drupal, Tom is right...

And here's the rub. Tools like WordPress require you to create a category BEFORE you have created the item you want to add that category too. This is so backward. It'??s a simple usability error. Most web-based software does this and it is such an obvious gaff.

With it being such a source of frustration, I tend not to bother and forget.

It can't be that hard to make a little pop-up window that submits tags to the database as you write the content... else, why doesn't someone just modify the form to create a space to add new tags as you submit the page... easy?


Spot on. Each time Drupal build another release I have to consider the opportunities created by upgrading to their latest release versus the pain caused in upgrading, which largely means...

1. discovering what modifications have been made between the current version and the upgrade (I only do this, so that if the upgrade goes pear-shaped, I know where to start looking to fix it.)

2. understanding the upgrade path.... can I upgrade from 4.1 to 4.6 or do I need to follow an upgrade path, 4.1 --> 4.2 --> 4.3

3. reminding myself, what customisations have I made to the core code, so that I can re-apply those changes after the upgrade.

4. having the courage to fix what ain't broken.

Your comments spur me on to write a series of posts on 'the problem with open source'

Absolutely agree - I do't understand how web content management and other content management software has lasted so long forcing people to define the categories up-front. Tools like del.ici.ous seem to be turning the tide though and showing others the value of tagging rather than categorisation.

Having worked in the Enterprise Content Management software industry I wished someone would do del.ici.ous for enterprise content as well as web content, so a few friends and I set up Same tagging model as del.ici.ous but when you tag a piece of content on your desktop it also uploads to the service for central storage and backup.

Would be good to get your view on this usage model...

Nice post. Thanks!!!

Very helpful content and informative. Thanks!

very informative...thanks for the post.....

Add new comment

Filtered HTML

  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Enter the characters shown in the image.