BlogFwrd - Gadgets, technology, web development and a dude

Theme Validation Problem

I have some problems validating this new theme of mine with W3C markup validator. So far there is nothing wrong with the markups or anything, and I have triple checked it again and found no problem at all. Yet the validator keeps saying that there is a problem at line 106. It is a code for search form which is using the default WordPress search form setup. It seems like when W3C’s validator crawl the site, WordPress responses with some kind of variable making the validator to output error for that certain line.

This is the first time I am getting this kind of unknown error and problem with validator. So far it is the only validation error that this them is having. Talking of the theme, this is my new theme and it may looks a bit different in IE 7 and below (I have tested with IE8 and it works alright) due to some of the CSS markups I use. It works best with FireFox, Safari and Opera.

I am planning to release this them to the public, but it may have to wait until I have lots of time to clear the theme files and make it widget friendly.

Web Standards dude meets WebSphere!

Recently, I am involved in a project for a corporation (can’t disclose the name due to NDA) which uses IBM’s Websphere as its backend CMS.  My duty is to overhaul the portal UI (sort of theme). This is my first time dealing with IBM’s Websphere which is known for breaking the standards (Web Standards) and its limited support for proper markup.

As I am still in conceptualization stage, I have yet to encounter any problem with creating standards compliance templates. However, it sounds pretty bad from what I have heard regarding lack of proper support for Web Standards compliance markups in WebSphere. The challenge is on for sure, and I am gonna do whatever I can to enforce Web Standards at enterprise level.