Hmm eh?

[bowersbros]

i dont understand what you mean about the if/else bit,

Also ive changed to styling it now using font-style:italics; in CSS

please can u explain the if/else bit?

[bowersbros]

Okay, ive fixed that one, one last error to go

Line number On/Off | Expand/Contract | Select all

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="submit" name="submit" value="Update Cart" />
✉
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>").

i dont understand this one, as it isnt inside an inline element. its only inside a <form> which is where it is supposed to be, :/

[bowersbros]

fixed, It was as simple as wrapping it all in <fieldset>

(the form data)

[bowersbros]

still got the problem if i remove error_reporting(0) though,

Any ideas?

[libeco]

If it's the input on the same page I wouldn't worry about it. Remember that validating is only a matter of making sure you didn't make any stupid mistakes. It's not a way to magically create semantic code. Firefox' validator has no problem with your page.

[bowersbros]

I know, but i cant post it as being XHTML valid, if it throws up errors..

:/

[libeco]

fixed, It was as simple as wrapping it all in <fieldset>

(the form data)

That was the version I was looking at while writing my previous post. I already saw a fieldset.

[bowersbros]

So, any ideas about the error_reporting bit?

[bowersbros]

These are the errors given out by the validator:

Line number On/Off | Expand/Contract | Select all

document type does not allow element "br" here
        <br />
✉
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).

Line number On/Off | Expand/Contract | Select all

document type does not allow element "b" here
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/flashmin/pu
✉
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).

Line number On/Off | Expand/Contract | Select all

character data is not allowed here
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/flashmin/pu
✉
You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Line number On/Off | Expand/Contract | Select all

document type does not allow element "b" here
…rgument supplied for foreach() in <b>/home/flashmin/public_html/codecanyon/ca
✉
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).

Line number On/Off | Expand/Contract | Select all

character data is not allowed here
…c_html/codecanyon/cart/cart.php</b> on line <b>41</b><br />
✉
You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.

Line number On/Off | Expand/Contract | Select all

document type does not allow element "b" here
…ecanyon/cart/cart.php</b> on line <b>41</b><br />
✉
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).

Line number On/Off | Expand/Contract | Select all

document type does not allow element "br" here
…/cart.php</b> on line <b>41</b><br />
✉
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).

However, none of that is in my code..

Im totally baffled by this ? :/

[wide_load]

you are getting php errors in your html when the validator visits the page, perhaps because some $_GET data is not present.

try using the http://validator.w3.org/#validate_by_input version and paste in the source you see