ESOK-hanke 2006-2011

[Invalid] Markup Validation of webdeveloper-sole.adm.jyu.fi-1248861517453.html - W3C Markup Validator

W3C's easy-to-use HTML validation service, based on an SGML parser.

Errors found while checking this document as HTML 4.01 Transitional!

Result: 296 Errors, 22 warning(s)
File:

Use the file selection box above if you wish to re-validate the uploaded file webdeveloper-sole.adm.jyu.fi-1248861517453.html
Modified:(undefined)
Server:Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729)
Size:(undefined)
Content-Type:text/html
Encoding: iso-8859-1 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: HTML 4.01 Transitional (detect automatically) HTML5 (experimental) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML + RDFa XHTML Basic 1.0 XHTML Basic 1.1 XHTML Mobile Profile 1.2 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0
Root Element: html
Options
Show Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML Tidy

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Warning Unable to Determine Parse Mode!

    The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

    • the MIME Media Type (text/html) can be used for XML or SGML document types
    • No known Document Type could be detected
    • No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
    • No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.

    As a default, the validator is falling back to SGML mode.

  2. Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

    No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

    The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

    It is recommended to use a DOCTYPE declaration as the very first thing in your HTML document, to identify the precise language being used. For example, for a typical XHTML 1.0 document: 

          <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
      <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
        <head>
          <title>Title</title>
        </head>

        <body>
          <!-- ... body of document ... -->
        </body>
      </html>

    For XML documents, you may also wish to include an "XML Declaration" even before the DOCTYPE Declaration, but this is not well supported in older browsers. More information about this can be found in the XHTML 1.0 Recommendation.

    The W3C QA Activity maintains a List of Valid Doctypes that you can choose from, and the WDG maintains a document on "Choosing a DOCTYPE".

↑ Top

