Validation Output: 36 Errors

1. Line 6, Column 8: required attribute "TYPE" not specified

   <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>.

2. Line 87, Column 237: end tag for element "A" which is not open

   …Takaisin työtiloihin" border="0"></a></td>');

   ✉

   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.

3. Line 87, Column 242: end tag for element "TD" which is not open

   …sin työtiloihin" border="0"></a></td>');

   ✉

   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.

4. Line 88, Column 178: end tag for element "A" which is not open

   …t="" title="Oma tila" border="0"></a></td>');

   ✉

   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.

5. Line 88, Column 183: end tag for element "TD" which is not open

   …title="Oma tila" border="0"></a></td>');

   ✉

   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.

6. Line 89, Column 199: end tag for element "A" which is not open

   …itle="Sulje oma tila" border="0"></a></td>');

   ✉

   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.

7. Line 89, Column 204: end tag for element "TD" which is not open

   …"Sulje oma tila" border="0"></a></td>');

   ✉

   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.

8. Line 90, Column 31: end tag for element "TR" which is not open

     dttxt1 = dttxt1.concat('</tr></tbody></table></div>');

   ✉

   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.

9. Line 90, Column 39: end tag for element "TBODY" which is not open

     dttxt1 = dttxt1.concat('</tr></tbody></table></div>');

   ✉

   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.

10. Line 90, Column 47: end tag for element "TABLE" which is not open

      dttxt1 = dttxt1.concat('</tr></tbody></table></div>');

    ✉

    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.

11. Line 90, Column 53: end tag for element "DIV" which is not open

      dttxt1 = dttxt1.concat('</tr></tbody></table></div>');

    ✉

    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.

12. Line 211, Column 46: end tag for element "TITLE" which is not open

       cookiePopup.document.write('<title></title></head><body class="objectstyle">');

    ✉

    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.

13. Line 211, Column 53: end tag for "SCRIPT" omitted, but its declaration does not permit this

       cookiePopup.document.write('<title></title></head><body class="objectstyle">');

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

14. Line 6: start tag was here

    ><script>

15. Line 211, Column 53: end tag for "HEAD" which is not finished

       cookiePopup.document.write('<title></title></head><body class="objectstyle">');

    ✉

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.

16. Line 213, Column 136: required attribute "ALT" not specified

    …c="/pics/actionarrow.gif" border="0"> Sulje</a></body></html>');

    ✉

    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>.

17. Line 213, Column 161: character data is not allowed here

    … border="0"> Sulje</a></body></html>');

    ✉

    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.
18. Line 218, Column 9: end tag for element "SCRIPT" which is not open

    </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.

19. Line 219, Column 7: end tag for element "HEAD" which is not open

    </head>

    ✉

    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.

20. Line 220, Column 59: document type does not allow element "BODY" here

    <body class="upmoststyle" onload="checkCookieExpiration()">

    ✉

    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).

21. Line 231, Column 266: required attribute "ALT" not specified

    …uudestaan jatkaaksesi työskentelyä."></a></span>&nbsp;<span id="cexp"></span>

    ✉

    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>.

22. Line 234, Column 5: end tag for "TABLE" omitted, but its declaration does not permit this

    </td>

    ✉

    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

23. Line 227: start tag was here

    ><table class="upmosttable1" border="0">

24. Line 242, Column 70: cannot generate system identifier for general entity "ws"

    …ctpath1"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"

    ✉

    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 "&amp;" (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 &aelig; 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.

25. Line 242, Column 70: general entity "ws" not defined and no default entity

    …ctpath1"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"

    ✉

    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.

26. Line 242, Column 72: reference to entity "ws" for which no system identifier could be generated

    …path1"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  

    ✉

    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.

27. Line 242, Column 68: entity was defined here

    …jectpath1"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikk

28. Line 242, Column 79: cannot generate system identifier for general entity "noedit"

    …<a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="

    ✉

    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 "&amp;" (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 &aelig; 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.

29. Line 242, Column 79: general entity "noedit" not defined and no default entity

    …<a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="

    ✉

    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.

30. Line 242, Column 85: reference to entity "noedit" for which no system identifier could be generated

    …f="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="" clas

    ✉

    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.

31. Line 242, Column 77: entity was defined here

    …"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title

32. Line 242, Column 88: cannot generate system identifier for general entity "name"

    …doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="" class="

    ✉

    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 "&amp;" (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 &aelig; 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.

33. Line 242, Column 88: general entity "name" not defined and no default entity

    …doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="" class="

    ✉

    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.

34. Line 242, Column 92: reference to entity "name" for which no system identifier could be generated

    …show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="" class="upmo

    ✉

    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.

35. Line 242, Column 86: entity was defined here

    …="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikko"  title="" class

36. Line 243, Column 447: reference to entity "ws" for which no system identifier could be generated

    …; <a href="config_frames?id=18745&ws=18683&mode=" title="Objektin hallinta" 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.

37. Line 242, Column 68: entity was defined here

    …jectpath1"><a href="doc_show?id=18745&ws=18683&noedit=1&name=/Palautuslaatikk

38. Line 243, Column 454: cannot generate system identifier for general entity "mode"

    …ef="config_frames?id=18745&ws=18683&mode=" title="Objektin hallinta" target="

    ✉

    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 "&amp;" (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 &aelig; 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.

39. Line 243, Column 454: general entity "mode" not defined and no default entity

    …ef="config_frames?id=18745&ws=18683&mode=" title="Objektin hallinta" target="

    ✉

    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.

40. Line 243, Column 458: reference to entity "mode" for which no system identifier could be generated

    …config_frames?id=18745&ws=18683&mode=" title="Objektin hallinta" target="MAIN

    ✉

    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.

41. Line 243, Column 452: entity was defined here

    …href="config_frames?id=18745&ws=18683&mode=" title="Objektin hallinta" target

42. Line 249, Column 5: end tag for element "TD" which is not open

    </td>

    ✉

    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.

43. Line 250, Column 24: document type does not allow element "TD" here

    <td class="upmostright"></td>

    ✉

    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).

44. Line 251, Column 5: end tag for element "TR" which is not open

    </tr>

    ✉

    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.

45. Line 252, Column 8: end tag for element "TBODY" which is not open

    </tbody>

    ✉

    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.

46. Line 253, Column 8: end tag for element "TABLE" which is not open

    </table>

    ✉

    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.

47. Line 255, Column 7: end tag for element "HTML" which is not open

    </html>

    ✉

    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.

↑ Top