Archive for August, 2010

I’ve been working on a fully fluid-width, XHTML Strict, table-less, three column child theme for WordPress’ Twenty Ten default theme…

And in the process, discovered a bottom margin bug!

I submitted the bug to a Trac ticket HERE and also documented the fix that would squash the bug flat and make Twenty Ten render the way it was supposed to which I will share here in my blog.

The Bug (in short):

The margin-bottom: 20px that is applied to the footer div triggers a well known CSS bug causing the 20px margin to be applied to the adjoining/bottom margin-touching wrapper div instead of the footer div.

That bottom margin you see at the bottom of the page where the end of the content wrapper should be touching the bottom of the screen?

That’s the bug.

The Fix (in short):

To correctly apply the 20px margin-bottom to the footer div and not accidentally to the wrapper div, the wrapper div needs to be given a 1px padding-bottom and the footer div needs to be given a 19px margin-bottom.

The padding applied to the wrapper where it touches the bottom of the footer container will trigger the margin-bottom to be rendered correctly for the footer and not the wrapper as the padding will add some ’separation’ between the two containers.

Another fix is to add a 1px border to the bottom of the wrapper and leave the 20px margin-bottom on the footer.

The border adds ‘content’ to the bottom of the wrapper which triggers the margin-bottom for the footer to be rendered correctly.

Why the Bug Happens:

Read the rest of this page »

It’s been a few long months owing to me having to take care of emergency familial issues, but remember that post I made back in March about Web Hosting Gone Wrong?

Shortly after I wrote that post, I spoke with Andrew from Media Temple about this matter and where he obviously was not allowed to go into situation specifics aside from what was publicly posted by Kyle, we were able to talk more in-depth about Media Temple’s policies and about specifics regarding theoretical situations which could result in the scenario that Kyle experienced. I aired my concerns – elaborated where necessary – and Andrew addressed them all quite thoroughly and we spoke at length about the various topics I had addressed in my previous blog posts.

At this point (actually, much earlier, but I have been unable to really sit down to write until now – sorry, Andrew!), I have to say that where I still have mild concerns about the potential ‘ease’ of going over resource allotment, I am satisfied with the results of the conversation and no longer have that sour taste in my mouth or the same misgivings I once had.

In case it wasn’t evident in previous posts or in case anyone needs a reminder, I will reiterate that my concerns were NOT regarding MT charging for overages (in other words, I wasn’t saying that MT shouldn’t charge for overages, period).

My greatest concern was how unexpectedly the overage-causing situation had happened (it was a total and complete accident and there was no prior indication that such a problem would happen), what the ramifications were (triggering the overage as the situation caused resource over-usage), what the implications might be (how easy would it be to go over resource allotment?), and then how MT INITIALLY handled the situation.

As a courtesy to Andrew and Media Temple, I will address the issues one more time and then close this particular ‘chapter’ of blog posts regarding Web Hosting Gone Wrong.

Read the rest of this page »