I would like to know the answer too. Anyone here know what is the answer to that question. I'll do some research in Google and get back to you if I bump into an decent answer. You should email the people at iPage as they probably could answer your iPage question..
Http://validator.w3.org/check?uri=ht...tern+Europe%29.
Yup, you have a lot of things messed up...
Check the error list for 539 errors, many of which are the same error repeated many times (which makes it all a lot easier to fix):.
Http://validator.w3.org/check?uri=ht...tern+Europe%29.
<noscript>.
Is not allowed inside.
<head>.
..
There must be no other code between.
</head>.
And.
<body>.
Tags..
Add.
Type="text/javascript".
To every.
<script>.
Tag..
Add a.
Type="text/css".
Attribute to every.
<style>.
Tag..
You have duplicated the.
Text.
Attribute:.
Text="#000000" BGCOLOR="#ffffff" TEXT="#000000".
... take one out..
It never used to matter if tags used upper or lower case. In.
HTML 4.01.
It is.
Recommended.
To write all tags and attributes in.
Lower case.
For.
XHTML.
An.
XML.
It then becomes a.
Requirement.
..
The four.
Margin.
Errors can be replaced with a little bit of CSS code instead. Put this in a text file, with a name ending in.
.css.
:.
Body {.
Margin: 0px;.
Padding: 0px;.
}.
In this code you close a.
</center>.
Tag but you don't have an opening.
<center>.
Tag. Add an opener, or remove the closer:.
<td>.
<b><font face="arial,helvetica"><font color="#FFFFFF"><font size="-2">.
....
</font></font></font></b>.
</center>.
</td>.
The.
<font>.
Tags have a lot of code bloat too..
Identical adjacent opening tags that each have a separate attribute, like.
<font size="2"><font color="#FFFFFF"><font face="ariel">.
, can be combined so that it becomes one tag with several attributes, like.
<font size="2" color="#FFFFFF" face="ariel">.
For example. This then only requires one closing.
</font>.
Tag, instead of three..
In many places you have three opening.
<font>.
Tags but only one closing.
</font>.
Tag. Combine the three opening tags into one each time..
This will solve most of the errors on the page..
There are 539 HTML errors on this page alone. Work through all of the stuff above, and then post again when there are just a few errors left. It is impossible to tell you the fixes for every single error on the page right now. Post again when there are just a few left and it will be a lot easier to see what is going on then...
I lost the link coming back here and just now finally found you again..
Thank you so very much for your replies. And yes, I knew there were.
TONS OF ERRORS.
..
That's why it took me a bit, to gather up enough courage to post!.
I shall return when I get it down to only a few errors..
Again, thank you so much for your time helping me..
Rusty..
Glad you are working on this. Post again if you get stuck with anything at all..
Ummm, we are here to help. No point in you having a duff webpage when there are dozens of people here that can help you make it look nicer, have better content, work better with search engines, etc, etc, etc...
Side note....
NM doesn't seem to like my xhtml transitional coding when it comes to closing the single tags with.
Space/>.
Example....
<br />..
I'm not endorsing NM, I just used it because it can show you alot of your errors without declaring a DOCTYPE. Things like nesting and improper tag placement..
(I'm not sure if NM takes the different versions of HTML into account; therefore, it might not like the space/slash)..
If you're declaring a DOCTYPE, I would recommend W3C's Validator...
Yeah. my error part was just in the browser compatability portion for that anyways, so no biggy. most people are viewing my iPage site are in newest browsers anyways..
W3C likes me..