theres an error on my site and i cant figure out wut or where it is... can someone take a look at if for me plz<br />
my site (<!-- m --><a class="postlink" href="http://www.geocities.com/xdragracing/">http://www.geocities.com/xdragracing/</a><!-- m -->)
<!--content-->never mind my friend fixed it sry for wasting your time<!--content-->You fixed an error? This will give you something to do: [Click here (<!-- m --><a class="postlink" href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.geocities.com%2Fxdragracing%2F&charset=iso-8859-1+%28Western+Europe%29&doctype=HTML+4.01+Transitional&ss=1&outline=1&sp=1&verbose=1">http://validator.w3.org/check?uri=http% ... &verbose=1</a><!-- m -->)]. There are a few more to fix up yet.<br />
<br />
All of these problems have been answered in this forum in the last few weeks, if you read a few old posts you will soon find them.<!--content-->uh... i dont get it<!--content-->its a validator - it checks your code against an international recommendation (in this case the transitional one) and lets you know where there are possible causes for concern. This is because you might be using code that current browser do not yet or no longer support that particular element.<!--content-->>> This is because you might be using code that current browser do not yet or no longer support that particular element. <<<br />
<br />
However, in this case most of the errors are entity errors, which can be fixed by changing each & to & in every URL. Codes beginning with & are reserved for entities such as © and so on. If you need an & in a URL, then writing just & makes the system see this as trying to define an entity and returns an error. If you want an & symbol in a URL, you have to use the full & entity version of it, in order to avoid generating these entity errors.<br />
<br />
<br />
Other problems with the document include incorrectly nested elements, various typos in tags and attributes, elements opened but not closed, or closed in the wrong order, and other errors with the logic, structure and syntax of the document. There are some browser specific pieces of code, but those aren't so important to fix.<br />
<br />
Post again, if you need help with fixing any specific errors.<!--content-->
my site (<!-- m --><a class="postlink" href="http://www.geocities.com/xdragracing/">http://www.geocities.com/xdragracing/</a><!-- m -->)
<!--content-->never mind my friend fixed it sry for wasting your time<!--content-->You fixed an error? This will give you something to do: [Click here (<!-- m --><a class="postlink" href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.geocities.com%2Fxdragracing%2F&charset=iso-8859-1+%28Western+Europe%29&doctype=HTML+4.01+Transitional&ss=1&outline=1&sp=1&verbose=1">http://validator.w3.org/check?uri=http% ... &verbose=1</a><!-- m -->)]. There are a few more to fix up yet.<br /><br />
All of these problems have been answered in this forum in the last few weeks, if you read a few old posts you will soon find them.<!--content-->uh... i dont get it<!--content-->its a validator - it checks your code against an international recommendation (in this case the transitional one) and lets you know where there are possible causes for concern. This is because you might be using code that current browser do not yet or no longer support that particular element.<!--content-->>> This is because you might be using code that current browser do not yet or no longer support that particular element. <<<br />
<br />
However, in this case most of the errors are entity errors, which can be fixed by changing each & to & in every URL. Codes beginning with & are reserved for entities such as © and so on. If you need an & in a URL, then writing just & makes the system see this as trying to define an entity and returns an error. If you want an & symbol in a URL, you have to use the full & entity version of it, in order to avoid generating these entity errors.<br />
<br />
<br />
Other problems with the document include incorrectly nested elements, various typos in tags and attributes, elements opened but not closed, or closed in the wrong order, and other errors with the logic, structure and syntax of the document. There are some browser specific pieces of code, but those aren't so important to fix.<br />
<br />
Post again, if you need help with fixing any specific errors.<!--content-->