[Invalid] Markup Validation of http://www.nexuizninjaz.com/

Errors found while checking this document as XHTML 1.0 Transitional!

Result:	9 Errors, 15 warning(s)
Address:
Encoding:	utf-8
Doctype:	XHTML 1.0 Transitional
Root Element:	html
Root Namespace:	http://www.w3.org/1999/xhtml

Result:

9 Errors, 15 warning(s)

Address:

Encoding:

utf-8

Doctype:

XHTML 1.0 Transitional

Root Element:

html

Root Namespace:

http://www.w3.org/1999/xhtml

Interested in “developing” your developer skills? In W3Cx’s hands-on Professional Certificate Program, learn how to code the right way by creating Web sites and apps that use the latest Web standards. Find out more!

Donate and help us build better tools for a better web.

Options

Help on the options is available.

↑ Top

Validation Output: 9 Errors

Line 25, Column 161: cannot generate system identifier for general entity "v"
```
…/users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtu…
```
✉

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.
Line 25, Column 161: general entity "v" not defined and no default entity
```
…/users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtu…
```
✉

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.
Line 25, Column 162: reference not terminated by REFC delimiter
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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.
Line 25, Column 162: reference to external entity in attribute value
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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 '&'.
Line 25, Column 162: reference to entity "v" for which no system identifier could be generated
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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.

Line 25, Column 160: entity was defined here

…e/users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-yout…

Line 25, Column 165: cannot generate system identifier for general entity "orderby"
```
…rs/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-p…
```
✉

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.
Line 25, Column 165: general entity "orderby" not defined and no default entity
```
…rs/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-p…
```
✉

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.
Line 25, Column 172: reference not terminated by REFC delimiter
```
…izninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile"…
```
✉

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.
Line 25, Column 172: reference to external entity in attribute value
```
…izninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile"…
```
✉

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 '&'.
Line 25, Column 172: reference to entity "orderby" for which no system identifier could be generated
```
…izninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile"…
```
✉

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.

Line 25, Column 164: entity was defined here

…ers/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-…

Line 25, Column 183: cannot generate system identifier for general entity "client"
```
…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />
```
✉

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.
Line 25, Column 183: general entity "client" not defined and no default entity
```
…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />
```
✉

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.
Line 25, Column 189: reference not terminated by REFC delimiter
```
…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />
```
✉

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.
Line 25, Column 189: reference to external entity in attribute value
```
…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />
```
✉

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 '&'.
Line 25, Column 189: reference to entity "client" for which no system identifier could be generated
```
…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />
```
✉

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.

Line 25, Column 182: entity was defined here

…ninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtube-profile" />

Line 77, Column 146: reference not terminated by REFC delimiter
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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.
Line 77, Column 146: reference to external entity in attribute value
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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 '&'.
Line 77, Column 146: reference to entity "v" for which no system identifier could be generated
```
…users/nexuizninjaz/favorites?alt=rss&v=2&orderby=published&client=ytapi-youtub…
```
✉

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.