Due to a spot of neglect on my part, A recent server upgrade led to a domain routing error and my URL directed traffic to a hopelessly bad spam site catering to MySpace users. Joy. The issue is resolved, but artifacts remain. Uploaded images and my sub-domains were erased from the digital ether and a prolonged session of file uploads seems in order.
More soon.
I updated the Drupal engine to vesion 4.7.2 this morning. The transistion has been fairly smooth. Some new features have farked a bit of the non-essential content display, but I've been tossing around the idea of refactoring a lot of the site anyway. There is too much elbow room on the site for the tiny amount of content it contains.
Logging in to the site this morning form work I couldn't help but notice that IE is actually displaying the site content mostly properly. Perhaps some float model bugs were fixed? Of course, if that is the case I may have some other tweaking to do on other site layouts. After all, creating pixel prefect layouts with CSS almost requires hacks in order to maintain consistent rendering across a myriad of buggy or inconsistent browsing platforms.
The Internet Explorer Development Blog informs site developers many IE-specific and aggravating CSS bugs will be fixed. Until then Microsoft developers recommend phasing out any hacks and workarounds. In the spirit of this bold proposal, I built the new USL Site Theme using no CSS hacks.
I've been mulling over content organization again. The vast majority of new posts are Blog Entries; there simply isn't enough traffic to warrant Fora. Of course, I'd have to move content from the Fora to the Blogs, but that could damage my Google Page Rank.
A new version of Drupal has been released, and that means I'll be updating the site. There are a buttload of changes, so the site will be down for some time while I install the new system and associated modules. Changes in the 4.6.0 release can be found here.
CSS Support IE 7.0's Weakest Link - dilbertspace writes "Anyone who has ever developed a website knows that cross-browser and cross-platform compatibility is a nightmare, mainly due to Microsoft's willful non-compliance with the CSS2 standard. As this eWeek article points out, it seems Microsoft will continue their poor support for CSS2 even in the IE 7.0 release.
