Księgarnia internetowa sieci Matras. Najlepsze książki w najlepszej cenie. Szybka dostawa 24h. Zapraszamy! ...

matras.pl
  • Domain Name
    matras.pl
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #67764
  • Page Size
    172.4 KB
  • Ip Address
    212.91.10.61
  • Heading
    H1: 1, H2: 34, H3: 40, H4: 1, H5: 0, H6: 0
  • Images
    49 GIF, 34 JPG, 7 PNG

Website Meta Analysis

  • Title
    Matras Księgarnie - matras.pl
  • Meta Keyword
    matras, matras księgarnie, księgarnia internetowa, książki
  • Meta Description
    Księgarnia internetowa sieci Matras. Najlepsze książki w najlepszej cenie. Szybka dostawa 24h. Zapraszamy!

Technical Analysis

  • Webserver
    Mis Matras
  • Ip Address
    212.91.10.61
  • Domain Age
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from matras.pl.

HTML Analysis

  • server: Mis Matras
  • date: Fri, 27 Sep 2013 04:30:06 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • content-encoding: gzip
  • age: 2759
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for matras.pl

IP 212.91.10.61 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 452 Errors
  • 254 Warnings
Ratio Text/Html
  • 0.6914362105883286
Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:url" content="http://www.matras.pl/" />

    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 66, Column 64: cannot generate system identifier for general entity "parentUrl"
    …nA.setURL('/naduzycie/index/form?abuseId='+abuseId+'&parentUrl='+document.URL);

    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 66, Column 64: general entity "parentUrl" not defined and no default entity
    …nA.setURL('/naduzycie/index/form?abuseId='+abuseId+'&parentUrl='+document.URL);

    This is usually a cascading error caused by 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 66, Column 73: reference not terminated by REFC delimiter
    …nA.setURL('/naduzycie/index/form?abuseId='+abuseId+'&parentUrl='+document.URL);

    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.

  • Error Line 66, Column 73: reference to entity "parentUrl" for which no system identifier could be generated
    …nA.setURL('/naduzycie/index/form?abuseId='+abuseId+'&parentUrl='+document.URL);

    This is usually a cascading error caused by 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 66, Column 63: entity was defined here
    …nA.setURL('/naduzycie/index/form?abuseId='+abuseId+'&parentUrl='+document.URL);
  • Error Line 141, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Warning Line 145, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=171002852975780";

    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 145, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=171002852975780";

    This is usually a cascading error caused by 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 145, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=171002852975780";

    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.

  • Error Line 145, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=171002852975780";

    This is usually a cascading error caused by 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 145, Column 56: entity was defined here
      js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=171002852975780";
  • Error Line 150, Column 48: there is no attribute "data-href"
    …   <div class="fb-like-box" data-href="http://www.facebook.com/Matraspl" data-…

    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 150, Column 94: there is no attribute "data-width"
    …www.facebook.com/Matraspl" data-width="292" data-height="500" data-show-faces=…

    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 150, Column 112: there is no attribute "data-height"
    …atraspl" data-width="292" data-height="500" data-show-faces="true" data-stream…

    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 150, Column 134: there is no attribute "data-show-faces"
    …92" data-height="500" data-show-faces="true" data-stream="true" data-border-co…

    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 150, Column 153: there is no attribute "data-stream"
    …0" data-show-faces="true" data-stream="true" data-border-color="185494" data-h…

    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 150, Column 178: there is no attribute "data-border-color"
    …="true" data-stream="true" data-border-color="185494" data-header="true"></div>

    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 150, Column 199: there is no attribute "data-header"
    …="true" data-stream="true" data-border-color="185494" data-header="true"></div>

    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 224, Column 28: document type does not allow element "span" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
            <span class="label">zapisz się do newslettera</span>

    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 235, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    	<div class="cart-header cart-empty">

    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 248, Column 58: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
          <input type="hidden" name="query2" id="querycopy2"/>

    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 249, Column 66: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
          <input type="hidden" name="as" id="advsearch_on" value="1"/>

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

  • Warning Line 418, Column 25: character "&" is the first character of a delimiter but occurred as data
          var qA = q.split('&');

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 477, Column 44: character "&" is the first character of a delimiter but occurred as data
          else {str += e.id + "=" + e.value + "&"}

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 501, Column 63: there is no attribute "target"
    …ass="main-item"><a href="http://firma.matras.pl" target="_blank">O nas</a></li>

    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 536, Column 10: ID "section4" already defined
    <div id="section4" class="sectionslide"><a href="http://www.matras.pl/kto-zabil…

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

  • Info Line 535, Column 10: ID "section4" first defined here
    <div id="section4" class="sectionslide"><a href="http://www.matras.pl/gry-plans…
  • Error Line 551, Column 31: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="category-products">

    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 638, Column 31: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="category-products">

    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 773, Column 31: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="category-products">

    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 909, Column 31: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="category-products">

    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 1040, Column 84: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …"slt_user_home" style="width: 460px; height: 290px;" class="ajax-big-bg"></div>

    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 1192, Column 31: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class="category-products">

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

  • Warning Line 1458, Column 47: cannot generate system identifier for general entity "preview"
    …ref="http://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureate…

    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 1458, Column 47: general entity "preview" not defined and no default entity
    …ref="http://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureate…

    This is usually a cascading error caused by 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 1458, Column 54: reference not terminated by REFC delimiter
    …tp://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureatem ranki…

    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 1458, Column 54: reference to external entity in attribute value
    …tp://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureatem ranki…

    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 1458, Column 54: reference to entity "preview" for which no system identifier could be generated
    …tp://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureatem ranki…

    This is usually a cascading error caused by 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 1458, Column 46: entity was defined here
    …href="http://ksiazki.matras.pl/?p=4196&preview=true">Księgarnia Matras laureat…
  • Error Line 1599, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1652, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1705, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1758, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1811, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1835, Column 41: ID "product-price-176280" already defined
                    <span class="price" id="product-price-176280">32,99 zł</span>

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

  • Info Line 706, Column 41: ID "product-price-176280" first defined here
                    <span class="price" id="product-price-176280">32,99 zł</span>
  • Error Line 1840, Column 41: ID "old-price-176280" already defined
                    <span class="price" id="old-price-176280">39,90 zł</span>

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

  • Info Line 711, Column 41: ID "old-price-176280" first defined here
                    <span class="price" id="old-price-176280">39,90 zł</span>
  • Error Line 1860, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1913, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 1967, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2015, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2068, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2116, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2165, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2218, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2271, Column 44: ID "block-related" already defined
            <ol class="mini-products-list" id="block-related">

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

  • Info Line 1546, Column 44: ID "block-related" first defined here
            <ol class="mini-products-list" id="block-related">
  • Error Line 2381, Column 422: there is no attribute "border"
    …ng.pl/logo/paypal_mark_50x34.gif" border="0" alt="Znak akceptacji" /></a></div>

    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.

Visitor Analysis

Daily Visitor
  • 1.867 visits