Devam Ediyor

501186 Website error fix

Hello

I posted a project before for a website design and upload. The programmer who shall remain nameless who won the auction. Created and uploaded the template with loads of errors. So now I need to fix them.

go to [url removed, login to view]

I need the programmar to fix the problem.

I checked the errors with a software and there are 139 errors and 36 warnings, which I need cleared up. Also the admin for the forum is not accessable. These problems are minor and dont require alot of time.

Please send me a quote or you will not be answered.

Here is the list of problems:

Validation Output: 139 Errors

Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"

<html>

✉

The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

Warning Line 8, Column 71: cannot generate system identifier for general entity "ref"

…[url removed, login to view]" ty…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 8, Column 71: general entity "ref" not defined and no default entity

…[url removed, login to view]" ty…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 8, Column 74: reference to entity "ref" for which no system identifier could be generated

…[url removed, login to view]" type=…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 8, Column 70: entity was defined here

…[url removed, login to view]" t…

Warning Line 35, Column 25: NET-enabling start-tag requires SHORTTAG YES

</head><script src=[url removed, login to view] ></script>

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 35, Column 25: required attribute "TYPE" not specified

</head><script src=[url removed, login to view] ></script>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 35, Column 76: end tag for element "SCRIPT" which is not open

</head><script src=[url removed, login to view] ></script>

✉

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Error Line 36, Column 37: there is no attribute "LEFTMARGIN"

<body bgcolor="#cccccc" leftmargin="0" topmargin="0" marginwidth="0" marginhei…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 36, Column 51: there is no attribute "TOPMARGIN"

…or="#cccccc" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" onL…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 36, Column 67: there is no attribute "MARGINWIDTH"

…tmargin="0" topmargin="0" marginwidth="0" marginheight="0" onLoad="MM_preloadI…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 36, Column 84: there is no attribute "MARGINHEIGHT"

…rgin="0" marginwidth="0" marginheight="0" onLoad="MM_preloadImages('images/fet…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 36, Column 177: document type does not allow element "BODY" here

…preloadImages('images/[url removed, login to view]','images/[url removed, login to view]')">

✉

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Error Line 42, Column 20: there is no attribute "BACKGROUND"

<td background="images/[url removed, login to view]">

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 45, Column 95: required attribute "ALT" not specified

…ef="[url removed, login to view]"><img src="images/[url removed, login to view]" hspace="10" border="0" ></a></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 48, Column 28: required attribute "TYPE" not specified

<td align="center"><style>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 48, Column 28: document type does not allow element "STYLE" here

<td align="center"><style>

✉

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Error Line 65, Column 51: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

…c="images/[url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]"…

✉

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

Warning Line 65, Column 53: NET-enabling start-tag requires SHORTTAG YES

…"images/[url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]">V…

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 65, Column 53: required attribute "ALT" not specified

…"images/[url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]">V…

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 66, Column 55: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

