r-bank.pl

Skip to Content Szanowni Państwo, Dnia 10-07-2013 w godzinach 00:00 - 02:00 mogą wystąpić problemy z logowaniem oraz autoryzacją transakcji płatniczych z wykorzystaniem potwierdzeń SMS. Utrudnienia spowodowane są przez prace techniczne prowadzone ... ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    r-bank.pl
  • Favicon
  • Alexa Rank
    #60990
  • Google Page Rank
    PR 0
  • Ip Address
    195.85.249.50
  • Page Size
    36.3 KB
  • Images
    0 GIF, 0 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 2 3 9 0 0

Website Meta Analysis



  • Title
    Raiffeisen Polbank - Logowanie - Raiffeisen Bank Polska S.A.
  • Meta Keyword
  • Meta Description
    Skip to Content Szanowni Państwo, Dnia 10-07-2013 w godzinach 00:00 - 02:00 mogą wystąpić problemy z logowaniem oraz autoryzacją transakcji płatniczych z wykorzystaniem potwierdzeń SMS. Utrudnienia spowodowane są przez prace techniczne prowadzone ...

Technical Analysis



  • Webserver
    Apache/2.2.3 (Red Hat) DAV/2 mod_jk/1.2.37
  • Ip Address
    195.85.249.50
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from r-bank.pl.

HTML Analysis

  • content-length: 34861
  • content-type: text/html;charset=UTF-8
  • date: Tue, 09 Jul 2013 13:14:04 GMT
  • server: Apache/2.2.3 (Red Hat) DAV/2 mod_jk/1.2.37
  • x-powered-by: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
  • liferay-portal: Liferay Portal Enterprise Edition 6.0 EE SP1 (Bunyan / Build 6011 / December 16, 2010)
  • etag: "37ad645f"
  • via: 1.1 proxy-moj.raiffeisenpolbank.com
  • proxy-agent: rbpl-proxy
  • x-google-cache-control: remote-fetch
No data whois for r-bank.pl

DNS Analysis


DNS servers
dns2.raiffeisen.pl [195.85.249.13]
dns1.raiffeisen.pl [195.85.249.11]


DNS Records

Answer records
r-bank.pl SOA
server: dns1.raiffeisen.pl
email: root@raiffeisen.pl
serial: 2011090901
refresh: 28800
retry: 3600
expire: 172800
minimum ttl: 86400
172800s
r-bank.pl NS  dns2.raiffeisen.pl 172800s
r-bank.pl NS  dns1.raiffeisen.pl 172800s
r-bank.pl A 195.85.249.50 172800s

Authority records

Additional records
dns1.raiffeisen.pl A 195.85.249.11 3600s
dns2.raiffeisen.pl A 195.85.249.13 3600s

IP 195.85.249.50 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 195.85.249.50

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 51 Errors
  • 46 Warnings
Ratio Text/Html
  • 0.8039110057641545