Validation Output: 296 Errors

  1. Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>" 
    <html xmlns:java-sole="http://xml.apache.org/xslt/java/fi.solenovo.servlet.ui.So

    ✉

    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.

  2. Error Line 1, Column 23: Attribute "XMLNS:JAVA-SOLE" is not a valid attribute 
    <html xmlns:java-sole="http://xml.apache.org/xslt/java/fi.solenovo.servlet.ui.So

    ✉

    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.

  3. Error Line 1, Column 102: Attribute "XMLNS:DYN" is not a valid attribute 
    …o.servlet.ui.SoleSession" xmlns:dyn="http://exslt.org/dynamic">

    ✉

    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.

  4. Error Line 12, Column 11: Attribute "HREF" is not a valid attribute. Did you mean "href"? 
    <rel href="/tyoaikatest/all/css/favicon.ico" type="shortcut icon"></rel>

    ✉

    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.

  5. Error Line 12, Column 51: Attribute "TYPE" is not a valid attribute. Did you mean "type"? 
    <rel href="/tyoaikatest/all/css/favicon.ico" type="shortcut icon"></rel>

    ✉

    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.

  6. Error Line 12, Column 66: element "REL" undefined. Did you mean "area" or "del"? 
    …aikatest/all/css/favicon.ico" type="shortcut icon"></rel>

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  7. Error Line 13, Column 57: element "REL" undefined. Did you mean "area" or "del"? 
    <rel href="/tyoaikatest/all/css/favicon.gif" type="icon"></rel>

    ✉

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  8. Error Line 21, Column 163: required attribute "ALT" not specified 
    …" class="topmenu_ekakuva" border="0">Etusivu</a><a href="/tyoaikatest/disp/fi

    ✉

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

  9. Error Line 21, Column 324: required attribute "ALT" not specified 
    …gif" class="topmenu_kuva" border="0">Yhteydenotto</a><a target="new" href="/t

    ✉

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

  10. Error Line 21, Column 482: required attribute "ALT" not specified 
    …gif" class="topmenu_kuva" border="0">Käyttöohje</a></td><td class="ylatunnus_

    ✉

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

  11. Error Line 22, Column 235: required attribute "ALT" not specified 
    …gif" class="topmenu_kuva" border="0">Lopetus</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>.

  12. Error Line 30, Column 53: required attribute "ALT" not specified 
    <img border="0" src="/tyoaikatest/all/gifs/logo.gif"></p>

    ✉

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

  13. Error Line 32, Column 103: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/menu_minus.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  14. Warning Line 35, Column 60: cannot generate system identifier for general entity "vainomat" 
    …isp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img borde

    ✉

    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.

  15. Error Line 35, Column 60: general entity "vainomat" not defined and no default entity 
    …isp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img borde

    ✉

    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.

  16. Error Line 35, Column 68: reference to entity "vainomat" for which no system identifier could be generated 
    …a_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" sr

    ✉

    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.

  17. Info Line 35, Column 58: entity was defined here 
    …/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor
  18. Warning Line 35, Column 69: cannot generate system identifier for general entity "menuid" 
    …_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src

    ✉

    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.

  19. Error Line 35, Column 69: general entity "menuid" not defined and no default entity 
    …_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src

    ✉

    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.

  20. Error Line 35, Column 75: reference to entity "menuid" for which no system identifier could be generated 
    …k/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyo

    ✉

    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.

  21. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  22. Warning Line 35, Column 78: cannot generate system identifier for general entity "omat" 
    …ab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaik

    ✉

    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.

  23. Error Line 35, Column 78: general entity "omat" not defined and no default entity 
    …ab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaik

    ✉

    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.

  24. Error Line 35, Column 82: reference to entity "omat" for which no system identifier could be generated 
    …ab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoaikates

    ✉

    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.

  25. Info Line 35, Column 76: entity was defined here 
    …/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa
  26. Error Line 35, Column 148: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  27. Error Line 35, Column 226: reference to entity "vainomat" for which no system identifier could be generated 
    …a_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: blac

    ✉

    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.

  28. Info Line 35, Column 58: entity was defined here 
    …/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor
  29. Error Line 35, Column 233: reference to entity "menuid" for which no system identifier could be generated 
    …k/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: black; text

    ✉

    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. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  31. Error Line 35, Column 240: reference to entity "omat" for which no system identifier could be generated 
    …ab/clr?page=0&vainomat&menuid=2&omat=519120" style="color: black; text-decora

    ✉

    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.

  32. Info Line 35, Column 76: entity was defined here 
    …/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa
  33. Error Line 38, Column 65: reference to entity "menuid" for which no system identifier could be generated 
    …i/ta_pohja/tab/tab/clr?page=0&menuid=3"><img border="0" src="/tyoaikatest/all

    ✉

    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. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  35. Error Line 38, Column 126: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  36. Error Line 38, Column 201: reference to entity "menuid" for which no system identifier could be generated 
    …i/ta_pohja/tab/tab/clr?page=0&menuid=3">Reaaliaikainen</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.

  37. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  38. Error Line 41, Column 120: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  39. Error Line 44, Column 129: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  40. Error Line 47, Column 103: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/menu_minus.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  41. Error Line 50, Column 76: reference to entity "vainomat" for which no system identifier could be generated 
    …sisummat/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" sr

    ✉

    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.

  42. Info Line 35, Column 58: entity was defined here 
    …/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor
  43. Error Line 50, Column 83: reference to entity "menuid" for which no system identifier could be generated 
    …t/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" src="/tyo

    ✉

    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.

  44. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  45. Error Line 50, Column 90: reference to entity "omat" for which no system identifier could be generated 
    …ab/clr?page=0&vainomat&menuid=7&omat=519120"><img border="0" src="/tyoaikates

    ✉

    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.

  46. Info Line 35, Column 76: entity was defined here 
    …/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa
  47. Error Line 50, Column 156: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  48. Error Line 50, Column 242: reference to entity "vainomat" for which no system identifier could be generated 
    …sisummat/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</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.

  49. Info Line 35, Column 58: entity was defined here 
    …/disp/fi/ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img bor
  50. Error Line 50, Column 249: reference to entity "menuid" for which no system identifier could be generated 
    …t/tab/tab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</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.

  51. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  52. Error Line 50, Column 256: reference to entity "omat" for which no system identifier could be generated 
    …ab/clr?page=0&vainomat&menuid=7&omat=519120">Kuukausisummat</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.

  53. Info Line 35, Column 76: entity was defined here 
    …/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" src="/tyoa
  54. Error Line 53, Column 127: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  55. Error Line 56, Column 121: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  56. Error Line 59, Column 104: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/menu_minus.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  57. Error Line 62, Column 123: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  58. Error Line 65, Column 104: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/menu_minus.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  59. Error Line 68, Column 79: reference to entity "menuid" for which no system identifier could be generated 
    …kaynnistys/tab/tab/clr?page=0&menuid=13"><img border="0" src="/tyoaikatest/al

    ✉

    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.

  60. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  61. Error Line 68, Column 141: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  62. Error Line 68, Column 230: reference to entity "menuid" for which no system identifier could be generated 
    …kaynnistys/tab/tab/clr?page=0&menuid=13">K&auml;ynnistys</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.

  63. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  64. Error Line 71, Column 75: reference to entity "menuid" for which no system identifier could be generated 
    …tti_lataus/tab/tab/clr?page=0&menuid=14"><img border="0" src="/tyoaikatest/al

    ✉

    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.

  65. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  66. Error Line 71, Column 137: required attribute "ALT" not specified 
    …/tyoaikatest/all/gifs/menu_none.gif"></a>&nbsp;<a href="/tyoaikatest/disp/fi/

    ✉

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

  67. Error Line 71, Column 222: reference to entity "menuid" for which no system identifier could be generated 
    …tti_lataus/tab/tab/clr?page=0&menuid=14">Valmiit</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.

  68. Info Line 35, Column 67: entity was defined here 
    …ta_tyoaik/tab/tab/clr?page=0&vainomat&menuid=2&omat=519120"><img border="0" s
  69. Error Line 81, Column 133: required attribute "ALT" not specified 
    …rc="/tyoaikatest/all/gifs/fetch.gif">&nbsp;Hae kaikki</a><a href="/tyoaikates

    ✉

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

  70. Error Line 81, Column 276: required attribute "ALT" not specified 
    …c="/tyoaikatest/all/gifs/startq.gif">&nbsp;Tarkennettu haku</a><a class="acti

    ✉

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

  71. Error Line 81, Column 426: required attribute "ALT" not specified 
    … src="/tyoaikatest/all/gifs/new.gif">&nbsp;Uusi</a><a href="/tyoaikatest/disp

    ✉

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

  72. Error Line 81, Column 564: required attribute "ALT" not specified 
    … src="/tyoaikatest/all/gifs/new.gif">&nbsp;Aikav&auml;likirjaus</a><a href="/

    ✉

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

  73. Error Line 81, Column 728: required attribute "ALT" not specified 
    …c="/tyoaikatest/all/gifs/report.gif">&nbsp;csv-Raportti</a>

    ✉

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

  74. Error Line 98, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  75. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  76. Error Line 102, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  77. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  78. Error Line 106, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  79. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  80. Error Line 110, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  81. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  82. Error Line 114, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  83. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  84. Error Line 118, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  85. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  86. Error Line 122, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  87. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  88. Error Line 126, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  89. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  90. Error Line 130, Column 10: ID "HEADER" already defined 
    <div id="header">

    ✉

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  91. Info Line 94, Column 9: ID "HEADER" first defined here 
    <div id="header">
  92. Warning Line 136, Column 95: cannot generate system identifier for general entity "hyvpass" 
    …p/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpv

    ✉

    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.

  93. Error Line 136, Column 95: general entity "hyvpass" not defined and no default entity 
    …p/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpv

    ✉

    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.

  94. Error Line 136, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090

    ✉

    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.

  95. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  96. Warning Line 136, Column 104: cannot generate system identifier for general entity "id" 
    …yoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=2009070

    ✉

    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.

  97. Error Line 136, Column 104: general entity "id" not defined and no default entity 
    …yoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=2009070

    ✉

    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.

  98. Error Line 136, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  99. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  100. Warning Line 136, Column 114: cannot generate system identifier for general entity "muuttaja" 
    …tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&or

    ✉

    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.

  101. Error Line 136, Column 114: general entity "muuttaja" not defined and no default entity 
    …tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&or

    ✉

    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.

  102. Error Line 136, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  103. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  104. Warning Line 136, Column 130: cannot generate system identifier for general entity "muutpvm" 
    …&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&

    ✉

    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.

  105. Error Line 136, Column 130: general entity "muutpvm" not defined and no default entity 
    …&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&

    ✉

    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.

  106. Error Line 136, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  107. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  108. Warning Line 136, Column 153: cannot generate system identifier for general entity "organisaatio" 
    …ttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass

    ✉

    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.

  109. Error Line 136, Column 153: general entity "organisaatio" not defined and no default entity 
    …ttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass

    ✉

    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.

  110. Error Line 136, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  111. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  112. Warning Line 136, Column 171: cannot generate system identifier for general entity "projekti" 
    …vm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_hen

    ✉

    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.

  113. Error Line 136, Column 171: general entity "projekti" not defined and no default entity 
    …vm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_hen

    ✉

    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.

  114. Error Line 136, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  115. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  116. Warning Line 136, Column 187: cannot generate system identifier for general entity "totpass" 
    …5&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projek

    ✉

    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.

  117. Error Line 136, Column 187: general entity "totpass" not defined and no default entity 
    …5&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projek

    ✉

    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.

  118. Error Line 136, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  119. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  120. Warning Line 136, Column 196: cannot generate system identifier for general entity "sub_pvm" 
    …aatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_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 "&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.

  121. Error Line 136, Column 196: general entity "sub_pvm" not defined and no default entity 
    …aatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_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.

  122. Error Line 136, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  123. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  124. Warning Line 136, Column 205: cannot generate system identifier for general entity "sub_henkilo" 
    …7&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&

    ✉

    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.

  125. Error Line 136, Column 205: general entity "sub_henkilo" not defined and no default entity 
    …7&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&

    ✉

    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.

  126. Error Line 136, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  127. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  128. Warning Line 136, Column 218: cannot generate system identifier for general entity "sub_projekti" 
    …8305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0

    ✉

    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.

  129. Error Line 136, Column 218: general entity "sub_projekti" not defined and no default entity 
    …8305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0

    ✉

    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.

  130. Error Line 136, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  131. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  132. Warning Line 136, Column 232: cannot generate system identifier for general entity "sub_projteht" 
    …sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht

    ✉

    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.

  133. Error Line 136, Column 232: general entity "sub_projteht" not defined and no default entity 
    …sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht

    ✉

    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.

  134. Error Line 136, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  135. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  136. Warning Line 136, Column 246: cannot generate system identifier for general entity "sub_projteht0" 
    …enkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteh

    ✉

    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.

  137. Error Line 136, Column 246: general entity "sub_projteht0" not defined and no default entity 
    …enkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteh

    ✉

    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.

  138. Error Line 136, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  139. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  140. Warning Line 136, Column 261: cannot generate system identifier for general entity "sub_projteht1" 
    …jekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteh

    ✉

    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.

  141. Error Line 136, Column 261: general entity "sub_projteht1" not defined and no default entity 
    …jekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteh

    ✉

    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.

  142. Error Line 136, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  143. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  144. Warning Line 136, Column 276: cannot generate system identifier for general entity "sub_projteht2" 
    …teht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteh

    ✉

    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.

  145. Error Line 136, Column 276: general entity "sub_projteht2" not defined and no default entity 
    …teht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteh

    ✉

    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.

  146. Error Line 136, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  147. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  148. Warning Line 136, Column 291: cannot generate system identifier for general entity "sub_projteht3" 
    …eht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_e

    ✉

    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.

  149. Error Line 136, Column 291: general entity "sub_projteht3" not defined and no default entity 
    …eht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_e

    ✉

    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.

  150. Error Line 136, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  151. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  152. Warning Line 136, Column 306: cannot generate system identifier for general entity "sub_projteht4" 
    …eht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img cl

    ✉

    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.

  153. Error Line 136, Column 306: general entity "sub_projteht4" not defined and no default entity 
    …eht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img cl

    ✉

    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.

  154. Error Line 136, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  155. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  156. Warning Line 136, Column 321: cannot generate system identifier for general entity "sub_pager_exists" 
    …eht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" b

    ✉

    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.

  157. Error Line 136, Column 321: general entity "sub_pager_exists" not defined and no default entity 
    …eht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" b

    ✉

    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.

  158. Error Line 136, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  159. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  160. Error Line 136, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  161. Error Line 139, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519142&muuttaja=519120&muutpvm=20090

    ✉

    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.

  162. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  163. Error Line 139, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519142&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  164. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  165. Error Line 139, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519142&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  166. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  167. Error Line 139, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519142&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  168. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  169. Error Line 139, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  170. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  171. Error Line 139, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  172. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  173. Error Line 139, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  174. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  175. Error Line 139, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  176. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  177. Error Line 139, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  178. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  179. Error Line 139, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  180. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  181. Error Line 139, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  182. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  183. Error Line 139, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  184. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  185. Error Line 139, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  186. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  187. Error Line 139, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  188. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  189. Error Line 139, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  190. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  191. Error Line 139, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  192. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  193. Error Line 139, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  194. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  195. Error Line 139, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  196. Error Line 142, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519160&muuttaja=519120&muutpvm=20090

    ✉

    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.

  197. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  198. Error Line 142, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519160&muuttaja=519120&muutpvm=200907130

    ✉

    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.

  199. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  200. Error Line 142, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519160&muuttaja=519120&muutpvm=20090713093243&organisaat

    ✉

    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.

  201. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  202. Error Line 142, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519160&muuttaja=519120&muutpvm=20090713093243&organisaatio=23217&projek

    ✉

    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.

  203. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  204. Error Line 142, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090713093243&organisaatio=23217&projekti=198305&totpass=&sub_pvm=&

    ✉

    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.

  205. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  206. Error Line 142, Column 180: reference to entity "projekti" for which no system identifier could be generated 
    …13093243&organisaatio=23217&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  207. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  208. Error Line 142, Column 195: reference to entity "totpass" for which no system identifier could be generated 
    …saatio=23217&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  209. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  210. Error Line 142, Column 204: reference to entity "sub_pvm" for which no system identifier could be generated 
    …217&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  211. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  212. Error Line 142, Column 217: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  213. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  214. Error Line 142, Column 231: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  215. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  216. Error Line 142, Column 245: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  217. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  218. Error Line 142, Column 260: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  219. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  220. Error Line 142, Column 275: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  221. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  222. Error Line 142, Column 290: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  223. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  224. Error Line 142, Column 305: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  225. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  226. Error Line 142, Column 320: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  227. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  228. Error Line 142, Column 338: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  229. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  230. Error Line 142, Column 415: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  231. Error Line 145, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519141&muuttaja=519120&muutpvm=20090

    ✉

    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.

  232. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  233. Error Line 145, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519141&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  234. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  235. Error Line 145, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519141&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  236. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  237. Error Line 145, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519141&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  238. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  239. Error Line 145, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  240. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  241. Error Line 145, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  242. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  243. Error Line 145, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  244. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  245. Error Line 145, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  246. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  247. Error Line 145, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  248. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  249. Error Line 145, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  250. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  251. Error Line 145, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  252. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  253. Error Line 145, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  254. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  255. Error Line 145, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  256. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  257. Error Line 145, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  258. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  259. Error Line 145, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  260. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  261. Error Line 145, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  262. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  263. Error Line 145, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  264. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  265. Error Line 145, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  266. Error Line 148, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519140&muuttaja=519120&muutpvm=20090

    ✉

    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.

  267. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  268. Error Line 148, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519140&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  269. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  270. Error Line 148, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519140&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  271. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  272. Error Line 148, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519140&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  273. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  274. Error Line 148, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  275. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  276. Error Line 148, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  277. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  278. Error Line 148, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  279. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  280. Error Line 148, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  281. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  282. Error Line 148, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  283. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  284. Error Line 148, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  285. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  286. Error Line 148, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  287. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  288. Error Line 148, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  289. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  290. Error Line 148, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  291. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  292. Error Line 148, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  293. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  294. Error Line 148, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  295. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  296. Error Line 148, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  297. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  298. Error Line 148, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  299. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  300. Error Line 148, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  301. Error Line 151, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519139&muuttaja=519120&muutpvm=20090

    ✉

    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.

  302. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  303. Error Line 151, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519139&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  304. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  305. Error Line 151, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519139&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  306. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  307. Error Line 151, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519139&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  308. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  309. Error Line 151, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  310. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  311. Error Line 151, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  312. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  313. Error Line 151, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  314. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  315. Error Line 151, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  316. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  317. Error Line 151, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  318. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  319. Error Line 151, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  320. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  321. Error Line 151, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  322. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  323. Error Line 151, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  324. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  325. Error Line 151, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  326. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  327. Error Line 151, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  328. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  329. Error Line 151, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  330. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  331. Error Line 151, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  332. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  333. Error Line 151, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  334. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  335. Error Line 151, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  336. Error Line 154, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519179&muuttaja=519120&muutpvm=20090

    ✉

    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.

  337. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  338. Error Line 154, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519179&muuttaja=519120&muutpvm=200907140

    ✉

    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.

  339. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  340. Error Line 154, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519179&muuttaja=519120&muutpvm=20090714095102&organisaat

    ✉

    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.

  341. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  342. Error Line 154, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519179&muuttaja=519120&muutpvm=20090714095102&organisaatio=4338&projekt

    ✉

    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.

  343. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  344. Error Line 154, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090714095102&organisaatio=4338&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  345. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  346. Error Line 154, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …714095102&organisaatio=4338&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  347. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  348. Error Line 154, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4338&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  349. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  350. Error Line 154, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …338&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  351. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  352. Error Line 154, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  353. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  354. Error Line 154, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  355. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  356. Error Line 154, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  357. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  358. Error Line 154, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  359. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  360. Error Line 154, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  361. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  362. Error Line 154, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  363. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  364. Error Line 154, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  365. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  366. Error Line 154, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  367. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  368. Error Line 154, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  369. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  370. Error Line 154, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  371. Error Line 157, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519138&muuttaja=519120&muutpvm=20090

    ✉

    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.

  372. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  373. Error Line 157, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519138&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  374. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  375. Error Line 157, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519138&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  376. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  377. Error Line 157, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519138&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  378. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  379. Error Line 157, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  380. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  381. Error Line 157, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  382. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  383. Error Line 157, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  384. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  385. Error Line 157, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  386. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  387. Error Line 157, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  388. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  389. Error Line 157, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  390. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  391. Error Line 157, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  392. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  393. Error Line 157, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  394. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  395. Error Line 157, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  396. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  397. Error Line 157, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  398. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  399. Error Line 157, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  400. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  401. Error Line 157, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  402. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  403. Error Line 157, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  404. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  405. Error Line 157, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  406. Error Line 160, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519137&muuttaja=519120&muutpvm=20090

    ✉

    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.

  407. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  408. Error Line 160, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519137&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  409. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  410. Error Line 160, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519137&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  411. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  412. Error Line 160, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519137&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  413. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  414. Error Line 160, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  415. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  416. Error Line 160, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  417. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  418. Error Line 160, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  419. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  420. Error Line 160, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  421. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  422. Error Line 160, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  423. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  424. Error Line 160, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  425. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  426. Error Line 160, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  427. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  428. Error Line 160, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  429. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  430. Error Line 160, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  431. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  432. Error Line 160, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  433. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  434. Error Line 160, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  435. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  436. Error Line 160, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  437. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  438. Error Line 160, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  439. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  440. Error Line 160, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  441. Error Line 163, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519136&muuttaja=519120&muutpvm=20090

    ✉

    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.

  442. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  443. Error Line 163, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519136&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  444. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  445. Error Line 163, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519136&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  446. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  447. Error Line 163, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519136&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  448. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  449. Error Line 163, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  450. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  451. Error Line 163, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  452. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  453. Error Line 163, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  454. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  455. Error Line 163, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  456. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  457. Error Line 163, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  458. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  459. Error Line 163, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  460. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  461. Error Line 163, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  462. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  463. Error Line 163, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  464. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  465. Error Line 163, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  466. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  467. Error Line 163, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  468. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  469. Error Line 163, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  470. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  471. Error Line 163, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  472. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  473. Error Line 163, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  474. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  475. Error Line 163, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  476. Error Line 166, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519135&muuttaja=519120&muutpvm=20090

    ✉

    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.

  477. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  478. Error Line 166, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519135&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  479. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  480. Error Line 166, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519135&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  481. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  482. Error Line 166, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519135&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  483. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  484. Error Line 166, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  485. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  486. Error Line 166, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  487. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  488. Error Line 166, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  489. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  490. Error Line 166, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  491. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  492. Error Line 166, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  493. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  494. Error Line 166, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  495. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  496. Error Line 166, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  497. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  498. Error Line 166, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  499. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  500. Error Line 166, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  501. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  502. Error Line 166, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  503. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  504. Error Line 166, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  505. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  506. Error Line 166, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  507. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  508. Error Line 166, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  509. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  510. Error Line 166, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  511. Error Line 169, Column 102: reference to entity "hyvpass" for which no system identifier could be generated 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519134&muuttaja=519120&muutpvm=20090

    ✉

    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.

  512. Info Line 136, Column 93: entity was defined here 
    …isp/fi/ta_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muut
  513. Error Line 169, Column 106: reference to entity "id" for which no system identifier could be generated 
    …aik/edi/tab/fet?henkilo=&hyvpass=&id=519134&muuttaja=519120&muutpvm=200907011

    ✉

    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.

  514. Info Line 136, Column 102: entity was defined here 
    …_tyoaik/edi/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090
  515. Error Line 169, Column 122: reference to entity "muuttaja" for which no system identifier could be generated 
    …henkilo=&hyvpass=&id=519134&muuttaja=519120&muutpvm=20090701100915&organisaat

    ✉

    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.

  516. Info Line 136, Column 112: entity was defined here 
    …i/tab/fet?henkilo=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&
  517. Error Line 169, Column 137: reference to entity "muutpvm" for which no system identifier could be generated 
    …s=&id=519134&muuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekt

    ✉

    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.

  518. Info Line 136, Column 128: entity was defined here 
    …o=&hyvpass=&id=519143&muuttaja=519120&muutpvm=20090701100915&organisaatio=429
  519. Error Line 169, Column 165: reference to entity "organisaatio" for which no system identifier could be generated 
    …&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&s

    ✉

    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.

  520. Info Line 136, Column 151: entity was defined here 
    …uuttaja=519120&muutpvm=20090701100915&organisaatio=4297&projekti=198305&totpa
  521. Error Line 169, Column 179: reference to entity "projekti" for which no system identifier could be generated 
    …701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&su

    ✉

    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.

  522. Info Line 136, Column 169: entity was defined here 
    …tpvm=20090701100915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_h
  523. Error Line 169, Column 194: reference to entity "totpass" for which no system identifier could be generated 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub

    ✉

    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.

  524. Info Line 136, Column 185: entity was defined here 
    …915&organisaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_proj
  525. Error Line 169, Column 203: reference to entity "sub_pvm" for which no system identifier could be generated 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht

    ✉

    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.

  526. Info Line 136, Column 194: entity was defined here 
    …isaatio=4297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub
  527. Error Line 169, Column 216: reference to entity "sub_henkilo" for which no system identifier could be generated 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh

    ✉

    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.

  528. Info Line 136, Column 203: entity was defined here 
    …297&projekti=198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht
  529. Error Line 169, Column 230: reference to entity "sub_projekti" for which no system identifier could be generated 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte

    ✉

    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.

  530. Info Line 136, Column 216: entity was defined here 
    …198305&totpass=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteh
  531. Error Line 169, Column 244: reference to entity "sub_projteht" for which no system identifier could be generated 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt

    ✉

    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.

  532. Info Line 136, Column 230: entity was defined here 
    …=&sub_pvm=&sub_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projte
  533. Error Line 169, Column 259: reference to entity "sub_projteht0" for which no system identifier could be generated 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt

    ✉

    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.

  534. Info Line 136, Column 244: entity was defined here 
    …_henkilo=&sub_projekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projt
  535. Error Line 169, Column 274: reference to entity "sub_projteht1" for which no system identifier could be generated 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt

    ✉

    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.

  536. Info Line 136, Column 259: entity was defined here 
    …rojekti=&sub_projteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projt
  537. Error Line 169, Column 289: reference to entity "sub_projteht2" for which no system identifier could be generated 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager

    ✉

    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.

  538. Info Line 136, Column 274: entity was defined here 
    …ojteht=&sub_projteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projt
  539. Error Line 169, Column 304: reference to entity "sub_projteht3" for which no system identifier could be generated 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img

    ✉

    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.

  540. Info Line 136, Column 289: entity was defined here 
    …jteht0=&sub_projteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager
  541. Error Line 169, Column 319: reference to entity "sub_projteht4" for which no system identifier could be generated 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"

    ✉

    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.

  542. Info Line 136, Column 304: entity was defined here 
    …jteht1=&sub_projteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img
  543. Error Line 169, Column 337: reference to entity "sub_pager_exists" for which no system identifier could be generated 
    …ht3=&sub_projteht4=&sub_pager_exists="><img class="tablink" border="0" src="/

    ✉

    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.

  544. Info Line 136, Column 319: entity was defined here 
    …jteht2=&sub_projteht3=&sub_projteht4=&sub_pager_exists="><img class="tablink"
  545. Error Line 169, Column 414: required attribute "ALT" not specified 
    …tyoaikatest/all/gifs/edit_small.gif"></a></td><td class="datatable">JY testau

    ✉

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

  546. Error Line 174, Column 9: end tag for "TR" which is not finished 
    <tr></tr>

    ✉

    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.

  547. Error Line 176, Column 4: end tag for element "P" which is not open 
    </p>

    ✉

    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