W3C Validation

How do we go about fixing the errors caused by JFBC when a website is ran through the W3C Validator?

[code]Warning Line 180, Column 56: cannot generate system identifier for general entity "task"

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 56: general entity "task" not defined and no default entity

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 60: reference not terminated by REFC delimiter

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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.
Error Line 180, Column 60: reference to entity "task" for which no system identifier could be generated

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 55: entity was defined here

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

Warning Line 180, Column 68: cannot generate system identifier for general entity "return"

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 68: general entity "return" not defined and no default entity

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 74: reference not terminated by REFC delimiter

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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.
Error Line 180, Column 74: reference to entity "return" for which no system identifier could be generated

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

✉

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 180, Column 67: entity was defined here

var jfbcLogoutLink = '/index.php?option=com_jfbconnect&task=logout&return=Lw==';

Error Line 325, Column 21: there is no attribute "v"

While a search on your forum didn't provide any results, I thought to do an advanced search on Google, and now I see this has been discussed before here on the forums.

If the problems I have are still related to Facebook's side of things, so be it, but if you do see any that we can correct, any help is much appreciated.

I understand validation errors might be less important then some people make them out to be, but I have to think that having as few as possible is still a good thing.