It's... not IE!
23 May 2006 15:58Percussion Rhythmyx, you have brought my wrath down upon yourself. When something works in the preview, it should also work when published out. All of the content items I'm using are in a public state, all of the content types are properly coded. The page is assembled and complete. The CSS is in place and functional, and all of the markup is good.
Why, oh why, when I run a full publish edition, do you decide to simply not bother with half of the homepage? What's more, why do you decide to not bother with it and then tell me it's all worked fine.
To add insult to injury, most of the bits you've left out this time were present last time and working fine. Can it be that adding something new to the page will miraculously break previously functioning parts for no apparent reason? Why yes, it can.
Rhythmyx, you are the diseased offspring of a pile of festering yak sputum and the horn of a bull that has recently been removed from the rear of a matador. Remove yourself from my sight before I am forced to smite you with fire for making me type your name (no mean feat, I should add) in a rant such as this.
Why, oh why, when I run a full publish edition, do you decide to simply not bother with half of the homepage? What's more, why do you decide to not bother with it and then tell me it's all worked fine.
To add insult to injury, most of the bits you've left out this time were present last time and working fine. Can it be that adding something new to the page will miraculously break previously functioning parts for no apparent reason? Why yes, it can.
Rhythmyx, you are the diseased offspring of a pile of festering yak sputum and the horn of a bull that has recently been removed from the rear of a matador. Remove yourself from my sight before I am forced to smite you with fire for making me type your name (no mean feat, I should add) in a rant such as this.