rustindy

That might be a truer statement than you know. If you’re currently young (say early twenties or less), there’s a fair chance that by the time you reach 60, medical technology will have extended lifetimes by up to 100%. By the time you reach 100 (and still hale and hearty), that will be extended by another 100 years. Finally, when you’re around 160 or so, computer technology will have caught up and you’ll have the option of copying yourself to an electronic form – just in case the age-reduction treatments fail 🙂 And if they do fail and you wake up dead instead of 25, just wait another 100 years for them to be able to grow you a stub body cloned from your original.

So if you think about it, 18446744073709551615 posts becomes more possible with each passing year.

jdingman, I do still develop for IE – but it saves a LOT of time to develop standards-compliant code first and then get IE to work with it. IE’s bugs are (mostly) well docuemented at various locations, and if you actually understand CSS and XHTML (as opposed to your only experience being the …For Dummies book), it’s simple enough to work that way. It also let’s you bypass browser-sniffing, which is becoming more and more frowned upon – sites should just work, whether I’ve got a blank or modified referrer field, javascript disabled, etc.

I can’t speak for the Edit Theme page not working in IE – I agree, though, it should “just work.”

If you really want bullets in your Kubrick sidebar (which, IMHO, looks dumb), find the CSS rule for the UL and/or LI tags, and remove the line that says display-type:none;. No guarantees that the spacing will be perfect afterwards though, you might need to mess with the margins and width too.

if you’re running your own server, check the php.ini file and make sure the SMTP settings are valid. on Windows, if the SMTP server is on the same maching as the web server, the SMTP address has to be localhost or it won’t work (found this out the hard way).

Interestingly, our AWStats stopped being able to update his site stats as of about 10pm last night. Apache is still logging 4 hits per second (average), but the stats update wasn’t seeing anything new…

Just remember that forcing the site to be 1024 pixels wide will cause a horizontal scrollbar to appear for maybe 90% of the people who go to look at your site.

Either remove the xmlrpc.php file if you have access to it, or send an email to your ISP informing them that a serious (and potentially severe) security problem has been identified and a patch is available.

Of note, this security issue is now public, and worms have been seen in the wild. If you haven’t updated to 1.5.1.3 yet, do it before you go to bed tonite.

There are two solutions.

First, code your template such that viewers are free to resize the font as they see fit. In other words, don’t specify font sizes in pixels. Ever.

Second, offer two (or more) stylesheets and use a style-switcher to allow users to choose whether they would like the “normal” version or the “large-fonts” version.

The third solution is just to use a bigger base font size. There are so many sites out there using “10px” (or less) as their base font size and it sucks big-time.

Yup, was on purpose and seems to be displaying now. Still loaded with validation errors though. Rohitkumar, check http://validator.w3.org/ and (friendly suggestion) get rid of them errors 🙂