Keeping IT Simple

My 2-year old Samsung LCD monitor died on me a few weeks ago, and little did I know that this would lead me down the path of investigating an issue and looking through Firefox' HTML parser code.  But that's what I did, and my experience simply reinforced my belief that HTML markup used on websites need to be validated.

This is the 3rd article in the series covering DRUPAL v6 bootstrap process.  As the bootstrap name implies, this phase covers initializing a connection to a database.

The previous article in this series focused on phase 1 of the Drupal bootstrap process (DRUPAL_BOOTSTRAP_CONFIGURATION). This article will now focus on the second phase - DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE.

For all of my video editing needs I use Adobe's Premiere Elements, and for the most part it works without any issues.  A few months ago I decided to upgrade to version 7 from version 2.  Things were going fine, but when I recently tried opening a project file I had worked on in version 2 I got an error.

I recently enabled the taxonomy module in Drupal so that I could easily categorize things when creating new content.  Everything seemed to be working fine, but when I created a post yesterday I got the following error when I started entering keywords to tag my article:

An HTTP error 0 occurred.
http://itnitwit.com/taxonomy/autocomplete/2

When investigating a recent rash of spam user registration on my site I began looking through Drupal core to gain a better understanding of its inner workings and how modules could be used to guard against these nuisances.  Like every journey there is a beginning, and for me it all started with index.php. 

I recently encountered another issue with scripts running on Internet Explorer.  In this particular instance I was running IE6, which unfortunately is still a corporate standard where I work.  I take comfort in knowing I'm not the only one that still uses this browser, but I long for the day when these older buggy and non-standard compliant browsers are no longer used or that their use has become so statistically insignificant that supporting them is simply not worth the effort.

When recently surfing the web, I came across the warning symbol again .  I was more interested in the site's contents and therefore didn't pay attention to it.  A short while later I was browsing the same website, but this time using Firefox.  I didn't encounter any errors, and there were animations on the screen I hadn't seen when I had browsed the same site using Internet Explorer. So I decided to investigate further.

I’ve been working on a website for a friend of mine these past few weeks and admittedly most of my time was being spent working around some browser idiosyncrasies (namely IE) and fine tuning CSS to make things work consistently across different browsers. 

Don't mind the mess - the site is currently under construction. I expect the site to be up and running some time in May - just need to get my bearings on Drupal.