Message Error
  • Error Line 1, Column 136: there is no attribute "class"
    …xhtml1-transitional.dtd"> <html class="ltr" dir="ltr" lang="pl-PL"> <head> <me…

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

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

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

  • Error Line 1, Column 124: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …/xhtml1/DTD/xhtml1-transitional.dtd"> <html class="ltr" dir="ltr" lang="pl-PL"…

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 2, Column 1062: there is no attribute "id"
    …ntent">Skip to Content</a> <header id="banner" role="banner" class="clearfix">…

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

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

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

  • Error Line 2, Column 1076: there is no attribute "role"
    … Content</a> <header id="banner" role="banner" class="clearfix"> <div class="w…

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

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

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

  • Error Line 2, Column 1091: there is no attribute "class"
    …eader id="banner" role="banner" class="clearfix"> <div class="wrapper"> <div i…

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

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

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

  • Error Line 2, Column 1101: element "header" undefined
    …banner" role="banner" class="clearfix"> <div class="wrapper"> <div id="top"> <…

    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).
  • Error Line 2, Column 2881: element "section" undefined
    …/div> </div> </div> </header> <section> <div id="main-content" role="main"> <d…

    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).
  • Error Line 2, Column 2911: there is no attribute "role"
    …<section> <div id="main-content" role="main"> <div class="wrapper"> <div class…

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

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

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

  • Warning Line 3, Column 122: cannot generate system identifier for general entity "p_p_lifecycle"
    …nk.com/logowanie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mod…

    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.

  • Error Line 3, Column 122: general entity "p_p_lifecycle" not defined and no default entity
    …nk.com/logowanie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mod…

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

  • Warning Line 3, Column 135: reference not terminated by REFC delimiter
    …nie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_co…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 135: reference to external entity in attribute value
    …nie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_co…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 135: reference to entity "p_p_lifecycle" for which no system identifier could be generated
    …nie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_co…

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

  • Info Line 3, Column 121: entity was defined here
    …ank.com/logowanie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mo…
  • Warning Line 3, Column 138: cannot generate system identifier for general entity "p_p_state"
    …?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_i…

    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.

  • Error Line 3, Column 138: general entity "p_p_state" not defined and no default entity
    …?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_i…

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

  • Warning Line 3, Column 147: reference not terminated by REFC delimiter
    …putilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 147: reference to external entity in attribute value
    …putilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 147: reference to entity "p_p_state" for which no system identifier could be generated
    …putilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-…

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

  • Info Line 3, Column 137: entity was defined here
    …e?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_…
  • Warning Line 3, Column 155: cannot generate system identifier for general entity "p_p_mode"
    …ogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_co…

    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.

  • Error Line 3, Column 155: general entity "p_p_mode" not defined and no default entity
    …ogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_co…

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

  • Warning Line 3, Column 163: reference not terminated by REFC delimiter
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 163: reference to external entity in attribute value
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 163: reference to entity "p_p_mode" for which no system identifier could be generated
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&…

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

  • Info Line 3, Column 154: entity was defined here
    …login&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_c…
  • Warning Line 3, Column 169: cannot generate system identifier for general entity "p_p_col_id"
    …ycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_co…

    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.

  • Error Line 3, Column 169: general entity "p_p_col_id" not defined and no default entity
    …ycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_co…

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

  • Warning Line 3, Column 179: reference not terminated by REFC delimiter
    …_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 179: reference to external entity in attribute value
    …_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 179: reference to entity "p_p_col_id" for which no system identifier could be generated
    …_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&…

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

  • Info Line 3, Column 168: entity was defined here
    …cycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_c…
  • Warning Line 3, Column 189: cannot generate system identifier for general entity "p_p_col_pos"
    …mal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPa…

    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.

  • Error Line 3, Column 189: general entity "p_p_col_pos" not defined and no default entity
    …mal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPa…

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

  • Warning Line 3, Column 200: reference not terminated by REFC delimiter
    …e=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 200: reference to external entity in attribute value
    …e=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 200: reference to entity "p_p_col_pos" for which no system identifier could be generated
    …e=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputi…

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

  • Info Line 3, Column 188: entity was defined here
    …rmal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastP…
  • Warning Line 3, Column 203: cannot generate system identifier for general entity "p_p_col_count"
    …iew&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilis…

    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.

  • Error Line 3, Column 203: general entity "p_p_col_count" not defined and no default entity
    …iew&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilis…

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

  • Warning Line 3, Column 216: reference not terminated by REFC delimiter
    …d=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 216: reference to external entity in attribute value
    …d=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 216: reference to entity "p_p_col_count" for which no system identifier could be generated
    …d=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_…

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

  • Info Line 3, Column 202: entity was defined here
    …view&p_p_col_id=column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputili…
  • Warning Line 3, Column 219: cannot generate system identifier for general entity "saveLastPath"
    …olumn-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_act…

    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.

  • Error Line 3, Column 219: general entity "saveLastPath" not defined and no default entity
    …olumn-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_act…

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

  • Warning Line 3, Column 231: reference not terminated by REFC delimiter
    …col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 231: reference to external entity in attribute value
    …col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 231: reference to entity "saveLastPath" for which no system identifier could be generated
    …col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2…

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

  • Info Line 3, Column 218: entity was defined here
    …column-1&p_p_col_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_ac…
  • Warning Line 3, Column 234: cannot generate system identifier for general entity "_rputilislogin_struts_action"
    …_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2flo…

    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.

  • Error Line 3, Column 234: general entity "_rputilislogin_struts_action" not defined and no default entity
    …_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2flo…

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

  • Warning Line 3, Column 262: reference not terminated by REFC delimiter
    …astPath=0&_rputilislogin_struts_action=%2frpu%2flogin" name="utilisLogin" meth…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 3, Column 262: reference to external entity in attribute value
    …astPath=0&_rputilislogin_struts_action=%2frpu%2flogin" name="utilisLogin" meth…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 3, Column 262: reference to entity "_rputilislogin_struts_action" for which no system identifier could be generated
    …astPath=0&_rputilislogin_struts_action=%2frpu%2flogin" name="utilisLogin" meth…

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

  • Info Line 3, Column 233: entity was defined here
    …l_pos=1&p_p_col_count=2&saveLastPath=0&_rputilislogin_struts_action=%2frpu%2fl…
  • Error Line 3, Column 477: there is no attribute "autocomplete"
    …ype="text" name="userId" autocomplete="off"> </label> <span class="keyboard nu…

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

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

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

  • Error Line 3, Column 483: end tag for "input" omitted, but OMITTAG NO was specified
    …ext" name="userId" autocomplete="off"> </label> <span class="keyboard numeric"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 402: start tag was here
    …ss="capitalize">identyfikator:</span> <input id="userId" class="required" type…
  • Error Line 3, Column 631: end tag for "img" omitted, but OMITTAG NO was specified
    ….png" alt="Klawiatura ekranowa"></span> </li> <li> <label for="userPass"> <spa…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 524: start tag was here
    …label> <span class="keyboard numeric"><img src="/raiffeisen-polbank-utilis-the…
  • Error Line 3, Column 795: end tag for "input" omitted, but OMITTAG NO was specified
    …d" name="userPass" autocomplete="off"> </label> <span class="keyboard"> <img s…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 706: start tag was here
    …span class="capitalize">hasło:</span> <input id="userPass" class="required" ty…
  • Error Line 3, Column 941: end tag for "img" omitted, but OMITTAG NO was specified
    … alt="Numeryczna klawiatura ekranowa"> <div class="normal tooltip"> <div class…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 829: start tag was here
    …ff"> </label> <span class="keyboard"> <img src="/raiffeisen-polbank-utilis-the…
  • Error Line 3, Column 969: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ekranowa"> <div class="normal tooltip"> <div class="tooltipContent">CAPS LOCK …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 3, Column 1132: end tag for "input" omitted, but OMITTAG NO was specified
    …put type="submit" value="zaloguj się"> <p class="sub"> <a href="/problem-z-log…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3, Column 1091: start tag was here
    …gle"></div> </div> </span> </li> <li> <input type="submit" value="zaloguj się"…
  • Warning Line 4, Column 1994: cannot generate system identifier for general entity "groupId"
    …=95b4e3d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="R…

    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.

  • Error Line 4, Column 1994: general entity "groupId" not defined and no default entity
    …=95b4e3d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="R…

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

  • Warning Line 4, Column 2001: reference not terminated by REFC delimiter
    …d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeis…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4, Column 2001: reference to external entity in attribute value
    …d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeis…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4, Column 2001: reference to entity "groupId" for which no system identifier could be generated
    …d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeis…

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

  • Info Line 4, Column 1993: entity was defined here
    …d=95b4e3d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="…
  • Warning Line 4, Column 2011: cannot generate system identifier for general entity "t"
    …cf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Brokers…

    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.

  • Error Line 4, Column 2011: general entity "t" not defined and no default entity
    …cf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Brokers…

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

  • Warning Line 4, Column 2012: reference not terminated by REFC delimiter
    …f-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Brokers"…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4, Column 2012: reference to external entity in attribute value
    …f-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Brokers"…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4, Column 2012: reference to entity "t" for which no system identifier could be generated
    …f-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Brokers"…

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

  • Info Line 4, Column 2010: entity was defined here
    …bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Broker…
  • Error Line 4, Column 2059: end tag for "img" omitted, but OMITTAG NO was specified
    …77583" alt="Raiffeisen Brokers"></span> <span class="content">Systemy transakc…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4, Column 1921: start tag was here
    …get="_self" rel=""> <span class="img"><img src="/image/image_gallery?uuid=95b4…
  • Warning Line 4, Column 2317: reference not terminated by REFC delimiter
    …09-460f-4b77-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4, Column 2317: reference to external entity in attribute value
    …09-460f-4b77-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4, Column 2317: reference to entity "groupId" for which no system identifier could be generated
    …09-460f-4b77-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor…

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

  • Info Line 4, Column 1993: entity was defined here
    …d=95b4e3d6-d03d-4bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="…
  • Warning Line 4, Column 2328: reference not terminated by REFC delimiter
    …7-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor"></span> <…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 4, Column 2328: reference to external entity in attribute value
    …7-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor"></span> <…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 4, Column 2328: reference to entity "t" for which no system identifier could be generated
    …7-9139-94058205c927&groupId=30393759&t=1357951877582" alt="R-Faktor"></span> <…

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

  • Info Line 4, Column 2010: entity was defined here
    …bcf-8cc9-84c78110ac3c&groupId=30393759&t=1357951877583" alt="Raiffeisen Broker…
  • Error Line 4, Column 2365: end tag for "img" omitted, but OMITTAG NO was specified
    …t=1357951877582" alt="R-Faktor"></span> <span class="content">Platforma faktor…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4, Column 2237: start tag was here
    …get="_self" rel=""> <span class="img"><img src="/image/image_gallery?uuid=b178…
  • Error Line 25, Column 650: there is no attribute "id"
    …hrefFm"></form> </section> <footer id="footer" role="contentinfo"> <div id="p_…

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

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

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

  • Error Line 25, Column 664: there is no attribute "role"
    …> </section> <footer id="footer" role="contentinfo"> <div id="p_p_id_amgembedd…

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

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

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

  • Error Line 25, Column 677: element "footer" undefined
    …<footer id="footer" role="contentinfo"> <div id="p_p_id_amgembeddedjournaldisp…

    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).
  • Warning Line 34, Column 76: reference not terminated by REFC delimiter
    …ef="/logowanie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_st…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 34, Column 76: reference to external entity in attribute value
    …ef="/logowanie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_st…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 34, Column 76: reference to entity "p_p_lifecycle" for which no system identifier could be generated
    …ef="/logowanie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_st…

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

  • Info Line 3, Column 121: entity was defined here
    …ank.com/logowanie?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mo…
  • Warning Line 34, Column 88: reference not terminated by REFC delimiter
    …ie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 34, Column 88: reference to external entity in attribute value
    …ie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 34, Column 88: reference to entity "p_p_state" for which no system identifier could be generated
    …ie?p_p_id=82&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=…

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

  • Info Line 3, Column 137: entity was defined here
    …e?p_p_id=rputilislogin&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_…
  • Warning Line 34, Column 104: reference not terminated by REFC delimiter
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fvi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 34, Column 104: reference to external entity in attribute value
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fvi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 34, Column 104: reference to entity "p_p_mode" for which no system identifier could be generated
    …_lifecycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fvi…

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

  • Info Line 3, Column 154: entity was defined here
    …login&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_c…
  • Warning Line 34, Column 110: cannot generate system identifier for general entity "_82_struts_action"
    …ycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&lan…

    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.

  • Error Line 34, Column 110: general entity "_82_struts_action" not defined and no default entity
    …ycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&lan…

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

  • Warning Line 34, Column 127: reference not terminated by REFC delimiter
    …normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&languageId=en_US" ti…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 34, Column 127: reference to external entity in attribute value
    …normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&languageId=en_US" ti…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 34, Column 127: reference to entity "_82_struts_action" for which no system identifier could be generated
    …normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&languageId=en_US" ti…

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

  • Info Line 34, Column 109: entity was defined here
    …cycle=1&p_p_state=normal&p_p_mode=view&_82_struts_action=%2flanguage%2fview&la…
  • Warning Line 34, Column 147: cannot generate system identifier for general entity "languageId"
    …&_82_struts_action=%2flanguage%2fview&languageId=en_US" title="">English versi…

    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.

  • Error Line 34, Column 147: general entity "languageId" not defined and no default entity
    …&_82_struts_action=%2flanguage%2fview&languageId=en_US" title="">English versi…

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

  • Warning Line 34, Column 157: reference not terminated by REFC delimiter
    …s_action=%2flanguage%2fview&languageId=en_US" title="">English version</a> </l…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 34, Column 157: reference to external entity in attribute value
    …s_action=%2flanguage%2fview&languageId=en_US" title="">English version</a> </l…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 34, Column 157: reference to entity "languageId" for which no system identifier could be generated
    …s_action=%2flanguage%2fview&languageId=en_US" title="">English version</a> </l…

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

  • Info Line 34, Column 146: entity was defined here
    …w&_82_struts_action=%2flanguage%2fview&languageId=en_US" title="">English vers…

Visitor Analysis

Daily Visitor
  • 3.033 visits

In Page Analysis