…mages/my [url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

Warning Line 66, Column 57: NET-enabling start-tag requires SHORTTAG YES

…ges/my [url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 66, Column 57: required attribute "ALT" not specified

…ges/my [url removed, login to view]" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 67, Column 71: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"

…idth="30" height="32" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

Warning Line 67, Column 73: NET-enabling start-tag requires SHORTTAG YES

…th="30" height="32" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 67, Column 73: required attribute "ALT" not specified

…th="30" height="32" align="absmiddle" /> <a href="[url removed, login to view]…

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 67, Column 114: cannot generate system identifier for general entity "page"

…="absmiddle" /> <a href="[url removed, login to view]">FAQ</a> </span>

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 67, Column 114: general entity "page" not defined and no default entity

…="absmiddle" /> <a href="[url removed, login to view]">FAQ</a> </span>

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 67, Column 118: reference to entity "page" for which no system identifier could be generated

…="absmiddle" /> <a href="[url removed, login to view]">FAQ</a> </span>

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 67, Column 113: entity was defined here

…="absmiddle" /> <a href="[url removed, login to view]">FAQ</a> </span>

Warning Line 71, Column 101: NET-enabling start-tag requires SHORTTAG YES

… width="250"><font style="font-size:16px;"><strong> <br /></strong></font></td>

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Warning Line 72, Column 77: NET-enabling start-tag requires SHORTTAG YES

…e"><img src="images/[url removed, login to view]" border="0" />   <img src="images/pay…

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 72, Column 77: required attribute "ALT" not specified

…e"><img src="images/[url removed, login to view]" border="0" />   <img src="images/pay…

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 72, Column 150: NET-enabling start-tag requires SHORTTAG YES

…>   <img src="images/[url removed, login to view]" border="0" vspace="15" /></td>

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 72, Column 150: required attribute "ALT" not specified

…>   <img src="images/[url removed, login to view]" border="0" vspace="15" /></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 79, Column 19: NET-enabling start-tag requires SHORTTAG YES

</table><br /></td>

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 84, Column 64: required attribute "ALT" not specified

<td width="43" align="right"><img src="images/[url removed, login to view]" ></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 87, Column 60: required attribute "ALT" not specified

<td align="right"><img src="images/[url removed, login to view]" ></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 90, Column 65: cannot generate system identifier for general entity "hard_id"

…er"><a href="[url removed, login to view]" class="topnav">…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 90, Column 65: general entity "hard_id" not defined and no default entity

…er"><a href="[url removed, login to view]" class="topnav">…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 90, Column 72: reference to entity "hard_id" for which no system identifier could be generated

…href="[url removed, login to view]" class="topnav">Coming …

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 90, Column 64: entity was defined here

…ter"><a href="[url removed, login to view]" class="topnav"…

Warning Line 90, Column 77: cannot generate system identifier for general entity "no_cart"

…"[url removed, login to view]" class="topnav">Coming Soon<…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 90, Column 77: general entity "no_cart" not defined and no default entity

…"[url removed, login to view]" class="topnav">Coming Soon<…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 90, Column 84: reference to entity "no_cart" for which no system identifier could be generated

…php?event=products&hard_id=yes&no_cart=yes" class="topnav">Coming Soon</a> </t…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 90, Column 76: entity was defined here

…="[url removed, login to view]" class="topnav">Coming Soon…

Error Line 94, Column 68: reference to entity "page" for which no system identifier could be generated

…><a href="[url removed, login to view]" class="topnav">Contact Us</a…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 67, Column 113: entity was defined here

…="absmiddle" /> <a href="[url removed, login to view]">FAQ</a> </span>

Warning Line 96, Column 82: cannot generate system identifier for general entity "hardn_id"

…[url removed, login to view]" class="topnav">New Released…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 96, Column 82: general entity "hardn_id" not defined and no default entity

…[url removed, login to view]" class="topnav">New Released…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 96, Column 90: reference to entity "hardn_id" for which no system identifier could be generated

…ent=new_featured_all_products&hardn_id=no" class="topnav">New Released</a></td…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 96, Column 81: entity was defined here

…[url removed, login to view]" class="topnav">New Release…

Warning Line 98, Column 82: cannot generate system identifier for general entity "hardf_id"

…[url removed, login to view]" class="topnav">Featured Pr…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 98, Column 82: general entity "hardf_id" not defined and no default entity

…[url removed, login to view]" class="topnav">Featured Pr…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 98, Column 90: reference to entity "hardf_id" for which no system identifier could be generated

…ent=new_featured_all_products&hardf_id=yes" class="topnav">Featured Product</a…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 98, Column 81: entity was defined here

…[url removed, login to view]" class="topnav">Featured P…

Error Line 104, Column 51: required attribute "ALT" not specified

<td width="20"><img src="images/[url removed, login to view]" ></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 117, Column 100: required attribute "TYPE" not specified

…185" align="right" valign="top" class="leftnav"><script language="javascript">

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 159, Column 80: NET-enabling start-tag requires SHORTTAG YES

… <td><img src="images/[url removed, login to view]" width="171" align="right" /></td>

✉

The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

Error Line 159, Column 80: required attribute "ALT" not specified

… <td><img src="images/[url removed, login to view]" width="171" align="right" /></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 169, Column 141: there is no attribute "BORDER"

…bmitsubscribe" id="submitsubscribe" src="images/[url removed, login to view]" border="0" alt="">

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Error Line 177, Column 51: there is no attribute "HEIGHT"

…gn="center"><table width="168" height="138" border="0" align="right" cellpaddi…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Warning Line 179, Column 185: cannot generate system identifier for general entity "category_id"

… <a href="[url removed, login to view] free mobile p…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 179, Column 185: general entity "category_id" not defined and no default entity

… <a href="[url removed, login to view] free mobile p…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 179, Column 196: reference to entity "category_id" for which no system identifier could be generated

…="[url removed, login to view] free mobile phone">Sim f…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 184: entity was defined here

… <a href="[url removed, login to view] free mobile …

Warning Line 179, Column 199: cannot generate system identifier for general entity "category"

…[url removed, login to view] free mobile phone">Sim free…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 179, Column 199: general entity "category" not defined and no default entity

…[url removed, login to view] free mobile phone">Sim free…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 179, Column 207: reference to entity "category" for which no system identifier could be generated

…?event=products&category_id=1&category=Sim free mobile phone">Sim free mobile …

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 198: entity was defined here

…[url removed, login to view] free mobile phone">Sim fre…

Error Line 185, Column 85: required attribute "ALT" not specified

… <td width="15" height="20" align="right"><img src="images/[url removed, login to view]"></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Warning Line 186, Column 75: cannot generate system identifier for general entity "second_level_cat_id"

…ong><a href="[url removed, login to view]…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 186, Column 75: general entity "second_level_cat_id" not defined and no default entity

…ong><a href="[url removed, login to view]…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 186, Column 94: reference to entity "second_level_cat_id" for which no system identifier could be generated

…php?event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu"…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 74: entity was defined here

…rong><a href="[url removed, login to view]…

Warning Line 186, Column 98: cannot generate system identifier for general entity "first_level_cat_id"

…event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ver…

✉

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Error Line 186, Column 98: general entity "first_level_cat_id" not defined and no default entity

…event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ver…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Error Line 186, Column 116: reference to entity "first_level_cat_id" for which no system identifier could be generated

…ond_level_cat_id=10&first_level_cat_id=1&category=Vertu">Vertu</a></strong></t…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 97: entity was defined here

…?event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ve…

Error Line 186, Column 127: reference to entity "category" for which no system identifier could be generated

…nd_level_cat_id=10&first_level_cat_id=1&category=Vertu">Vertu</a></strong></td>

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 198: entity was defined here

…[url removed, login to view] free mobile phone">Sim fre…

Error Line 189, Column 85: invalid comment declaration: found name start character outside comment but inside comment declaration

…--------------------------------------End third lavel-------------------------…

✉

Info Line 188, Column 15: comment declaration started here

<!-- ------------------------------------------------start third …

Error Line 189, Column 86: character data is not allowed here

…-------------------------------------End third lavel--------------------------…

✉

You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or

forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or

using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Error Line 191, Column 85: required attribute "ALT" not specified

… <td width="15" height="20" align="right"><img src="images/[url removed, login to view]"></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 192, Column 94: reference to entity "second_level_cat_id" for which no system identifier could be generated

…php?event=products&second_level_cat_id=9&first_level_cat_id=1&category=Sony er…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 74: entity was defined here

…rong><a href="[url removed, login to view]…

Error Line 192, Column 115: reference to entity "first_level_cat_id" for which no system identifier could be generated

…cond_level_cat_id=9&first_level_cat_id=1&category=Sony ericsson">Sony ericsson…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 97: entity was defined here

…?event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ve…

Error Line 192, Column 126: reference to entity "category" for which no system identifier could be generated

…cat_id=9&first_level_cat_id=1&category=Sony ericsson">Sony ericsson</a></stron…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 198: entity was defined here

…[url removed, login to view] free mobile phone">Sim fre…

Error Line 195, Column 85: invalid comment declaration: found name start character outside comment but inside comment declaration

…--------------------------------------End third lavel-------------------------…

✉

Info Line 194, Column 15: comment declaration started here

<!-- ------------------------------------------------start third …

Error Line 195, Column 86: character data is not allowed here

…-------------------------------------End third lavel--------------------------…

✉

You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or

forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or

using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Error Line 197, Column 85: required attribute "ALT" not specified

… <td width="15" height="20" align="right"><img src="images/[url removed, login to view]"></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 198, Column 94: reference to entity "second_level_cat_id" for which no system identifier could be generated

…php?event=products&second_level_cat_id=4&first_level_cat_id=1&category=Samsung…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 74: entity was defined here

…rong><a href="[url removed, login to view]…

Error Line 198, Column 115: reference to entity "first_level_cat_id" for which no system identifier could be generated

…cond_level_cat_id=4&first_level_cat_id=1&category=Samsung">Samsung</a></strong…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 97: entity was defined here

…?event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ve…

Error Line 198, Column 126: reference to entity "category" for which no system identifier could be generated

…level_cat_id=4&first_level_cat_id=1&category=Samsung">Samsung</a></strong></td>

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 198: entity was defined here

…[url removed, login to view] free mobile phone">Sim fre…

Error Line 201, Column 85: invalid comment declaration: found name start character outside comment but inside comment declaration

…--------------------------------------End third lavel-------------------------…

✉

Info Line 200, Column 15: comment declaration started here

<!-- ------------------------------------------------start third …

Error Line 201, Column 86: character data is not allowed here

…-------------------------------------End third lavel--------------------------…

✉

You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or

forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or

using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Error Line 203, Column 85: required attribute "ALT" not specified

… <td width="15" height="20" align="right"><img src="images/[url removed, login to view]"></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 204, Column 94: reference to entity "second_level_cat_id" for which no system identifier could be generated

…php?event=products&second_level_cat_id=5&first_level_cat_id=1&category=Nokia">…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 74: entity was defined here

…rong><a href="[url removed, login to view]…

Error Line 204, Column 115: reference to entity "first_level_cat_id" for which no system identifier could be generated

…cond_level_cat_id=5&first_level_cat_id=1&category=Nokia">Nokia</a></strong></t…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 97: entity was defined here

…?event=products&second_level_cat_id=10&first_level_cat_id=1&category=Vertu">Ve…

Error Line 204, Column 126: reference to entity "category" for which no system identifier could be generated

…ond_level_cat_id=5&first_level_cat_id=1&category=Nokia">Nokia</a></strong></td>

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 179, Column 198: entity was defined here

…[url removed, login to view] free mobile phone">Sim fre…

Error Line 207, Column 85: invalid comment declaration: found name start character outside comment but inside comment declaration

…--------------------------------------End third lavel-------------------------…

✉

Info Line 206, Column 15: comment declaration started here

<!-- ------------------------------------------------start third …

Error Line 207, Column 86: character data is not allowed here

…-------------------------------------End third lavel--------------------------…

✉

You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or

forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or

using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Error Line 209, Column 85: required attribute "ALT" not specified

… <td width="15" height="20" align="right"><img src="images/[url removed, login to view]"></td>

✉

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Error Line 210, Column 94: reference to entity "second_level_cat_id" for which no system identifier could be generated

…php?event=products&second_level_cat_id=11&first_level_cat_id=1&category=Motoro…

✉

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Info Line 186, Column 74: entity was defined here

…rong><a href="[url removed, login to view]…

Error Line 210, Column 116: reference to entity "first_level_cat_id" for which no system identifier could be generated

…ond_level_cat_id=11&first_level_cat_id=1&category=Mo

Beceriler: Her şey Kabul, HTML, MySQL, PHP, Betik Yükleme, Şablonlar, Web Sitesi Tasarımı, XML

Daha fazlasını görün: net enabling start tag requires shorttag yes, general entity defined default entity, generate system identifier general entity, line column attribute class, general entity page defined default entity, document type declaration implying doctype html system, attribute onload, you ver, you fix, xml validator web, xml use case, xhtml template free, x-cart web design, x cart web design, x-cart programmer, x cart programmer, where to start as php programmer, web template free entry data, website to create website for free, website template free fix, website style design free, website errors fix, website editing software, website design types, website design template for message

İşveren Hakkında:
( 0 değerlendirme )

Proje NO: #2247107