HTML Validator aktualisiert nicht

Forum für unsere SEO-Software "Hello Engines!".
Post Reply
KUHoepcke
Newbie
Newbie
Posts: 4
Joined: October 13th, 2010, 1:39 pm

HTML Validator aktualisiert nicht

Post by KUHoepcke » October 13th, 2010, 1:50 pm

Hallo zusammen,

nachdem der HTML-Validator eine Reihe von "Fehlern" gefunden hat, haben wir diese korrigiert. Allerdings findet der HTML-Validator auch nach der Korrektur die Fehler wieder. Wie kann ich dafür sorgen, dass HE6 prof. auf die aktualisierte Version der HTML-Datei zugreift?
Wer nachschauen möchte:
http://www.online-skatclub.de Zeile 303 sieht im Validator noch immer so aus:
>>> Zu den Turnieren gehts hier lang >>>

Die aktuelle Datei enthält statt dessen:
>>> Zu den Turnieren gehts hier lang >>> 

Gruß und Danke im Voraus:

Kay-Uwe

User avatar
AceBIT
Site Admin
Posts: 3450
Joined: March 20th, 2003, 8:08 pm

Re: HTML Validator aktualisiert nicht

Post by AceBIT » October 13th, 2010, 5:08 pm

Hallo,

liegen eventuell zwei Startseiten, z.B. index.htm und default.asp vor? Sind die Korrekturen in beiden durchgeführt worden?
Beste Grüße aus Darmstadt! - Best regards from Darmstadt!

AceBIT GmbH, Holzhofallee 15, 64295 Darmstadt, Deutschland - Tel.: +49 61 51 136 50-0, Fax: +49 61 51 136 50-20, E-Mail: info@acebit.de, Web: https://www.acebit.de

KUHoepcke
Newbie
Newbie
Posts: 4
Joined: October 13th, 2010, 1:39 pm

Re: HTML Validator aktualisiert nicht

Post by KUHoepcke » October 14th, 2010, 10:09 am

Moin...

Also, nein, es gibt keine Index.htm... Die Kollegen von der Entwicklung versichern mir, es gibt NUR eine .asp.

Gruß: Kay-Uwe

KUHoepcke
Newbie
Newbie
Posts: 4
Joined: October 13th, 2010, 1:39 pm

Re: HTML Validator aktualisiert nicht

Post by KUHoepcke » October 25th, 2010, 11:16 am

Hmm... keine Antwort mehr vom Acebit-Support. Auch keine Antwort auf zwei Emails. Und wenn ich hier im Forum bin, dann bin ich auch der einzige Anwesende (neben den Bots von Google und Yahoo)... Das sollte doch wohl zu denken geben, oder nicht? Gibts bei Acebit überhaupt irgendwelche Mitarbeiter hier in Deutschland??

Wie auch immer: Ich denke inzwischen, die Entscheidung pro HelloEngines würde heute bei uns zumindestens nicht mehr so ausfallen!

Kay-Uwe

KUHoepcke
Newbie
Newbie
Posts: 4
Joined: October 13th, 2010, 1:39 pm

Re: HTML Validator aktualisiert nicht

Post by KUHoepcke » October 25th, 2010, 12:10 pm

Und hier die Lösung:

Im Quellcode steht (nachweislich):

">>> Zu den Turnieren geht es hier lang >>> "

(wie soll auch sonst die Ausgabe von ">" codiert werden??). Der HTML-Validator von Helloengines interpretiert aber bereits und mach aus der Zeile

"> > > Zu den Turnieren geht es hier lang > > >"

und meldet die ">" als Fehler. Für uns ziemlich unsinnig, wie soll denn bitte ein ">" im Quellcode aussehen, wenn nicht "&gt"? (Übrigens bei "&ge" tritt der Fehler nicht auf...).

Gruß: Kay-Uwe (Rookie)

User avatar
Support (AceBIT)
AceBIT
AceBIT
Posts: 2463
Joined: March 27th, 2003, 10:53 am
Contact:

Re: HTML Validator aktualisiert nicht

Post by Support (AceBIT) » October 27th, 2010, 6:43 pm

Hallo Kay-Uwe,

zunächst einmal entschuldigen wir uns für die späte Antwort!

Wir konnten dies reproduzieren und werden es schnellstmöglich korrigieren.

Freundliche Grüße
AceBIT - Support -

Salsa
Newbie
Newbie
Posts: 3
Joined: August 3rd, 2013, 11:58 am

Re: HTML Validator aktualisiert nicht

Post by Salsa » August 3rd, 2013, 12:03 pm

