Submitted by Jonathan on 15 February 2005 - 10:54pm
Submitted by Jonathan on 14 February 2005 - 6:02pm
Submitted by Jonathan on 14 February 2005 - 5:35pm
Submitted by Jonathan on 13 February 2005 - 9:49pm
Submitted by Jonathan on 13 February 2005 - 10:54am
Submitted by Jonathan on 1 February 2005 - 10:27pm
Submitted by Jonathan on 25 January 2005 - 9:27pm
Submitted by Jonathan on 25 January 2005 - 8:58pm
Submitted by Jonathan on 23 January 2005 - 5:57pm
Submitted by Jonathan on 21 January 2005 - 11:46pm
Submitted by Jonathan on 12 January 2005 - 12:30am
Submitted by Jonathan on 11 January 2005 - 10:51pm
Submitted by Jonathan on 10 January 2005 - 1:11pm
Submitted by Jonathan on 6 January 2005 - 11:26pm
Submitted by Jonathan on 6 January 2005 - 8:01am
Submitted by Jonathan on 3 January 2005 - 9:35pm
Submitted by Jonathan on 1 January 2005 - 11:48pm
Submitted by Jonathan on 1 January 2005 - 11:18pm
Submitted by Jonathan on 22 December 2004 - 12:54pm
Submitted by Jonathan on 19 December 2004 - 1:45am
Submitted by Jonathan on 17 December 2004 - 6:08pm
Submitted by Jonathan on 17 December 2004 - 5:57pm
Submitted by Jonathan on 17 December 2004 - 5:20pm
Submitted by Jonathan on 15 December 2004 - 7:45pm
Spent some of this morning upgrading my blog site software to the latest version... Drupal 4.5.1 and found that by following the upgrade process fails to make the new site work. So apologies to those who tried to access my blog and failed earlier. Now working, but restored to the older version sadly.
When I was in the throws of bug fixing, Ali came up to me and said 'If it ain't broken, don't fix it" - which is not a bad rule to live by if you are quite content with things 'just working'.
I'm far too curious for my own good sometimes, and when I can see cool plugins and features which are only available to me if I am running the latest blog software... then I have to bite the bullet and move on.
Another reason to upgrade is simply to maintain an up-to-date version so that future upgrade procedures are more straight-forward. I think Drupal have yet to produce an upgrade procedure which doesn't require you to upgrade through each version.
Submitted by Jonathan on 30 November 2004 - 10:43pm
Now that we have resumed a normal Internet service following a fault with the University network over the past few days, I got wondering about how people might still be able to read content even though our servers, or anyone else's for that matter, was unavailable.
Google have been cache'ing (storing a history of) websites for years, and I remembered that this might be useful for when sites are unavailable..... simply go to www.google.com and type in the following:
cache:[url of site]
e.g. cache:www.jonathansblog.net
If your site has been cached, Google will return the page as it was the last time Google crawled it.
There is a whole heap of Google Web Search Features, including calculators, language translators, dictionary definitions etc.
Pages