Can somebody help me find the wrong code?

Rubag · December 7, 2016

the keywords are in dutch so don't look at that. The page is a register page.

<html>

<head>

<title>Create Profile</title>

<?php

include("connect.php");

?>

</head>

<body >

<h2 class="header1"> Star Wars profiler </h2>

</header>

<nav>

<li><a href="show_profile.php">Show profile</a></li>

<li><a href="search_profile.php"> Search profile</a></li>

</ul>

</nav>

<tr>

<td colspan="2"><div align="center"><strong>Vul onderstaande gegevens in en creeër je profiel</strong></div></td>

</tr>

<tr>

<tr>

<td valign="bottom">Gebruikersnaam: </td>

</tr>

<tr>

<td valign="bottom">Wachtwoord: </td>

</tr>

<tr>

<td valign="bottom">Opnieuw wachtwoord: </td>

</tr>

<tr>

<td valign="bottom">Voornaam: </td>

</tr>

<tr>

<td valign="bottom">Tussenvoegsel: </td>

</tr>

<tr>

<td valign="bottom">Achternaam: </td>

</tr>

<tr>

<td valign="bottom">Leeftijd: </td>

</tr>

<tr>

<td valign="bottom"> Wapen </td>

<td>

<option>Pistool</option>

<option>LightSaber</option>

</select>

</td>

</tr>

<tr>

<td valign="bottom"> Model </td>

<td valign="bottom">indien lightsaber gekozen kies: none</td>

<td>

</select>

</td>

</tr>

<tr>

<td valign="bottom"> lightsaber kleur </td>

<td valign="bottom">indien pistool gekozen kies: none</td>

<td>

<option>blauw</option>

<option>groen</option>

<option>paars</option>

</select>

</td>

</tr>

<tr>

<td valign="bottom"> factie </td>

<td>

<option>Republic</option>

<option>Empire</option>

<option>Rebel</option>

<option>Resistance</option>

<option>First Order</option>

</select>

</td>

</tr>

<tr>

<td valign="bottom"><input type="submit"

name="submit" value="Registreer"></td>

</tr>

</table>

</form>

</div>

</td>

</tr>

</table>

</section>

</footer>

</body>

</html>

requinix · December 7, 2016

And how are we supposed to know what's wrong?

NotionCommotion · December 7, 2016

Well, your HTML is a wreck. Your also not doing any PHP other than potentially setting up a database connection.

Notes and Potential Issues

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

Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
- in Direct Input mode, no MIME Media Type is served to the validator
- No known Document Type could be detected
- No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
- No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> ) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

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

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

Learn how to add a doctype to your document from our FAQ.
No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.
Using Direct Input mode: UTF-8 character encoding assumed

Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

↑ Top

Validation Output: 10 Errors

Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
```
<html>
```
✉

The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
Line 8, Column 16: element "HEADER" undefined
```
        <header>
```
✉
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).
Line 12, Column 13: element "NAV" undefined
```
        <nav>
```
✉
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).
Line 18, Column 17: element "SECTION" undefined
```
        <section>
```
✉
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).
Line 19, Column 56: there is no attribute "HEIGHT"
```
            <table class="pagina3" width="100%" height="100%" cellpadding="10">
```
✉

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.
Line 30, Column 74: there is no attribute "MINLENGHT"
```
…               <td><input type="Text" minlenght="6" name="gebruikersnaam"></td>
```
✉

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.
Line 54, Column 64: value of attribute "TYPE" cannot be "NUMBER"; must be one of "TEXT", "PASSWORD", "CHECKBOX", "RADIO", "SUBMIT", "RESET", "FILE", "HIDDEN", "IMAGE", "BUTTON"
```
…               <td><input type="Number" name="leeftijd" min="1" max="150" ></t…
```
✉

The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
Line 54, Column 86: there is no attribute "MIN"
```
…              <td><input type="Number" name="leeftijd" min="1" max="150" ></td>
```
✉

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.
Line 54, Column 94: there is no attribute "MAX"
```
…              <td><input type="Number" name="leeftijd" min="1" max="150" ></td>
```
✉

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.
Line 119, Column 16: element "FOOTER" undefined
```
        <footer>
```
✉
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).

Psycho · December 7, 2016

I see that in the inner table (that holds the form) most of the rows contain two cells (i.e. TDs). However, there are a couple rows at the end that have three cells. If you are seeing some anomaly in the layout, it could be due to this. You should use the same number of cells per row or use rowspan on certain cells within a row that won't have the maximum number. When I am using any tables on a page, I will always set them with a border when developing the layout so I can "see" the table - then remove the border when I'm done if one is not wanted.

benanamen · December 7, 2016

In a nutshell, using tables for page layout went out in the 90's. This is almost 2017, use CSS like you're supposed to.

Sign In

Can somebody help me find the wrong code?

Recommended Posts

Rubag

Link to comment

Share on other sites

requinix

Link to comment

Share on other sites

NotionCommotion

Link to comment

Share on other sites

Psycho

Link to comment

Share on other sites

benanamen

Link to comment

Share on other sites

Join the conversation

Browse

Activity

Important Information