Hallo Kay-Uwe
Kannst du mir Bitte helfen?
ich habe eine Validator auf meine website gemacht: http://www.salsa-ma.de
Ich habe schönn von 160 auf 42 Fehle reduzieren.
Aber jetzt kann ich nicht mehr weiter machen; weil ich vestehe nicht mehr wie ich Korrigieren kann.
Würdest du mir bitte helfen mit dieser Problem Validator?

Vielen Danke
und alles Gut
Salsa

User avatar
Stefan (AceBIT Team)
Guru
Guru
Posts: 423
Joined: June 4th, 2013, 5:19 pm

Re: HTML Validator aktualisiert nicht

Post by Stefan (AceBIT Team) » August 6th, 2013, 11:28 am

Hallo Salsa,

welche Version von Hello Engines benutzen Sie?

Salsa
Newbie
Newbie
Posts: 3
Joined: August 3rd, 2013, 11:58 am

Re: HTML Validator aktualisiert nicht

Post by Salsa » August 6th, 2013, 7:04 pm

Kay-Uwe - ich vestehe leider deine frage nicht: welche Version von Hello Engines benutzen Sie? Was meine Sie?

PS. Ich kann nicht so Gut Deutsche schreiben, beser ist auf: Spanich und Portuguiesisch.

Vielen Danke dass Sie zeite genohmen habe mir zu Antwocht.
Salsa

User avatar
Stefan (AceBIT Team)
Guru
Guru
Posts: 423
Joined: June 4th, 2013, 5:19 pm

Re: HTML Validator aktualisiert nicht

Post by Stefan (AceBIT Team) » August 8th, 2013, 3:43 pm

Hola Salsa,

no soy "Kay-Uwe", pero espero que no es un problema si te ayudo todavía. :)

Mi espanol no es tan bueno, pero si queres podemos intentar en espanol. O quizás entiendes inglés más que alemán?

Cual version de Hello Engines utilizas?

Salsa
Newbie
Newbie
Posts: 3
Joined: August 3rd, 2013, 11:58 am

Re: HTML Validator aktualisiert nicht

Post by Salsa » August 8th, 2013, 4:27 pm

Hola Stefan (AceBIT Team) Hi Stefan (AceBIT Team)
Danke - Muchas Gracias.
Ich habe kleines Problem
-Yo tengo un Pequenho problema.
Mein Website habe ich mit Validator die fehle zu Korrigieren in Html.
-My Website Yo echo una Busca de errores con Validator.
Aber ich weis nicht wie soll ich die Fehle Zu Korrigieren?
-No entiendo como puedo corrigir los Errores de Validator ?

Ich suche jemand die mir helfen Kann wie man dieser Fehle Korrigieren:
- Yo Busco ajuda de una persona que puede me orientar como puedo aser Correctamente:
--------------------------------
www.validator.w3.org:

Validation Output: 42 Errors

Error Line 54, Column 12: there is no attribute "src"

<embed src="Flash/head.swf" quality="high" width="1000"



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 54, Column 37: there is no attribute "quality"

<embed src="Flash/head.swf" quality="high" width="1000"



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 54, Column 50: there is no attribute "width"

<embed src="Flash/head.swf" quality="high" width="1000"



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 55, Column 8: there is no attribute "height"

height="200" name="movie" align=""



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 55, Column 19: there is no attribute "name"

height="200" name="movie" align=""



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 55, Column 33: there is no attribute "align"

height="200" name="movie" align=""



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 56, Column 6: there is no attribute "type"

type="application/x-shockwave-flash"



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 57, Column 6: "plug" is not a member of a group specified for any attribute

plug inspage="http://www.macromedia.com/go/getflashplayer">


Error Line 57, Column 14: there is no attribute "inspage"

plug inspage="http://www.macromedia.com/go/getflashplayer">



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 57, Column 59: element "embed" undefined

plug inspage="http://www.macromedia.com/go/getflashplayer">



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 58, Column 6: end tag for "embed" 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 54, Column 1: start tag was here

<embed src="Flash/head.swf" quality="high" width="1000"

Error Line 63, Column 20: there is no attribute "direction"

<marquee direction="Left" scrollamount="5" style="font-size: 12pt; color: rgb(1…



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 63, Column 40: there is no attribute "scrollamount"

…marquee direction="Left" scrollamount="5" style="font-size: 12pt; color: rgb(1…



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 63, Column 50: there is no attribute "style"

…rection="Left" scrollamount="5" style="font-size: 12pt; color: rgb(128, 0, 0);…



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 63, Column 125: there is no attribute "onmouseover"

…0); font-family: Tahoma;" onmouseover="this.stop()" onmouseout="this.start()" …



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 63, Column 150: there is no attribute "onmouseout"

