Code: Selecteer alles
W3C CSS Validator Resultaten met object : http://cubaplaza.nl/[b]portal[/b].php (CSS versie 2.1)
Sorry! We vonden de volgende fouten (6)
URI : http://cubaplaza.nl/portal.php
386 Ongeldig getal : float center geen float waarde : center center
397 Ongeldig getal : float center geen float waarde : center center
409 Ongeldig getal : float center geen float waarde : center center
447 Ongeldig getal : float center geen float waarde : center center
718 Ongeldig getal : float center geen float waarde : center center
736 Ongeldig getal : float center geen float waarde : center center Ook de HTML validator geeft diverse errors en waarschuwingen, zowel op index als op portal.
Code: Selecteer alles
W3C Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Jump To:
Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!
Result: 13 Errors, 3 warning(s)
Address: http://cubaplaza.nl/index.php
Modified: (undefined)
Server: Apache
Size: (undefined)
Content-Type: text/html
Encoding: utf-8
Doctype: XHTML 1.0 Transitional
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
Mozilla Foundation LogoThe W3C CSS validator is developed with assistance from the Mozilla Foundation, and supported by community donations.
Donate and help us build better tools for a better web.
Options
Show Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML-Tidy
Help on the options is available.
↑ Top
Validation Output: 13 Errors
Error Line 26, Column 36: there is no attribute "CONTENT"
<meta name="creation_date" CONTENT="17 juni 2007" />
✉
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 26, Column 52: required attribute "content" not specified
<meta name="creation_date" CONTENT="17 juni 2007" />
✉
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 207, Column 85: cannot generate system identifier for general entity "tag"
…odex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Error Line 207, Column 85: general entity "tag" not defined and no default entity
…odex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="…
✉
This is usually a cascading error caused by 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 207, Column 88: reference not terminated by REFC delimiter
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
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 207, Column 88: reference to external entity in attribute value
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
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 '&'.
Error Line 207, Column 88: reference to entity "tag" for which no system identifier could be generated
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
This is usually a cascading error caused by 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 207, Column 84: entity was defined here
…codex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style=…
Error Line 320, Column 130: end tag for element "centerr" which is not open
…rotator.tradetracker.net/?r=10721&t=js" charset="UTF-8"></script></centerr>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Error Line 333, Column 87: there is no attribute "border"
…4" height="60" frameborder="0" border="0" marginwidth="0" marginheight="0" scr…
✉
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 333, Column 138: document type does not allow element "iframe" here
…der="0" border="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>');
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Error Line 338, Column 20: an attribute specification must start with a name or name token
document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…
✉
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Error Line 338, Column 20: element "sc" undefined
document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…
✉
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 338, Column 90: delimiter "'" invalid: only S separators and TAGC allowed here
…'ript type="text/javascript" src="'+uri+'" charset="ISO-8859-1"></sc'+'ript>');
✉
Error Line 340, Column 9: end tag for "center" omitted, but OMITTAG NO was specified
</div>
✉
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 320, Column 1: start tag was here
<center><script type="text/javascript" src="http://rotator.tradetracker.net/?r=…
Error Line 725, Column 246: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…in de laatste 15 minuten)<br /><center>Bezoekersrecord: Op Zo 31 okt 2010 23:2…
✉
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 1393, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
</body>
✉
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 1390, Column 7: start tag was here
</div><center><br/><center>All logos and trademarks in this site are property o…
↑ Top
Home
About...
News
Docs
Help & FAQ
Feedback
Contribute
W3COpen-Source
I heart Validator logo
This service runs the W3C Markup Validator, v1.2+hg.
Copyright © 1994-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
Code: Selecteer alles
W3C Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Jump To:
Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!
Result: 13 Errors, 3 warning(s)
Address: http://cubaplaza.nl/portal.php
Modified: (undefined)
Server: Apache
Size: (undefined)
Content-Type: text/html
Encoding: utf-8
Doctype: XHTML 1.0 Transitional
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
Validators Donation Program LogoThe W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.
Options
Show Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML-Tidy
Help on the options is available.
↑ Top
Validation Output: 13 Errors
Error Line 26, Column 36: there is no attribute "CONTENT"
<meta name="creation_date" CONTENT="17 juni 2007" />
✉
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 26, Column 52: required attribute "content" not specified
<meta name="creation_date" CONTENT="17 juni 2007" />
✉
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 207, Column 85: cannot generate system identifier for general entity "tag"
…odex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Error Line 207, Column 85: general entity "tag" not defined and no default entity
…odex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="…
✉
This is usually a cascading error caused by 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 207, Column 88: reference not terminated by REFC delimiter
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
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 207, Column 88: reference to external entity in attribute value
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
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 '&'.
Error Line 207, Column 88: reference to entity "tag" for which no system identifier could be generated
…x=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style="bor…
✉
This is usually a cascading error caused by 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 207, Column 84: entity was defined here
…codex=aHR0cDovL3d3dy5jdWJhcGxhemEubmw=&tag=1" alt="Free Page Rank Tool" style=…
Error Line 320, Column 130: end tag for element "centerr" which is not open
…rotator.tradetracker.net/?r=10721&t=js" charset="UTF-8"></script></centerr>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Error Line 333, Column 87: there is no attribute "border"
…4" height="60" frameborder="0" border="0" marginwidth="0" marginheight="0" scr…
✉
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 333, Column 138: document type does not allow element "iframe" here
…der="0" border="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>');
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Error Line 338, Column 20: an attribute specification must start with a name or name token
document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…
✉
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Error Line 338, Column 20: element "sc" undefined
document.write('<sc'+'ript type="text/javascript" src="'+uri+'" charset="ISO-88…
✉
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 338, Column 90: delimiter "'" invalid: only S separators and TAGC allowed here
…'ript type="text/javascript" src="'+uri+'" charset="ISO-8859-1"></sc'+'ript>');
✉
Error Line 340, Column 9: end tag for "center" omitted, but OMITTAG NO was specified
</div>
✉
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 320, Column 1: start tag was here
<center><script type="text/javascript" src="http://rotator.tradetracker.net/?r=…
Error Line 725, Column 246: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
…in de laatste 15 minuten)<br /><center>Bezoekersrecord: Op Zo 31 okt 2010 23:2…
✉
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 1393, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
</body>
✉
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 1390, Column 7: start tag was here
</div><center><br/><center>All logos and trademarks in this site are property o…
↑ Top
Home
About...
News
Docs
Help & FAQ
Feedback
Contribute
W3COpen-Source
I heart Validator logo
This service runs the W3C Markup Validator, v1.2+hg.
Copyright © 1994-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
