Is Godaddy compatible with Wordpress at all?
Quick question: Is Godaddy compatible with Wordpress at all? Thanks for any answer. 2nd question I got is.. G'day all,.

New layout I'm doing involves setting a background image in it's own div. Never done this before, but I'm sure it can be done..

Demo page is at

The obvious problem is that the text in the #main div is not extending over the top of the image. Quite amazing really because I have had the reverse problem before and it has frustrated the hell out of me..

I've tried shifting the placement of the code for it all over the place, floating right, margins, padding, clears but all to no avail...

Comments (4)

You betcha! but... you might want to make sure and wait for another person to confirm this as I am not sure. Better yet, why don't you contact the Godaddy guys because they can help better...

Comment #1

Update and solution for my problem..

I had the background in the #wrap on the page and eventually got it all sorted out by setting the image on the x axis to 83%. This was fine in Firefox. Then I go to IE and low and behold it is placing the image 83% within the div so it was too far left..

After a bit of to and fro with different bits and pieces, I applied the background image in the body element thus:-.

Background:url(../images/tree.jpg) #040 83% 15% no-repeat fixed;.

Works fine in both FF and IE...

Comment #2

Background-attachment: fixed is a little odd. According to the spec, the image is always fixed in relation to the viewport, regardless of the element in which the background occurs. Firefox does this properly, which is why the image was occuring outside the element. Internet Explorer renders this incorrectly (although, in my opinion, a bit more sensibly), hence the difference..


Comment #3

Thanks for the explanation re the viewport Rys. Now I understand why it was doing it. However, I must say, that for the first time I can think of, I agree with you that IE is doing something far more intuitively in respect of the expectations of the code...

Comment #4

I have seen one good demonstration as to why it works the way it does, but I find it difficult to believe that the W3C had it in mind when they created that spec (nor does the author claim that they did). In the end, it's probably for the best, since it actually opens up more options as to how it can be used, but it's very confusing..



Comment #5

This question was taken from a support group/message board and re-posted here so others can learn from it.