… onmouseover="this.stop()" onmouseout="this.start()" height="20" width="1000"…



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 63, Column 173: there is no attribute "height"

… onmouseover="this.stop()" onmouseout="this.start()" height="20" width="1000">



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 63, Column 184: there is no attribute "width"

… onmouseover="this.stop()" onmouseout="this.start()" height="20" width="1000">



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 63, Column 190: element "marquee" undefined

… onmouseover="this.stop()" onmouseout="this.start()" height="20" width="1000">



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 179, Column 6: "plug" is not a member of a group specified for any attribute

plug inspage="http://www.macromedia.com/go/getflashplayer"> </embed></th>


Error Line 179, Column 59: element "embed" undefined

plug inspage="http://www.macromedia.com/go/getflashplayer"> </embed></th>



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 185, Column 6: "plug" is not a member of a group specified for any attribute

plug inspage="http://www.macromedia.com/go/getflashplayer"> </embed></th>


Error Line 185, Column 59: element "embed" undefined

plug inspage="http://www.macromedia.com/go/getflashplayer"> </embed></th>



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 192, Column 174: there is no attribute "allowscriptaccess"

…h="175" height="142" allowscriptaccess="always" allowfullscreen="true"></embed>



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 192, Column 199: there is no attribute "allowfullscreen"

…h="175" height="142" allowscriptaccess="always" allowfullscreen="true"></embed>



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 192, Column 205: element "embed" undefined

…h="175" height="142" allowscriptaccess="always" allowfullscreen="true"></embed>



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 249, Column 6: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<hr />



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 251, Column 17: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<h3 align="left">Die neuen Salsa Tanzkurse<br />



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 254, Column 6: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<hr />



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 258, Column 17: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<h3 align="left">Salsa, Bachata und Rueda de Casino.



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 263, Column 6: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<hr />



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 269, Column 17: document type does not allow element "h5" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

<h5 align="left">Dank an die Fotografen



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 275, Column 9: end tag for "p" omitted, but OMITTAG NO was specified

</td>



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 237, Column 2: start tag was here

<p class="Stil10"><strong>

Error Line 308, Column 71: there is no attribute "flashvars"

…uttons.org/icons/fb/12.swf" flashvars="name=salsa.mannheim.3" quality="high" 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 308, Column 116: there is no attribute "wmode"

…alsa.mannheim.3" quality="high" wmode="transparent" width="120" height="120" t…



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 308, Column 218: element "embed" undefined

…" height="120" type="application/x-shockwave-flash" allowscriptaccess="always">



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 309, Column 11: end tag for "embed" omitted, but OMITTAG NO was specified

</object>



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 308, Column 5: start tag was here

<embed src="http://facebookbuttons.org/icons/fb/12.swf" flashvars="name=sal…

Error Line 321, Column 219: element "embed" undefined

…" height="120" type="application/x-shockwave-flash" allowscriptaccess="always">



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 329, Column 12: end tag for "embed" omitted, but OMITTAG NO was specified

</table></td>



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 321, Column 5: start tag was here

<embed src="http://twitterfollowbuttons.com/icons/tw/2.swf" flashvars="name…

Error Line 329, Column 12: end tag for "object" omitted, but OMITTAG NO was specified

</table></td>



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 311, Column 3: start tag was here

<object type="application/x-shockwave-flash" data="http://twitterfollowbutton

Error Line 329, Column 12: end tag for "th" omitted, but OMITTAG NO was specified

</table></td>



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 297, Column 9: start tag was here

<th scope="row">

Error Line 329, Column 12: end tag for "tr" omitted, but OMITTAG NO was specified

</table></td>



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 296, Column 7: start tag was here

<tr>

User avatar
Stefan (AceBIT Team)
Guru
Guru
Posts: 423
Joined: June 4th, 2013, 5:19 pm

Re: HTML Validator aktualisiert nicht

Post by Stefan (AceBIT Team) » August 8th, 2013, 5:08 pm

Hola Salsa, :shock:

ok, eso es demasiado texto :dots:

Eso es el foro por el programa "Hello Engines" que tiene un "HTML Validator" proprio. Me aparece que tú utilizaste el validator online de w3. Correcto?

En Hello Engines puedes analizar documentos html y corregir los problemas en el HTML Editor.

Como quiere que sea, tienes la solucion por cada problema en el texto que lo has insertado en el mensaje (en ingles). Solo tienes que abres el documento html en un editor de texto y corriges el código html. :wink:

Y algo mas, por favor no escribes mensajes tan largos en el futuro. Por ejemplo en eso caso, fue bastante pegar un link.

Post Reply